Re: GSOC idea: integrating webodf with collaborative editing
ajung <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
Paul Roeland-2 wrote > one idea that might fit inside a project: > > - http://webodf.org is a pretty nice editor/viewer for ODF formats > > - and has initial support for collaborative editing, and track&trace > > - for instance the people from Owncloud have an integration with it now, > that uses Ownclouds versioning as the 'versioning backend' for > track&trace. > > what I would really like about a proper integration into Plone (so the > authornames are taken from Plone, etc) is that you could have editing > and track&trace done without installing extra services like etherpad or > xmpp, and without sending it over external servers like with togetherjs > and friends. Post-Snowden compliant ;-) > > It looks project-sized enough for a student that has some > javascript-skills and willingness to look into how Plone's membership > and versioning tools work could get that done in the allotted timeframe. -1 Managing website content with is basically HTML with an non-HTML editor is basically nonsense. Converting between two formats forth and back will always result in issues with structural and styling information. Such a conversion is never lossless. Look at a site like http://www.dgho-onkopedia.de/de/onkopedia/leitlinien/leitlinien_overview (one of our customers) where the primary content is authored in Word and then converted to X(HTML). The structure of the documents are pretty easy however there is no real way to get a reasonable roundtrip between Word and HTML. The functionality of ODF is completely over the functionality of HTML. So a WebODF based editor must be completely stripped down (functionality-wise) in order to provide on the functionality that you can map 1:1 to HTML through some transformation. I don't know much about the WebODF implementation - but I strongly believe that a collaboration solution for authoring text requires an up2date representation of the current content on the server backend (as it is likely implemented by Google Docs). I prototyped something using Nimbudocs Editor some months ago: http://www.youtube.com/watch?v=lwVcrSi-qwI And last but not least: WebODF is in a very early stage at the moment and the overall impression is fragile. A simplar project has/had the same problem: PDF.js which had some hype a while ago...the project is still stuck, working to some degree but in general it has various issues. My unimportant 2 euro cents.... -aj -- View this message in context: http://plone.293351.n2.nabble.com/GSOC-idea-integrating-webodf-with-collaborative-editing-tp7570154p7570156.html Sent from the Core Developers mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk