On 2 May 2011 16:21, Michael MacFadden <[email protected]> wrote: > Thomas, > > Thanks for your comments. Let me ask a follow up question. Would a standard > and documented client server protocol also be required to really make this > work? I have to admit I have been talking about this a lot without really > understanding the state of the current c/s protocol. It would however seem > that this would be beneficial to those interested in making wave clients. It > would be interesting if all wave servers and clients could communicate in a > standard way, such that you could use your favorite client with any server. > > ~Michael >
I dont think it would be *strictly* needed - a separation could happen with it still using undocumented in flux protocol. But I certainly think a c/s protocol would help a lot and the sooner the better. I really think we could see all sorts of interesting variations on clients all with their own take on how to display and navigate waves. As a user, I'd also love to be able to choose my wave client like I can choose my email client. PyOfWave is working on a c/s for their wave server - it would be nice if this one and the wiab one would be the same...but thats perhaps too much to hope. -Thomas > > On May 2, 2011, at 3:19 AM, Thomas Wrobel wrote: > >> I may be a bit behind - the last ime I checked out the wiab was about >> three months back and from my perspective it seemed very integrated >> together. >> >> Back then, I attempted to create a separate project in eclipse by >> copying over the webclient directory and importing the classes it >> needed - that quickly became a spaghetti like mess of hundreds of >> classes. I asked for advice on the newsgroup a few times with >> different related problems to this task but no real answers. >> You can of course experiment with making a webclient by just copying >> the whole wiab checked out source and then selectively compiling the >> client with ant - this did work for me - but this is hardly a neat >> method as if code elsewhere changed it would get out of sycn. (and its >> not nice having a massive code tree in eclipse if your just looking at >> a tiny branch) >> >> So overall I do think it would be a good idea to move towards >> separating the client and server completely (different eclipse >> projects / repositories). I assume this would mean making a wiab >> (communication?) lib of some sort which client makers could import - >> and would need to be updated as any relevant server changes are made. >> So I understand its quite a bit of bother - but I think the pay offs >> for the project will be worth it. >> Both in terms of code neatness and increased activity. >> >> From my perspective while I understand the basic method of OT, the >> vaste majority of the server code goes over my head and I think I >> could much more easier deal with client/UI stuff. I think I'm not >> alone in this, theres probably quite a few GWT savy developers that >> could make their own wave clients or contribute to the main one if it >> was easier to get into. >> I also think it would make it easier to create (native) clients for >> other platforms - it gives a specific set of code that client makers >> would have to port. At the moment its not at all clear what out of >> wiab is strictly the minimum needed for a working client. >> >> -Thomas Wrobel >> >> >> >> >> >> On 2 May 2011 07:35, David Hearnden <[email protected]> wrote: >>> Hi Thomas, >>> >>> Could you clarify what you mean by separate (I've noticed you've mentioned >>> it a few times)? The code is already logically separate in the package and >>> component structure, so do you mean some further level of separation? e.g., >>> separate build processes, file trees, code repositories, Eclipse projects, >>> etc? >>> >>> -Dave >>> >>> On Fri, Apr 29, 2011 at 7:35 PM, Thomas Wrobel <[email protected]> wrote: >>> >>>> Another reason perhaps to separate the server code from the clients - >>>> theres still a lot of legacy stuff about. >>>> >>>> On 29 April 2011 06:46, James Purser <[email protected]> wrote: >>>>> Hrmm, the console client hasn't had any love for a long time now. I'd >>>>> suggest using the web based client >>>>> >>>>> On Fri, Apr 29, 2011 at 11:53 AM, Gokul Jeyapaul < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi again, >>>>>> >>>>>> With a beginners question again, when I start running the wave client >>>>>> using >>>>>> the client.bat - the client asks for a password. Where is the password >>>>>> configured? or Is there any default password? >>>>>> >>>>>> Thanks, >>>>>> Gk >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> James Purser >>>>> Collaborynth >>>>> http://collaborynth.com.au >>>>> Mob: +61 406 576 553 >>>>> Wave: [email protected] >>>>> >>>> >>> > >
