Il giorno mar, 08/06/2010 alle 16.14 +0200, Marko Niinimaki ha scritto: > the keyword lookup is very nice! But there is something in the GUI.. > maybe it's because of my browser (Chrome): > typing: > lepto > -> a selection of keywords like lepton show up > -> click on lepton in the list > -> in the search box, the word remains "lepto", it does not become "lepton"
Indeed (I am also using Chrome). It becomes "keyword:lepton, " if you press enter. Just a note, I see that this is enabled only when you choose "keyword" from the list of fields (correct me if I am wrong). But it then add "keyword:" prefix in front of the autocompleted keyword. This is kind of causing broken search results, as it's like searching for "keyword:keyword:lepton"). While we are at that: To summarize the current situation of auto-completion, we do now have: * autocompletion of tags from Victor, based on a JQuery plugins, backed from tags tables * autocompletion in BibEdit from Marko, based on custom javascript, backed by dynamically allocated knowledge bases * autocompletion in search engine from Roman, based on ???, backed on bibconvert keywords (from MARC?) and I would like to implement WebSubmit drop-down menus based on JQuery, backed by knowledge bases. So shall we uniform our effor on a common solution (at least for the front-end part) in all using the same javascript code? I just noticed tha autocompletion got official into JQuery UI (1.8.x): <http://jqueryui.com/demos/autocomplete/> which might have a good chance to have robust support from the community in the future. What do you think about it? Regardless of which autocompletion js library we are going to, shall we choose just one, and someone volunteers for refactoring his code out into a miscellaneous library that can be used by the other. In particular it would be great IMHO to have a ready to use text field that can be easily backed by e.g. bibknowledge out of the box and that can be used everywhere... What do you think? Cheers, Sam
