Open GoogleCodeExporter opened 9 years ago
This would probably be best done as a plugin for Jx.Field.Text (either a
straight
plugin or an adaptor.... not much difference besides the naming scheme). Just
to
clarify that if you plan on linking this with a store in order to take
advantage of the
protocols then you should probably make it an adaptor.
Jon
Original comment by jbomgard@gmail.com
on 27 Mar 2010 at 9:25
Creating this as an adaptor is a good idea. I tried out some other autocomplete
scripts that can either use a local store or fetch it by ajax. I think this
should be
a good alternative for us too.
Do you think there should be an adaptor for jx.field.text that takes a store
reference in the options (which has its protocols and strategies if needed?). I
recognized that an adaptor extends jx.plugin - so there wouldn't really be a
difference between these two in that case here except that an adaptor already
has a
store reference?
Could this adaptor be useful on any other jx element?
Original comment by conrad.b...@gmail.com
on 28 Mar 2010 at 2:31
I've used http://digitarald.de/project/autocompleter/ a few times, its pretty
decent and might be a useful
starting point - the functionality is quite nice and I think could be adapted
to JxLib moderately easily.
Original comment by pagameba
on 28 Mar 2010 at 7:06
I had that one in mind too because I like it very much. He uses this in a
textarea
just like in an input field - we could do that too ;) I will see what I can do
until
the middle of the week to show you some results.
Original comment by conrad.b...@gmail.com
on 28 Mar 2010 at 7:56
Conrad,
Yes the only real difference between a plugin and an adaptor is the presence of
a store
and the fact that an adaptor is meant to take that store and create or fill a
widget of
some kind.
Jon
Original comment by jbomgard@gmail.com
on 28 Mar 2010 at 8:18
Conrad, this is a good idea and if you work on it we will include it but it was
already discussed in another issue
that this and other such plugins/adaptors would be worked on after we get 3.0.
If you have time, could you work
on some of the 3.0 milestone issues?
Original comment by pagameba
on 30 Mar 2010 at 12:35
I thought about this too and had so many ideas how this feature could much have
more
advanced features (also like the yui autocomplete for example (see it in action
in
the search field at last.fm). I was kind of overwhelmed by what I had in mind
and
found out that this would be very hard to press this into the 3.0 release. The
result
would definately be an autocomplete field which isn't rudimentary that cool as
I have
it in mind ;)
Lets put this to the end of the stack and focus on more important features for
now. I
will take a closer look over open issues and see where I can help.
Original comment by conrad.b...@gmail.com
on 30 Mar 2010 at 12:46
Moved to Lighthouse:
http://jxlib.lighthouseapp.com/projects/71243-jxlib/tickets/25-jxfieldautocomple
te
Original comment by jbomgard@gmail.com
on 5 Mar 2011 at 7:13
Original issue reported on code.google.com by
conrad.b...@gmail.com
on 27 Mar 2010 at 6:08