Introducing ODF to mobile platforms


Published 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 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.

Published in: Technology
  • 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

No notes for slide

Introducing ODF to mobile platforms

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