On Tue, Mar 17, 2009 at 8:10 PM, Alex Gaynor <alex.gay...@gmail.com> wrote:
> > > 2009/3/17 Filip Gruszczyński <grusz...@gmail.com> > >> >> > Are you talking about autocompletion as in what the browser does, or >> some >> > sort of Ajax autocompleter. If it's the format that's handled through >> an >> > html autocomplete="off" attribute on the input so you just need to pass >> that >> > in the attrs dictionary to a forms widget. If it's the later you'll >> need to >> > roll your own or use a solution out there like this: >> > >> http://jannisleidel.com/2008/11/autocomplete-form-widget-foreignkey-model-fields/ >> >> I think it's exactly, what I needed. Thanks a lot :-) >> >> Any chance such functionality will put directly into DJango in some >> future releases? >> >> -- >> Filip Gruszczyński >> >> >> >> > Highly unlike at best, the core developers are of the opinion that > javascript is a client side matter and shouldn't be dictated by your web > framework. > > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." --Voltaire > "The people's good is the highest law."--Cicero > serverside web frameowkr I should say. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
