ODFKit and WebODF Getting up to speed ● ODF ● ODFKit ● WebODF Discussion and brainstorming ● How would you use it? ● Office use-cases in 2010 and beyond ● Standards and Code

Open Document Format ● Format for Office Documents ● Open Standard ● All-in-one ● Still improving ● Should be as good as ● Might become language for communicating complexer documents

Open Document Format

ODFKit Scoped at Gran Canaria Desktop Summit 2009 Goal: Widely used shared code for ODF Method: Reuse WebKit technology in an ODF libray

What does WebKit provide? ● Framework abstraction ● Code generation ● Javascript binding via IDL ● XML parsing, XSLT processing ● Extensive unit testing

What will we implement in ODFKit? ● Reading ODF ● Writing ODF ● Creating ODF ● Modifying ODF ● Cherry pick lpOD and ODFDOM

Status after one month ● ZIP reading ● ZIP writing in progress Main TODO: ● Expose API to different ports

WebODF Idea resulted from ODFKit development Goal: Reusable simple ODF viewer and editor Method: HTML5, QtWebKit, OdfKit

Three Implementations

How does it work? 1)Load style and content XML from ODF 2)Import content XML into an HTML page 3)Convert styles XML to CSS 4)Enjoy

Converting styles.xml to CSS ODF Hello ODF text url(urn:oasis:names:tc:opendocument:xmlns:text:1.0); text|p[text|style-name="Elegant"] { font-style: italic; }

Missing features Nearly everything

Advantages ● Live ODF is the same as the saved ODF ● On-line office with no server side code required ● UI can be anything (HTML, Qt, Gtk, QML,...) ● No compilation ● Easy runtime document inspection ● Developing on-line is possible ● No crashing

There are on-line office suites.

WebODF can become an elegant one.

ODFKit discussion ● Ports ● Patch ● Bindings (C++ frameworks, scripting languages) ● API

WebODF discussion points ● Standards and Code ● Google Docs, Microsoft Live, ownCloud ● Development model