Anthony, > there have been many changes custom to pyjs that make the mapping task > next to impossible. my thought at the moment is to "freeze" the > "pyjamas" library as-is, and call it round one, this way people don't > need to change their apps. this doesn't mean it won't be updated or > improved, but it will never progress beyond GWT 1.x. for 2.x, we will > find a way to maintain a mostly pure translation, with pyjs changes > layered on top. > > this will be a part of ongoing work to break the UI libraries out of > the main distribution; i want to make it clear that 3rd party > implementations/frameworks are both possible *and* encouraged ... GWT > is just one path of many.
Some questions: 1. How can we integrate several 3rd party frameworks? (What if the features overlap?) 2. What parts (of widgets etc.) should be regarded as "core pyjs", what 3rd party? (i.e. what can be "generated" from another source in theory, what not?) 3. Can we try automating the conversion of GWT widgets to Pyjs? (Maybe set up a process that allows injecting code adaptions after an automated conversion with java2py [a], ideally supported by unit tests or whatsoever?) [a] https://github.com/pyjs/pyjs/blob/master/contrib/java2py.py It would be nice to see Pyjs being a very close sibling of a 3rd party framework (be it GWT or something else), with the main advantage we all value: Python. This can only be done in a somewhat automated manner, can't it? Peter
