BUEditor submodule: itemlist & autocomplete popup window

I see the point. Implementing a view would be no choice because I have to query all the links the view provides to create appropriate tags (I was thinking about that while defining the way Linodef should work).

Currently the Lino BUEditor submodule uses a Javascript function that is similar to the default button function of BUEditor. Instead I could use a select box for the list of nodes/fields/terms. At least I'd favor this over a popup window ...

... though the best way would be to give the choice to the user, so you could decide which button type you want to use (Javascript button, select box or popup). I'll look how good this feature would fit into the module.

Hehe, thx for these hints. Those modules could be useful for an additional button (type nodename, then press enter), but only looking at their functions will tell if the modules provides an api like structure.

Currently I'm working on two additional buttons: One as a popup window, the other as Javascript dialog using jQuery UI module. The second is almost done, for the first I'll have to look how to pass the data from one window to another (if its possible that easy).

Me too.^^

Yes, Nodereference use similar techniques but I think I'll implement the required functions for the autocomplete button in this module. Otherwise Linodef will depend on 1000+1 modules one day. ;)

After a couple of days working with the Javascript Dialog box it turned out that it isn't more useful than the currently implemented button (overview for big node/field/term lists has same quality) so I removed it.

Instead the popup window is working now. It took several hours since I never worked with hook_menu before. Inbetween I thought I had to realize it with views but then I got to know about the Wildcards in hook_menu. This saved my day. ;) The advantages of the popup window: Better overview for many nodes etc and it stays open after you've included a tag so you're able to include several tags without having to click on the button each time.

The popup is not styled yet (I've just written a plain template) but this is secondary. Next I'll include autocomplete button and then I commit it to CVS. You are welcome to test the dev release then for bugs (I'll let you know when it's ready to test).

Okay, the autocomplete is much more tricky than I suspected.

I can't use Nodereference and Userreference (even not as template) and Quick Node Find/Autocomplete Node Finder don't work as well. Maybe the reason is the inclusion in the Javascripts of the Button or the reason is unknown.

1) Therefore my own autocomplete list/menu entry doesn't work as well 'cause the form is part of the Javascript of the Button (unlikely) or because its inside an other form. => solution: popup
2) Besides that the submitting of variables to create the autocomplete list (e.g. element you entered and a API related variable) wasn't successful til now. EDIT: due to reason #1.
3) Furthermore I'm forced to use AHAH function (so the site doesn't reload after submitting), but for that I need the ID of the active textarea which isn't possible before submitting (can't pass variables from Javascript to PHP without submitting). => solution: Maybe include in popup (would solve #1 at least), but no idea how to insert the code into the correct textarea.

So three unsovled problems (the autocomplete itself, passing the variables (doesn't exist if #1 is solved) and the submitting of the form) prevent the completion of linodef rc2. If I don't find a solution the next couple of days I go without the autocomplete button for rc2.

I've found a way to implement the autocomplete button inside a popup and return the tag to the editor. I just want to do some further testing tomorrow morning (me @UTC+1) and then I'll commit the code to drupal.org. So the 6.x-1.x-dev will be updated sometime tomorrow night (the dev versions get updated only twice a day).

Before releasing an official rc2 I'd like you to have a look at the changes and say what you like/dislike, pls. :) (I need to change quite a few things in the documentation anyway)

Yes, the autocomplete uses exactly the same filter (the same function) as the listbutton and the popup window.

I've committed the chances, the dev version should be updated within 12 hours or earlier. Before uploading the folder to your Drupal installation, deactivate the Linodef and Linodef BUEditor module and delete the old "Linodef" folder. Then upload the new folder and heed the fact that you have to activate three Linodef modules. ;)

Please heed the commit message (found at page' bottom). That means update your BUEditor Buttons and "no link" tags (if you've used them already). It is unlikely that the tags will change again in a future version. Sorry for that but I needed to do it now.

What a foolish bug, I haven't added base_url. If you don't want to wait for the dev release to be updated download the updated file here and replace linodef_buttons_bueditor.module.

Thx for the feedback, I'll include the two suggestions. Before using it at a production site wait for rc2 release, pls. Don't use the dev release since it is more difficult to give support for a production site then. I just need a couple of days for rc2.

Added translateable text, close button, own css file.

Comitted to D6 branch. Please test the dev release on a test environment for bugs/flaws since with this dev update Linodef got tons of new features. RC2 will be released before Christmas unless major design bugs are found. If you find a bug relating this issue then reactivate it, please. Thx!