I should have given some more context, basically we have a website that is built using GWT in eclipse and we were hoping to leverage some of the of the work already completed by the community. We want to embed the undercurrent GUI into the website, without having to tear our current code line apart too much :) I really wanted to know if anyone has been developing their own website with that level of integration, how they went about it and if they have been able take parts of undercurrent and drop them straight into their own site. I'm aware that there is a Restful api but I'd prefer to automagically get the undercurrent editor without too much of a refactoring. On the same topic if anyone has done this then how do they mesh the two code lines togther? I had thought that maybe I should just take a snapshot of WIAB and work from that but I'd also like to continue to recieve updates from the community..
One of my real concerns has been around how to link our current user accounts to those of wave, we have a lot of user data that we keep and I'd prefer not to have to maintain two different user account systems, It'd be nice to know if anyone has tackled this... Cheers Ben On Mon, Dec 6, 2010 at 2:53 AM, Chris Harvey <[email protected]> wrote: > Ben, > > On 6 December 2010 08:09, Ben Hegarty <[email protected]> wrote: > > We've been keen to use wave as the basis for the communications in a new >> web site that I've been working on, I'm curious if anyone has integrated the >> WIAB code with their own web site code and continue to update from the main >> WIAB repo (I imagine this could get hairy atm as it looks like wave is still >> under heavy dev), or whether its just better to wait until the first rev is >> released? >> >> > It really depends upon what you mean by "integrate". The Wave architecture > (of which WIAB is an implementation) provides a powerful (although IMO > complex, incomplete, and cumbersome) array of methods to 'integrate': > gadgets (for inclusion of, effectively, bolt-on UI functionality); robots > (useful for server-to-wave server purposes); embedding (for dropping a wave > view into an existing site); and the Wave Federation Protocol (for wave > server to wave server) communication. > > When I started the iotaWave project, it took many (many) weeks of actual > development to work out the implementation, programming, and functionally > issues around each of these possibilities. At the end of the day, we > designed what we wanted to achieve and then we went back to see how the > technology could work for us. > > For us: Gadgets are useful (so long as they follow the OpenSocial API). > Robots serve little purpose. Embedding looks pretty but isolates wave > technology from other UI functionality. WFP is absolutely critical. To > achieve our UI and server-to-server communications we are 'standardising' on > one comms protocol (we call RFDP) that combines client-server and > server-server into one RESTful JSONish API. > > You need to sketch-out (a lot of) screen layouts to help visualise just how > your app/site is going to look. That helps you to then determine a > functional requirements architecture. Only then will you be able to > ascertain how specifications and implementations of Wave Tech will help you. > > Over the past few months, I have spoken to many people who want to 'simply' > integrate Wave Tech into their apps. Whilst, on the surface, its all very > exciting and hyped, the reality is that it is(/can be) a lot of "real > computer science". > > Guys like you telling "the wave development community" what you want in > your real-world scenarios is very important. The dog must wag the tail. > > HTH > -- > Chris > iotawave.org > Singapore > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- blog:http://thelifeofbenhegs.blogspot.com/ phone: +447767-322-122 -- 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.
