May I also suggest adding the Client/Sever protocol onto the list of potential things to do?
Its my own personal bias as I need it for my own project (arwave.org) in which I wish to make a custom client for a specific purpose, while still being compatible with all WIAB servers. It would also allow clients to be made more easily for non-web platforms (phone,native desktop etc). Also, as a GWT developer I feel webclient developments in general could progress much faster with a clean separation between the server and client code. (as I am pretty good at making webapps, guis etc, but cant for the life of me get my head around the WIAB code base). Of course, we all have our preferred things we want Wave to do, but it would be nice to see c/s on the list at least. Thanks -Thomas Wrobel ~~~~~~ Reviews of anything, by anyone; www.rateoholic.co.uk Please try out my new site and give feedback :) On 17 January 2012 18:50, Yuri Z <[email protected]> wrote: > How about adding other options to fundwiab.com? I think Flattr > <http://flattr.com/>is the most convenient method for micro payments. > > On Tue, Jan 17, 2012 at 7:36 PM, Kirill Kostyuchenko > <[email protected]>wrote: > >> Please apply attached patch to the main index.html. >> >> I added links to WaveImport utility and http://fundwiab.com site. >>
