On Sat, Jan 28, 2012 at 6:58 PM, C Anthony Risinger <[email protected]> wrote: > On Sat, Jan 28, 2012 at 12:21 PM, Jeffrey Van Voorst > <[email protected]> wrote: >> >> What happened to slow it down? Support of more browsers? or a lot more >> items get put in the js files to support more of the python language? >> Note I am assuming it is the download time, but I suppose it could >> also be initializing the javascript on the page itself. Is there much >> that could be done without breaking the "compatibility" between GWT >> and pyjamas? In other words, if radical changes are made, one might >> not be able to convert the Java GWT code to Python as easily as is >> currently done. > > the modules we actually split into a gwt namespace in the belief it > would be easier to stay in sync with upstream in the future.
btw i'm getting fed up with advertising gwt within the pyjamas codebase. i'd appreciate the library/gwt/* being removed. l.
