Basically, the most important info would be on the XMLRPC API on the OpenOffice side, and various client examples/development environments in which this has been done before, if possible.

But the more communication the better!

Victor Kane



On Thu, May 15, 2008 at 9:26 AM, Louis Suarez-Potts <Louis.Suarez-Potts@sun.com> wrote:
Hi,

On 2008-05-15, at 08:06 , FGM wrote:

Actually, I think this approach may give a solution with very little work on the drupal side.

Now, if someone with OOo programming knowledge could provide the required info to start on the OOo side of things, I'd gladly set up the whole thing. I've always wanted to improve my OOo integration skills, and stopped in front of the OOo SDK documentation, and this seems a good occasion to do so.

I'll ping some developers on this and cc you. They may be resistant to joining yet another list but let's see.

Thanks!
Louis




----- Original Message ----- From: "Victor Kane" <victorkane@gmail.com>
To: <development@drupal.org>
Sent: Thursday, May 15, 2008 12:42 PM
Subject: Re: [development] OpenOffice.org


Ok, taking into account what both Dario and Federic are saying (OpenOffice
as the user interface for publishing directly to a Drupal site via XMLRPC),
the best fit here in my opinion would be to use the services module.

It offers a rich API for node creation based on custom written services.

Here, I am not talking about importing a Document, but rather using the
OpenOffice as a client for Drupal, much as Word can be used as a client for
a Blog, including Drupal.

I am using this now for Drupal to Drupal speak (actually an editorial
workflow system sends articles to a  publishing system). See
http://awebfactory.com.ar/node/297

That would be a quick and sure path, leaving to OpenOffice the client work
and to Drupal the services server work, we'd be all set.

I actually did hunt around in the Open Office forums recently with an eye to
something like this, and saw something implemented ... but opted in the end
for Drupal 2 Drupal for the architecture of the system I was developing.

But imagine reporters in the field sending in their articles with a Drupal
plugin!

Victor Kane
http://awebfactory.com.ar

On Wed, May 14, 2008 at 11:49 PM, Frédéric G. MARAND <fgm@osinet.fr> wrote:

Hello,

Thanks for your message.

I have currently unpublished PHP code I've been using for a few years to
access OOo spreadsheets and load them into Drupal. However, it was developed
"ad hoc" to import product data, and is currently not fit for general use
since it is limited to spreadsheets and only goes from OOo to Drupal, not
the other way round. Maybe if others are interested in working on this we
could turn it into a general use module.

This being saind, while it could obviously be extended to other formats if
someone took time to create something more general, a limitation remains due
to the time it takes to load an OOo document in PHP vs the maximum
time/memory per PHP script on low-end intallations.

A file-system-like approach based on plain XML RPC or BlogAPI would
probably be easier on users and work in more cases. But it looks like this
would have to be done from within OOo, not in PHP but in Python, Basic, JS
or Beanshell.

Frederic G. MARAND
http://blog.riff.org/


----- Original Message ----- From: "Louis Suarez-Potts"
<Louis.Suarez-Potts@Sun.COM>
To: <development@drupal.org>
Sent: Thursday, May 15, 2008 3:35 AM
Subject: [development] OpenOffice.org




[This is a re-send of a message I sent originally to the
infrastructure list.]

Hello all!

Allow me to introduce myself: I'm the community manager of
OpenOffice.org, a role I've held for the last 7.5 years. My interest
here is to see if there is interest in developing an OpenDocument
Format filter for Drupal or (better yet) some ways of integrating or
at least linking OOo to Drupal. The reason? Lots, including both
public and private enterprises, want a CMS + productivity suite (such
as OOo) combo. Drupal has huge market share and is flourishing; so
does and is OOo.

How is integration imagined? It could be close or it could be even
something as simple as an extension. We have now many extensions, and
there is no reason why everything has to be a single package--this is
the Internet age, not the isolated desktop age.

If people are interested, let's talk. My guess is that an obstacle to
good intentions is reality: shortage of resources. But I also am
relentlessly optimistic and hopeful, and believe if we can present a
good case then companies may want to allocate those resources, which
is to say, people and money.

Ciao,

Louis


--
Louis Suarez-Potts, PhD
Community Manager, Sun Microsystems, Inc.
OpenOffice.org




--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 269.23.16/1432 - Release Date:
14/05/2008 07:49