Sean Schofield wrote:
I will try and look when I get a chance. Matt should also take a look
at it since he wrote all of the javascript for inputSuggest.
Based on Werner's sample page they are *very* similar. I agree that
inputSuggest can't support large data sets but that might just be a
matter of taking the AJAX stuff from Werner's component and putting it
into inputSuggest.
I would not recommend to use my javascript code at least not the one
which is the current production, it is not based on proto but more a
qickly fixed dirty hack refactored out of the blueprints and with the
component leaks removed and with ie compatibility added. I never was too
happy with it and have been working in my spare time on a rewrite which
is MVCed, which is not finished yet. (moving slowly due to a second job
currently)
Two days ago I saw the Prototype lib based autocomplete code Martin
added to the sandbox control, that stuff is lightyears ahead from my
dirty hack and even my MVC rewrite, although it leaks components (which
can be fixed easily by not referencing the components directly from an
object scope but using their ids as references), it is much much better
implementationwise than mine.
No rush on this IMO. Both components should stay in the sandbox. My
thinking is that if we refine both of these components intensively we
will end up with two of the exact same component.
+1 to that, before any ajaxing stuff is moved into the main core the
project also has to settle for a solid backend foundation.
Maybe the whole stuff never should go into the core itself, the problem
I see with ajax is, that you cannot avoid javascript, and one thing
which every component should adhere to is the non javascript flag in the
web.xml, am I right?
Maybe we need an entirely different submodule of components here, some
which force you to go the html/javascript way.
