Ok, let me explain which are our necessities to integrate and use the webclient that probably are not common.
- We need to open some waves at the same time (as GWave does) because we have different "spaces" and WIAB client one of them (your inbox, your individual point of view) but we have group wave pages, and maybe we are editing a personal wave, but also we want, in the group space, to edit another doc wave. - we use another kind of widgets for buttons, dialogs, and well we don't want to use windows.prompts, alerts, or turbulences popups, or adapt then to our current interface. Many of these current web client widgets just scary our users. - we need to enable or disable buttons in the toolbar depending on the content what your are editing. - we want to add custom buttons (probably not related to WIAB) as publish, share, etc. - we need to integrate better the avatars and user profiles which our own system. For instance, we show your contact presences (as GWave does) using or XMPP client/roster in the rest of the application (but not in WIAB). - we want to integrate a easy way to add participants, or to contact them (we use a suggestion box in other parts of our code). The remove participant button only give us, problems. - we use additional history token hashs (more only the WIAB wave history tokens) for things like #signin and so on. And we want to enable pretty urls (or shorter) for some public (wave) contents. - we use tooltips (with more rich content) instead of plain html titles. - we are looking with interest in the UI mocks: https://sites.google.com/a/waveprotocol.org/wave-protocol/protocol/web-client-ui-mocks as we thing that addresses some of the usability problems that make Google Wave fail. - We want to use the toolbar editor or the participant list not always in the same position and with the same look. So currently I found my self patching the webclient code to try to do a 1% of the previous list and well ... it's not easy. Compared with the work that I spend to adapt the server code to our needs, thanks to Guice. We'll from my experience with GWT, doing a big modular/extensible GWT app without dependency injection or something similar is quite difficult. So we did also a IoC library we used (pre google-gin): http://code.google.com/p/suco/ So, google-gin comes to my mind every time I try to do something with the client, but, maybe we can find other solutions. Bests, Vicente El dom 20 nov 2011 03:46:35 CET, Thomas Wrobel escribió: > 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 <v...@ourproject.org> 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] >> >> >> >> >> >> >> > -- Vicente J. Ruiz Jurado http://comunes.org http://ourproject.org http://homes.ourproject.org/~vjrj/blog (@vjrj) "Todos somos muy ignorantes. Lo que ocurre es que no todos ignoramos las mismas cosas." [Albert Einstein]
