OpenOffice.org resources Alexandro Colorado

Content Core Issue What we have on the web? Drupal sites What we have in OpenOffice.org? Dumb clients Smarter way Protocols

Core Issue

What we have on the web?

Drupal sites

What we have in OpenOffice.org?

Dumb clients

Smarter way

Protocols

Core issues Resources are spread over OpenOffice.org resources use an akward domain structure OpenOffice.org are not web savvy enough OpenOffice.org extensions are not integrated with the community services

Resources are spread over

OpenOffice.org resources use an akward domain structure

OpenOffice.org are not web savvy enough

OpenOffice.org extensions are not integrated with the community services

What we have on the web?

Drupal sites can run together

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.

How does our clients look now

What repos should be? GNU/Linux Repos gURPMI (Mandriva) Synaptics (Ubuntu) KDE Repos Wallpapers Plasmoids Themes

GNU/Linux Repos

gURPMI (Mandriva)

Synaptics (Ubuntu)

KDE Repos

Wallpapers

Plasmoids

Themes

What is a SMART client. Allow you to connect No browser Filter by categories Download and update Display some metatag Use protocols like REST or XMLRPC

Allow you to connect

No browser

Filter by categories

Download and update

Display some metatag

Use protocols like REST or XMLRPC

Drupal services Drupal uses XMLRPC by default XMLRPC is hard and usually not used Drupal has RESTfull modules (extensions) OpenTemplate.org uses API Clients should homonegize the API reference (functions) Extension should recognize a standard API

Drupal uses XMLRPC by default

XMLRPC is hard and usually not used

Drupal has RESTfull modules (extensions)

OpenTemplate.org uses API

Clients should homonegize the API reference (functions)

Extension should recognize a standard API