A lot of people, including myself, run pyjamas desktop in addition to compiling to javascript. I prefer pyjd during development as it provides for a very fast iterative approach. I've written some pretty sophisticated widgets and apps so far without using any JS() calls whatsoever. My app works in pyjd and in pyjs, development is a pleasure because of this.
- lex On Tue, Dec 6, 2011 at 12:48 PM, Apexi 200sx <[email protected]> wrote: > Hi, > > I understand that Pyjamas/GWT widgets were created to build a more desktop > like GUI API. > > These widgets essentially create/wrap plain HTML construct with nice OO > wrapper classes with lots of nice functionality for receiving events etc. > > What I am unsure about though is what is to be gained from wrapping existing > javascript objects you want to use such as say the geospatial, or websockets > API. > > These interfaces from what I can gather are quite adequate and I have > managed to use them directly using inline javascript ( using the JS() > function ). > > It looks like the GWT guys would create wrapper classes I am assuming only > to create a JAVA esque API and the fact that Java is statically typed and so > is required. > > The thing is I am not so sure it's worth doing this for Pyjamas, even if you > just port the GWT version of something because the API will have alot of > things unnecessary in Python/Javascript e.g. all the gettters and setters. > > Looking through the Pyjamas codebase it doesn't look like there has been > that many wrapper classes created and included that wrap Javascript > functionality outside the original GWT widget set. Is this because people > just haven't been bothered to contribute back or is it because > Pyjamas/Python is just a much better fit for interfacing with Javascript and > so people just don't think it's worth doing any wrapping and just use > libraries directly using the JS() function. > > Also why are there warnings within the comments for the JS() function > advising not to use it ? > > One reason for me wrapping a library that I can think of is for intellisense > within an IDE, but even this might not be really worth it because the API > could change and this would require changes to the wrapper classes etc. also > usually interfacing to the libs is usually only a small amount of the LOC of > the full app. Another reason could be that if there REALLY is something you > want to be careful interfacing with and REALLY want to provide a more > intelligent or simple API (FACADE) then it may be worth creating python > wrapper class. > > What are peoples thoughts on this ? > > Cheers > > > > >

