On Sun, Jan 29, 2012 at 3:35 AM, lkcl luke <[email protected]> wrote: > On Sat, Jan 28, 2012 at 11:47 PM, C Anthony Risinger <[email protected]> wrote: > > splitting the files up - badly - and making a dog's dinner out of > things by duplicating files and having others that maybe import from > some, have the same class name but extended functionality, such that > even the lead developer doesn't know what the fuck is going on, is a > bad idea. > > so, chalk that one down to experience: try a different route to > achieve the same goal.
if we can make it all work from one file that would be fantastic. i don't like how fragmented it is either, **especially** the overrides ... i didn't realize what was really going on until hours of wasted time (back when). but i also don't like the complete impossibility of *pretending* GWT is upstream, while simultaneously sprinkling modifications all over the place. we don't have to use the raw translation as-is, but we need to adhere to a process/toolchain. i 999% believe we need commit full-force to GWT as an upstream, or just walk away, now, because it's difficult enough already without internal chaos. there are too many engines, too many browsers, and too much cruft and obsolescence strewn about. nobody is really testing changes because it's just not feasible (btw, the mail app is completely busted when built with a non-2010 version of pyjs) ... i'm fairly certain some things have never worked since the day i looked at pyjamas; it's overwhelming to maintain with so few people. a bit of focus will go a long way. -- C Anthony
