Taking OpenOffice.org to the Web 2.0

AJAX, Google Maps, Blogs, Wiki’s, WebApps, Podcast, RSS, Flckr, Skype… all this applications that populate the internet right now are the flag of the Web 2.0. Which also sound like the return of the bubble.

With almost 15 years of internet explosion right now we see a lot of masive ammount of costumers using applications on teh web. Was this the promess of webservices? Maybe.

XML really pushed the value of the web, however low cost deployment of LAMP servers is what it really driven the users to deploy websites, content and interact with everybody.

Still we have seen that traditional applications are still a main prirority but the use might change soon.

With CMS deployment, E-Mails, and web-ERP, we spend more time in the web than the office suite.

Web applications have help us gave an independence from our desktop but still we have a legacy system which right now is less and less appealing.

OpenOffice.org is in part a reason why people don’t need the desktop app anymore, so a comodatize app like OpenOffice.org is good enough.

Paying for MSO is less and less appealing and really the way we have been behaving on the office latelly has to do more with web driven applications or web applications that interchange the content in our out of a business.

So how can we see the way we use the office suite in the future, well that is the question we really need plan to innovate.

OpenOffice.org to blog might be a good way to break into the office-web suite. So wha we want to do, connect the office to everything might be a way to do it.

The golden jewel might reside on the ability to publish, publish content on the web directly from the OOo interface is clearly something we might look into first.

Retrieving information also might be a good way to solve this. With a slim desire to develop we might also check for ways to generate our HTML content and upload it directly to the internet.

For Blogs the way applications usually do it is with XML-RPC which will connect to the site, pass the variables and insert it to the API. The more the generic the API the better so we can edit it and manipulate to our taste.

For wiki the method might be a bit difficult because wiki api are almost all different. PyBloxom is a wiki that might look more stable. Other wiki’s already halfway implemented like DokuWiki might also be a good candidate.

For PDA – OpenOffice.org already have a PDA but an uploader might be good to get OOo to encode as a wml document and send it to the pda, to do that we can do awareness of the infrared, this can be donde by just forwarding the document to the port of bluez or irman so we can directly send it there.

We could even do some synchronization if we use the metatags correctly triying to do the already available compare changes.

For Google, well the meta-data has certianly been solved on the google desktop, but how about doing things for linux. Beagle already have opendocument supports. However the OpenDocuments meta-tag is not as used so much. So now we can get OOoComments on track we can use the meta-data served on.