OpenOffice.org Online Resources

320 views

Published on

OpenOffice.org have been using dumb clients like other applications like Firefox. Is time to upgrade themselves to a SMART client which can connect retrieve resources information and update itself.

Published in: Technology, Art & Photos
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
320
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

OpenOffice.org Online Resources

  1. 1. OpenOffice.org resources Alexandro Colorado
  2. 2. Content <ul><li>Core Issue
  3. 3. What we have on the web? </li><ul><li>Drupal sites </li></ul><li>What we have in OpenOffice.org? </li><ul><li>Dumb clients </li></ul><li>Smarter way </li><ul><li>Protocols </li></ul></ul>
  4. 4. Core issues <ul><li>Resources are spread over
  5. 5. OpenOffice.org resources use an akward domain structure
  6. 6. OpenOffice.org are not web savvy enough
  7. 7. OpenOffice.org extensions are not integrated with the community services </li></ul>
  8. 8. What we have on the web?
  9. 9. Drupal sites can run together
  10. 10. OpenOffice.org uses DUMB clients Download from the web is not a viable way it forces the user to crawl on the web It doesnt produce value for OOo (no Google juice even) The engine might not be the best.
  11. 11. How does our clients look now
  12. 16. What repos should be? <ul><li>GNU/Linux Repos </li><ul><li>gURPMI (Mandriva)
  13. 17. Synaptics (Ubuntu) </li></ul><li>KDE Repos </li><ul><li>Wallpapers
  14. 18. Plasmoids
  15. 19. Themes </li></ul></ul>
  16. 20. What is a SMART client. <ul><li>Allow you to connect
  17. 21. No browser
  18. 22. Filter by categories
  19. 23. Download and update
  20. 24. Display some metatag
  21. 25. Use protocols like REST or XMLRPC </li></ul>
  22. 26. Drupal services <ul><li>Drupal uses XMLRPC by default
  23. 27. XMLRPC is hard and usually not used
  24. 28. Drupal has RESTfull modules (extensions)
  25. 29. OpenTemplate.org uses API
  26. 30. Clients should homonegize the API reference (functions)
  27. 31. Extension should recognize a standard API </li></ul>

×