2010/12/4 16:15:22
|
---|
|
@Phoenyx - AutocompleteHere ya go man - it's all working now.
I stripped some of the options out of Autocomplete.php you can replace them if you wish - but you should be wrapping them in ifs so they are not there if the option is empty. right? Please also check autocomp.php I was having real trouble with the original for some reason - so I included this one. Notice the json encoding formatting - this is critical to it actually working reliably. Edited by UnderDog on 2010/12/5 4:31:01
|
2010/12/5 2:20:25
|
---|
|
Re: @Phoenyx - AutocompleteThank you for your work Will. It's working great.
On thing to notice is, that you have to deactivate the debugger for autocomp.php via icms::$logger->disableLogger();. Otherwise, Autocomplete.php cannot read the response properly. For the configs: In case they are not set, I'm defaulting them to something so that we can always set them for the jQuery function. I will finalize everything and commit it. |
2010/12/5 9:01:53
|
---|
|
Re: @Phoenyx - AutocompleteThis looks cool. Any indication where this can be plugged in?
Thx, D. |
_________________
|
2010/12/5 9:52:23
|
---|
|
Re: @Phoenyx - AutocompleteIt's part of the IPF / ImBuilding for 1.3
|
2010/12/5 12:48:40
|
---|
|
Re: @Phoenyx - AutocompleteI saw that in the zipfile
I wanted to know if this plugs in into some class, so that it comes automagically available to current modules, or do we have to use it explicitly? After having a better look, there is some coding to be done specifically. So we'll need to educate module developers in using it. |
_________________
|
2010/12/6 9:33:01
|
---|
|
Re: @Phoenyx - AutocompleteThat's correct David. I've added some hints in the comment of Autocomplete.php which explains how everything works.
The module developer needs to do some specific tasks to use it for his modules. So far, it's not plugged into any of the modules or the core. |