I tried out gwtpyler on GWT2.4 and it seems to work with but a few warnings/errors(?) issued.That's a great first step. Thanks.
Your document says "The contents of src/java/__init__.py should go to ... the translator __pyjamas__ for pyjs. In the latter case some additional fixes are needed for POST/PRE INC/DEC. ' I can find translator_proto.py in the pyjs code (and translator_proto-KEES.py and translator_proto-KLUEV.py) but __pyjamas__ is an instance of the __Pyjamas__ class. Should the src/java/__init_.py be added to that class or something else? Any hints or an procedural outline on what to do with the gwt tree structure with the .py files created from the java source and other necessary modifications? I thought they should most likely go under the pyjs/library directory. But should they replace everything in that directory? (There are a variety of possibly handcrafted DOM...py files, e.g. DOM.safari.py that are still needed or must be created by hand for gwt 2.4. (?)) Regards, Norman On Sat, 2011-06-25 at 17:26 -0700, Norman Shelley wrote: > I downloaded and built javapyler and would like to convert some gwt or even smartgwt widgets to python for use in pyjamas. I do best getting started with concrete examples, so are there any more examples available of setting up the cfg file and converting actual some actual gwt widgets to python than are on the code page of this link? > http://sourceforge.net/p/javapyler/home/javapyler/ > ... I've added a liiiittle bit of documentation in README and the example configuration file gwtpyler.cfg. Note that I haven't really translated gwt parts yet (java code is parsed and look all right, but I didn't try to load that in python/pyjamas). - Kees --
