Closed GoogleCodeExporter closed 9 years ago
As far as I understand about both skulpt and pyjamas they are different.
skulpt - runs python at client side (ie, web browser).
pyjamas - converts python code to javascript at server
Original comment by bijumail...@gmail.com
on 15 Aug 2009 at 7:44
pyjamas - converts python to javascript on server-side _because_ we don't have
skulpt.
but that's exactly what we have wanted to do, for a long time: compile the pyjs
compiler itself into javascript.
it's the port of Grammargen, which compiles to an AST, that allows that.
from the skulpt side, you can take advantage of the pyjamas DOM code, take
advantage
of the pyjamas implementations of Dict, List, tuple, string, set; take
advantage of
the math library, sys library, md5 library; take advantage of the pyjamas.ui
widget
set and much more.
Original comment by luke.lei...@gmail.com
on 15 Aug 2009 at 8:26
That'd be something like "take stardard library stuff from pyjamas into skulpt"
(and
then implement the rest of stdlib that makes sense to have in a browser) and
then
turn pyjamas into a "Python UI Library for the Browser" ?
Original comment by telenieko
on 17 Aug 2009 at 8:48
> That'd be something like "take stardard library stuff from pyjamas into
skulpt"
yep.
> (and then implement the rest of stdlib that makes sense to have in a browser)
over the past 3 years we've collectively done that already, yep.
int, string, dict, list, tuple, set, math, md5, sys, gtk (yes, that's right, gtk!).
> and then turn pyjamas into a "Python UI Library for the Browser" ?
yep, that's right. 100 different widgets are available. Image, Label, Grid,
HorizontalPanel, DialogBox, HorizontalSplitPanel etc. etc.
but we're not stopping there: we recognise the value of python-to-javascript
compilation, so in various experiments have back-ended pyjs into
python-spidermonkey,
pyv8 and spidermonkey.
this we've been doing in order to do two things:
1) test the compiler, stand-alone, on the command line
2) provide a python accelerator similar to python-psyco
also on the roadmap for a long long time has been doing "eval" and "exec" - in
the
browser.
that's where skulpt comes in. unless skulpt is designed with other
python-to-javascript projects in mind (of which pyjamas is just _one_ - there
are two
more that i know of excluding skulpt!) i will simply absorb skulpt in its
entirety
into pyjamas, some time in the next few months. so it would be very good if
skulpt
could be templatised in some way so that the Grammargen port could output
slightly
different javascript.
Original comment by luke.lei...@gmail.com
on 17 Aug 2009 at 9:22
Yes, I'm aware of pyjamas, I used it a while back (and made some posts to its
list). I
agree there's the possibility of longer term merger/collaboration/something,
but I'm
going to close this issue because it's not actionable. If there's specific
changes
you'd like to see in skulpt you can open issues for them, or perhaps start a
discussion
on the maillist.
Original comment by sgraham
on 25 Aug 2009 at 10:58
yes - willdo, i'd like to use grammargen to generate pyjamas-compatible
javascript
(or perhaps, ironically, even python which then gets handed to the pyjamas
compiler!)
Original comment by luke.lei...@gmail.com
on 25 Aug 2009 at 12:44
Original issue reported on code.google.com by
luke.lei...@gmail.com
on 11 Aug 2009 at 7:09