On Fri, Dec 21, 2012 at 10:34 AM, Sarvi Shanmugham <[email protected]>wrote:
> I see 2 areas that coud use some effort > 1. Upgrade the GWT widget set to the latest GWT 2.5 > This is a stated goal of the current benevolent dictator of pyjs, Anthony. So you are in good company regarding that feature request. Although instead of upgrading the current widget set, this would be a separate module. We can't abandon support for people who have invested quite a bit into the current widget set available in pyjs. Personally, I am not interested in this work. I prefer to build custom widgets as needed. I only rely on a handful of low level GWT widgets to subclass from and then add my own functionality. See examples: https://github.com/damoti/damoti-client For new users I can see how having GWT 2.5 support can be a great selling point for the framework so I definitely support this effort in spirit. 2. Work on the compiler optimzations/redesign on pys or pyjaco - an > orthogonal question > I have a prototype of emulating pythons dynamic variable lookups in the object/class inheritance graph by re-using javascript prototype machinery. It would take a lot of work to integrate this into Pyjs but the benefits would be significant I think. Also, Anthony is working on integrating waf. Those are the two major efforts that I'm currently aware of. > 3. Work on the java2python translator to fully automate and/or generate > more optimal python code. > #1 and #3 are basically one and the same. > I am leaning towards tasking the resource to 1 above and maybe 3( towards > more complete automation if possible). > I don't think #1 and #3 can be separate tasks because #1 is the end production of implementing #3. > And from what I am hearing, 2 above is usable now, and I could wait to see > where pyjaco heads before deciding on what needs to be done, at a later > date. > > What do you think? > Everything is usable. In fact, you could just use pyjs as-is without any effort put into the project. You'd just have to work around things that aren't supported, which is doable. You don't *need* GWT 2.5 support, the widgets that are there now are more than adequate to build complicated applications, you may have to write some of your own code to handle edge cases but it works. Trying to decide how you want to help Pyjs before you've started on your app and hit a road block is a bit pre-mature planning. You may start using pyjs and decide it actually lets you do everything you need. Or you may decide it could do something better and than fix it. - lex --
