Google-gin sounds like it could simplify and separate out (at least too some extent) the client code.
However, is not the intended roadmap to have a standardised client/server protocol.? A wave equivalent of pop3/imap? If thats the case, I think thats all thats needed. Gin might be redundant. A little "wave interface" lib could go a long way, letting java developers make their own clients, and providing a very clear template for porting to other platforms and code base's. As a GWT developer I find making front-ends relatively easy (and have made quite a few online apps and games), yet the wave source code keeps defeating me when I try to work with it. I feel theres a lot of developers probably at only my skill level - very willing to help but hitting a skill barrier and not being able to invest the time to get past it. This is all assuming Gin isnt useful as a intermediate step. [/2 cents] ~~~~~~ Reviews of anything, by anyone; www.rateoholic.co.uk Please try out my new site and give feedback :) On 20 November 2011 02:00, Vicente J. Ruiz Jurado <[email protected]> wrote: > Hi there, > > We have the necessity to start to improve the webclient itself. > > What do you feel about: > - starting the internationalization of the client messages, toolbar, > panels, etc. > - starting (or try) to use google-gin to allow adaptations of the > client, reusing of code, etc > > I can propose patchs for that. > > Bests, > -- > Vicente J. Ruiz Jurado > > http://comunes.org > http://ourproject.org > http://homes.ourproject.org/~vjrj/blog (@vjrj) > > "Diffused knowledge immortalizes itself" [Vindicię Gallicę, Sir > James Mackintosh. 1765-1832] > > > > > > >
