Hi Brian, > Can you please provide reasons why it should?
Sorry for the short report... Now, a detailed report:
In "ajax_select/js/ajax_select.js" file:
<!-- CODE -->
$("#"+name).trigger('didAddPopup',[html_unescape(newId),html_unescape(newRepr)]);
<!-- END CODE -->
"trigger" is a method of jQuery API [0].
[0] http://api.jquery.com/trigger/
In "ajax_select/templates/*" files:
<!-- CODE -->
$("#{{html_id}}_text").autocomplete('{{lookup_url}}'...);
<!-- END CODE -->
It's a autocomplete call and it is deprecated [1].
But, the new version will use jQuery-UI, that is the
libjs-jquery-ui package.
[1] http://code.google.com/p/django-ajax-selects/issues/detail?id=46
In "ajax_select/fields.py" file:
<!-- CODE -->
from django import forms
<!-- CODE -->
django-ajax-selects should depends on python-django, too.
> At the moment, nothing in this package references the libjs-query
> except for the documentation. It was my feeling that if any package
> use django-ajax-selects, it will be these packages that reference
> jquery, and as such these packages should be depending on libjs-query.
>
> It would be nice if django-ajax-selects could reference the js files
> itself, but unfortunately that is going to vary from site to site. In
> fact, static files such as jquery could be found on another host.
>
> Maybe suggests or recommends would be better?
>
> Any comments for improvement?
The ajax_select.js and templates are not documentation files.
Does django-ajax-selects work without Django, jQuery and
jQuery-autocomplete? It doesn't. So, it depends on these libs.
Cheers,
--
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com
signature.asc
Description: This is a digitally signed message part
