"If you are interested in using WebODF in your commercial product, contact KO GmbH for a commercial license."<p>I know why this kind of tactic is used, I understand people have to make a living, but I'm not keen on it, it's a form on FUD. It suggests that the A(GPL) depends on the use case, which isn't the case.<p>You can use AGPL in a commercial product as long as you adhere to the terms of the license, none of which exclude commercial use.<p>I've seen this tactic used a lot, I wish "commercial, closed-sourced, product" were used instead.<p>That said, really nice product, impressed.
This looks really interesting and potentially very useful. I skimmed the docs and took a look at the source code. This is no small project. I could not find a high level doc about how it works, though. There seems to be contenteditable element as a user events (writing) receptacle from which it generates appropriate DOM manipulation. Since ODF is a complex format, the XML is complex too, so probably editing elements directly won't be feasible.<p>There is even a desktop version. I'd really like to try if this could work as a LightTable plugin. Code looks like straight forward JavaScript and it's build with Google Closure, like LT is. I'll how to dive through the code at some point and see how hard it could be to support different XML formats, like DocBook.
This has been integrated into the new version of ownCloud (<a href="http://owncloud.org" rel="nofollow">http://owncloud.org</a>) already, allowing for collaborative editing of ODF documents. It is pretty awesome.