As Michael mentioned the client-server protocol is tightly coupled. However, WIAB allows to run UI simulation of the main wave panel without any dependence on the server in GWT hosted mode. Take a look at the waveharness-hosted ant target in the build.xml. I think this can give you an idea how to isolate the UI code from the server and run it in the hosted mode. After that you will be able to package the isolated code as jar and import to other project. Hope this helps.
2011/2/27 Thomas Wrobel <[email protected]> > Its certainly ontopic. > I heard talk of a "simplified client/server protocol" that would > probably help with this, but that could be quite far off. > I didnt really want to wait on anything when I could try to push > forward with development myself. > > As for a mobile client, a college of mine managed to get a working > connection to FedOne on a Android phone by backporting > "waveinabox-client-console-0.2.jar" to Java1.5 style code. This is, > of course, hugely out of date and doesn't work with wiab now. But I > believe the same principles apply for anyone wanting to make a android > based wave client. > > ~~~~~~ > Reviews of anything, by anyone; > www.rateoholic.co.uk > Please try out my new site and give feedback :) > > > > On 27 February 2011 16:08, Michael MacFadden > <[email protected]> wrote: > > Not sure if this is 100% on topic or not, but I do think its important > that over time we mature the relationship between the server and client and > offer clean APIs and/or reusable modules for implementing clients. I am not > sure the code or the protocol do this well at the moment. I know there has > been interest for doing thing like using WAIB as the primary server and > hooking that up to a desktop or mobile (non-web based) client. > > > > Right now the client and server are pretty tightly integrated in the code > base, and the protocol between the two is fairly specific to that pairing. > > > > ~Michael > > > > On Feb 27, 2011, at 6:21 AM, Thomas Wrobel wrote: > > > >> Ok then this is....interesting.. ;) > >> > >> So is the expected way to make a new webclient then to copy the whole > >> wiab code, server and all, and use that for a new project changing it > >> bit by bit? Or is it just not expected for anyone to make new clients > >> yet? > >> Or is none of this thought about? > >> > >> Alternatively, is it more expected to use just the jar files > >> "waveinabox-client-console-0.3.jar" to make new clients with? (Those > >> files wont work with gwt I think because theres no sourecode within > >> them, just the class's). So if I was to use those class's Id need to > >> see where the sourcecode for them comes from. > >> > >> Sorry to ask so many questions, this has just thrown me for a bit of a > >> loop as I expected it to be a rather obvious thing to try to do and > >> it was just some silly java-related error on my part holding me back. > >> > >> -Thomas > >> > >> > >> > >> > >> > >> ~~~~~~ > >> Reviews of anything, by anyone; > >> www.rateoholic.co.uk > >> Please try out my new site and give feedback :) > >> > >> > >> > >> On 27 February 2011 07:00, Alex North <[email protected]> wrote: > >>> I don't think anyone's ever tried, so we don't know if it's possible. > >>> > >>> On 27 February 2011 10:27, Thomas Wrobel <[email protected]> wrote: > >>>> > >>>> I already had wiab imported into eclipse, its in my workspace just > fine. > >>>> > >>>> I wanted to create a new project, however. Not merely edit files in > >>>> the downloaded WiaB files directly. > >>>> Theres quite a few reasons for this, but mainly it would allow the > >>>> WiaB files to be updated without me having to worry about mergeing > >>>> changes every time. > >>>> > >>>> Is it not possible to make a new webclient by importing wiab files or > >>>> adding it as a required project on the build path? > >>>> > >>>> > >>>> On 26 February 2011 21:07, Yuri Z <[email protected]> wrote: > >>>>> You just need to create a workspace in Eclipse and then import the > wiab > >>>>> project. You don't need to create GWT project first. > >>>>> > >>>>> 2011/2/26 Thomas Wrobel <[email protected]> > >>>>> > >>>>>> I've been trying to make a wiab webclient, and thought the simplest > >>>>>> way would be to start a new gwt project in eclipse, and import a > >>>>>> checked out > >>>>>> copy of wiab's source. As wiab already has a gwt based webclient, I > >>>>>> thought I'd use it as a template. > >>>>>> > >>>>>> However, merely creating a fresh gwt default project, seeing wiab as > >>>>>> required on the build path, and adding a wave object like "WaveView" > I > >>>>>> start to get an odd error; > >>>>>> > >>>>>> > >>>>>> "Our heuristic for mapping anonymous classes between compilers > failed. > >>>>>> Unsafe to continue because the wrong jsni code could end up running. > >>>>>> className = org.waveprotocol.box.webclient.client.WebClient" > >>>>>> > >>>>>> > >>>>>> I assume this has something to do with JSNI native code? I'm not > >>>>>> using any myself, so it must be in the wiab end. Isn't there a way > to > >>>>>> import wiab's code :? > >>>>>> Maybe this is more a java/gwt issue then a wave one but I'm finding > it > >>>>>> hard to tell. > >>>>>> > >>>>>> > >>>>>> Thanks, > >>>>>> Thomas Wrobel > >>>>>> arwave.org > >>>>>> > >>>>> > >>> > >>> > > > > >
