I like the idea of a backend that can dynamically scale functionality from server side rendering to client side rendering based on the computing device, but I wonder if its the correct approach.
Given that it's much easier to write back-end systems that deliver static HTML that work on all browsers than to write rich frontend systems that are dynamic and interactive, surely choosing this path dooms the gwt front end to a dubious future where open source contributors work on the easier server side rendering code, make it look great, and the js frontend lags in functionality and is eventually dropped. Then, on top of that look at the front ends people have already made using the data api; basically server side rendered apps. I know there's a goal to make WIAB a generic product that runs on everything and so on, and things like the WebSocket support make IE support a real hassle, but................ why not just make the data api top notch and leave people to write other front ends for it using that, and focus of delivering a wave.google.com like experience in WIAB? :) ~ Doug. On Oct 19, 12:55 pm, David Hearnden <[email protected]> wrote: > Hi all, > > We've just published the design document for the Wave-In-A-Box > client's wave panel! > > For Wave-In-A-Box, instead of re-using the wave panel from the Google > Wave client, we opted to use a new design that was already underway. > This redesign, code-named Undercurrent, came after many lessons were > learned about what worked well and what did not work well with the > architecture of the original wave panel. > > http://www.waveprotocol.org/protocol/design-proposals/new-wave-panel-... > > Questions and feedback on the document are most welcome. Most of the > design has already been implemented and checked in, and you can use > the new wave panel right now (instructions at the end of the > document). A few features are still missing, and will be added in the > coming weeks. > > Cheers, > > -David -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
