On Mon, Jan 30, 2012 at 7:34 AM, Kees Bos <[email protected]> wrote: > On Sun, 2012-01-29 at 08:16 +0000, lkcl luke wrote: >> kees - i've committed, and pushed, moving the files back to "pyjamas", >> a decision that you did not consult me on. >> >> please could you sort out the mess. >> >> thanks. > > Hmm. I think I've done 99% of the changes without consulting ;-)
yehh... grrrr :) > I think I've mentioned before, but the idea was to separate gwt based > code from pyjamas code (changes) and thus facilitate the process of > getting up to date with gwt and also ease the documentation of the > differences between gwt and pyjamas. yeah the leo project shows a better way forward, there: they use specially-formatted comments to identify code blocks that have been edited through leo. > I don't think automated conversion from java to python is possible. well you gave it a damn good shot, so you know what you're talking about. this is why any conversion has to be done _carefully_, without disrupting existing code. > You'll need a library to mimic lots of standard java libraries. yes - including decorators to take care of function overloads (or an automated rewriting system) > I do think that it's possible to get 90% or so converted. ... the rest identified within code-comment blocks so that the auto-converters know to leave it alone. > At the moment I've to much on my mind to get involved. I can say I've a > hard time to keep up to date with the messages on the mailing list. it's ok - i believe i took care of moving most of the code back. i was just annoyed that there was quite a bit of code duplication and that things were hard to find. l.
