Closed GoogleCodeExporter closed 8 years ago
This sounds like something really worth investigating.
However, before deciding to use jQuery, see
http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
Original comment by andre.ro...@gmail.com
on 1 Jun 2008 at 9:44
Based on the wikipedia page mentioned above, the choice would seem to be between
jQuery and mochikit. Mochikit is certainly the more "Pythonic" of the two (it's
largely inspired by Twisted...), although from personal experience with jQuery I
would say that it would work just as well.
One advantage of jQuery is that the barrier to understanding it seems much
lower.
I am going to mark this as Accepted and Beyond1.0 - I think this should be one
of the
things we focus on post-1.0.
Original comment by johannes...@gmail.com
on 1 Jun 2008 at 7:50
In response to André's comments to issue 124 I am marking this as Release1.0
and I
will be creating a branch to play with jQuery.
Original comment by johannes...@gmail.com
on 2 Jun 2008 at 9:19
I will be documenting my efforts on the BetterJavascript page in the wiki.
Original comment by johannes...@gmail.com
on 2 Jun 2008 at 9:06
OK, as mentioned elsewhere, the COMET call now uses the jQuery AJAx interface
and
seems to work beautifully in Camino and Firefox 2. In theory we should not have
any
more problems with IE - can someone please test...
Original comment by johannes...@gmail.com
on 2 Jun 2008 at 9:50
This is essentially done. However, it appears to not work with Safari -
sometimes
the file loading just hangs... I'm keeping this open for now, but would be
happy to
declare it close (and require Firefox...).
Original comment by andre.ro...@gmail.com
on 7 Sep 2008 at 1:17
johannes, have you looked at http://pyjs.org ?
pyjs is _entirely_ python - not just "looks vaguely like" - it _is_ python.
any questions, contact us on google groups pyjamas-dev.
Original comment by luke.lei...@gmail.com
on 13 Apr 2009 at 9:30
This is essentially done. jquery plugins provide an easy way to add new
functionality. The problem with Safari (on a Mac) seems to have gone away now
with
the latest version.
Original comment by andre.ro...@gmail.com
on 12 Aug 2009 at 1:14
Original issue reported on code.google.com by
johannes...@gmail.com
on 1 Jun 2008 at 8:29