Another idea for a shorter-term solution for this is, instead of web-based LibO, someone make a synchronization software that relay changes between off-line ODF and online Google Docs, a la Google Cloud Connect for MS Office.<div> <br></div><div>Working with Google Docs is somewhat painful because it still lacks many familiar features. An ideal solution would be to use a fat client that store the ODF in the cloud. Many users can use the fat client to edit the document at the same time while the synchronization software relay the changes made by different users. Google Docs would be nice as the cloud storage except that ODF lost a lot of formatting when convert to Google Docs. <br> <br><div class="gmail_quote">On Mon, Jan 24, 2011 at 10:03 PM, Michael Meeks <span dir="ltr"><<a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Hi Ged,<br> <div class="im"><br> On Mon, 2011-01-24 at 15:06 +0100, Ged Wed wrote:<br> > whats the support for doing a web based open office ?<br> > Ajax based with a restful JSON or XML model.<br> <br> </div> Well, it is not an impossibly bad idea :-)<br> <div class="im"><br> > I am asking because this seems like such a good move.<br> > Libre Office would then have a very compelling solution that neither<br> > google Docs or MS Office can really compete against.<br> <br> </div> Riight; except they are already in the market place - which makes us at<br> least two years away from there, even if we had a product now :-)<br> <div class="im"><br> > - what is important is that both the fat client and the thin client<br> > are both adapted towards the client / server model together. This<br> > makes both version easy to maintain, change control, testing etc<br> <br> </div> Well - since we have a fat client; I would personally focus on two<br> things:<br> <br> a) feature parity between fat and web client<br> + no-one else does this.<br> + fat client for off-line, web for (who? ;-)<br> <br> b) abandon hope of off-line web editing: that's why you have the<br> fat client right ? :-)<br> <br> which means, we have to re-use the fat client on the web server; that<br> means all sorts of good things: we need to make it smaller, more<br> reliable, faster to start, etc. etc.<br> <br> and it also makes some things a lot easier; IMHO doing remote rendering<br> by cutting at VCL and proxying rendering (wherever possible) to a remote<br> canvas, -might- work in semi-linear time.<br> <br> I'm thinking a re-hash of:<br> <br> <a href="http://blogs.gnome.org/alexl/2010/11/23/gtk3-vs-html5/" target="_blank">http://blogs.gnome.org/alexl/2010/11/23/gtk3-vs-html5/</a><br> <br> Though of course VCL's rendering APIs are (now) substantially less<br> pleasant than gtk+'s.<br> <br> HTH,<br> <br> Michael.<br> <font color="#888888"><br> --<br> <a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a> <><, Pseudo Engineer, itinerant idiot<br> </font><div><div></div><div class="h5"><br> <br> _______________________________________________<br> LibreOffice mailing list<br> <a href="mailto:LibreOffice@lists.freedesktop.org">LibreOffice@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/libreoffice" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libreoffice</a><br> </div></div></blockquote></div><br><br clear="all"><br>-- <br>_/|\_ Samphan Raruenrom. Open Source Development Co., Ltd.<br>Tel: +66 38 311816, Fax: +66 38 773128, <a href="http://www.osdev.co.th/">http://www.osdev.co.th/</a><br> </div>