muhaha, funny all the push you're giving towards client-side widgets.... autocomplete NEEDS to be js code, and it's probably one of the three that NEED js (just a bit or a lot) to be used fairly. I'm not a fan of inlining js (as you know already, I had strong feeling to remove any occurrence of js in python code) but hey, we got you're a fan of client-side :-P
On Friday, September 12, 2014 4:16:55 AM UTC+2, Massimo Di Pierro wrote: > > What's broken in autocomplete? Was it a preexisting condition? Another > reason for client-side widgets. Autocomplete is JS code. > > On Sep 11, 2014, at 2:35 PM, Leonel Câmara <leonel...@gmail.com > <javascript:>> wrote: > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
