Introducing ODF to mobile platforms

Uploaded on

Open Document Format (ODF) due to a wide spectrum of software environments including office document editor suites is increasingly popular. To extend the list of platforms supporting ODF, as editors …

Open Document Format (ODF) due to a wide spectrum of software environments including office document editor suites is increasingly popular. To extend the list of platforms supporting ODF, as editors of concurrent formats (MS Office) are already available on mobile platforms, development of an ODF editor runnning on mobile devices is in need.

The goal of our project is to develop an ODF based data model and a set of supporting tools to create a user-friendly mobile editor suite. Considering the hardware and software resources available on a mobile device, a schema controlled editor is under design which is able to provide most of ODF features while editing standard conforming documents on the mobile site. As mobile devices range from cell phones through smart phones to PDAs, and these platforms have different resource limits, our editor has to be able to adapt to the current device.

To reach our goal, we investigated the resource need of test editor software, of primitive operations which transforms documents in a standard conforming way, and selected those which may be performed easily on a mobile device. We plan to extend our software suite with server (desktop) site components in order to distribute office documents over desktop and mobile site. The distribution involves fragmenting and tranforming documents between ODF and our data model.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Imre Barna, Péter Bauer , Kinga Bernád, Zsolt Hernáth, Zoltán Horváth, Balázs Kőszegi, Gergely Kovács, Tamás Kozsik, Zsolt Lengyel, Róbert Roth, Sándor Sike , Gábor Takács Eötvös Loránd University Introducing ODF to Mobile Platforms
  • 2. Agenda
    • Project goals
    • 3. Mobile platforms
    • 4. Chosen software platform and its limitations
    • 5. Prototype tools and tests
    • 6. Document handling techniques
    • 7. Conclusions
  • 8. Project goals
    • Creating an office software running on mobile devices, supporting ODF
      • Adaptive to mobile features
      • 9. Controlled by document schemata
    • Transfer documents between desktop and mobile device
  • 10. Mobile devices
    • Wide range of handheld devices
      • Mobile phones
      • 11. Smartphones
      • 12. Personal Digital Assistants
    • Different hardware and software capabilities
    • 13. Different office software supported
  • 14. Mobile phones
    • For everyday use, focusing on phone calls and text messages
    • 15. Different mobile operating systems
    • 16. Limited input interface
    • 17. Small screen
    • 18. Small batteries
    • 19. Slow processors
  • 20. Smartphones
    • For business use
    • 21. Physical keyboard
    • 22. Large screen
    • 23. Stronger processors
    • 24. Stronger batteries
    • 25. Software for displaying office documents
  • 26. Personal Digital Assistants
    • For business and entertainment
    • 27. Physical and/or virtual keyboard
    • 28. Large screen
    • 29. Powerful processor
    • 30. Strong battery
    • 31. Office suite with limited features
  • 32. Software platform
    • Common platform for all devices
    • 33. Java ME
      • Mobile Information Device Profile 2.0
      • 34. Connected Limited Device Configuration 1.1
    • Limited display capabilities
      • 3 font faces
      • 35. 3 font sizes
  • 36. Prototype tools
    • Prototype text editor
      • Understands basic ODF features
      • 37. Paragraphs, font styles, basic lay-out algorithm
    • Prototype spreadsheet editor
      • Cell styles and formats, ranges
    • Performance testing
      • To identify critical features
    • Feature tests
  • 38. Test methodology
    • Created documents with different sizes and features
      • From 1-paragraph notes
      • 39. To 50 pages articles
    • Created scripts focusing on special features and stress testing
      • Individually tested text manipulation
      • 40. Style editing and applying
      • 41. Combined tests
  • 42. Considerations
    • We cannot handle too long documents
      • Creating the layout for a 10-page document lasts minutes
      • 43. Editing spreadsheets with more than 100*100 cells leads to OutOfMemory
    • The critical operation is creating the layout and rendering the document
    • 44. Separate style and editing scripts are faster than combined tests
  • 45. Large documents
    • Splitting up documents
      • Document server running on a desktop or server machine splits up documents
      • 46. Using different windows embedded in each other
  • 47. Separating layers
    • Layering documents
  • 53. Adaptivity
    • Some features are turned off dinamically
    • 54. Different ODF schema derivatives are needed for different feature sets
    • 55. Document reduced dynamically to conform the selected schema derivative with markers
  • 56. Features supporting adaptivity
    • Small performance test suite runs on the mobile
      • Checks physical parameters
      • Measures the speed of some critical operations
        • creating visual layout
        • 58. text processing
        • 59. file operations
  • 60. Selecting the appropriate schema
    • Based on the device's capabilities and user requirements the set of features is selected
    • 61. Result is sent to server site where a schema derivative is selected
    • 62. Schema derivations are generated in advance with a schema transformation tool
      • Derivations are consistent transformed ODF schema versions
      • 63. Features may be removed or limited (recursion depth)
  • 64. Transforming documents
    • Documents must be transformed to conform the selected schema
    • 65. Sub-trees may need to be detached from the document tree
    • 66. Typed markers are used in place of detached sub-trees
      • Marker types enables consistent handling of documents
      • 67. Visualization of placeholders of removed elements
  • 68. Fragmenting documents
    • Transformed document layers are split into fragments
    • 69. Fragments are edited on mobile site
  • 70. Integration of documents
    • Edited fragments are integrated into a document conforming the selected schema derivative
    • 71. Removed sub-trees are restored from marker database
    • 72. Integrated document is transformed back to desktop ODF format
  • 73. Defining schema derivatives
    • Schema derivative is generated for each predefined feature set
    • 74. Feature sets are based on evaluated use cases
    • 75. Schemata are derived from ODF schema
    • 76. Schema transformation is automated
      • Expressed in Schema Transformation Descriptive Language
    • STDL is the RELAX NG embedding of the context-sensitive aML macro language
  • 77. Conclusion
    • Prototype office software created and tested on a wide range of mobile devices
    • 78. Solutions found for the main problems:
      • Splitting documents with embedded sliding windows
      • 79. Splitting schema into layers
      • 80. Using adaptive schema and feature set
    • Schema derivatives are defined supporting different feature sets
    • 81. Schema controlled editor is to be implemented