forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: Forrest OpenOffice.org plugin
Date Wed, 06 Oct 2004 18:43:38 GMT
On Oct 6, 2004, at 11:09 AM, Ross Gardler wrote:
> There was a bug introduced a while back that caused this. It looks 
> like I create the branch when that bug existed. I don't have the time 
> to merge the changes in trunk into the branch right now. However, if 
> you do a "forrest run" everything works fine.

D'oh! Ahh well. You're right. I didn't try a /forrest run/ before. I 
just tried it, and it works fine. (BTW, in spite of the BUILD FAILED I 
was still able to see the docs/plugins.html file...)

>>> When developing a plugin you can do so directly in the  
>>> FORREST_HOME/plugins directory. We only need to package it for  
>>> download once it is complete.
>> I'll check it out. Do you have a "starter" zip of an OOo plugin to 
>> get  me started? I'd thought you mentioned you had something started, 
>> which  enabled one to use an OpenOffice.org .sxw file with embedded 
>> images.  Can you get me a copy of that?
>
> No, I seem to have misled you, sorry. I have some enhancements to the 
> OOo integration but it is using the existing system not the proposed 
> plugin system. I was hoping that we could extract the existing 
> functionality into a plugin and then add my enhancements.
>
> If you would prefer you are welcome work the other way around and work 
> my enhancements into the existing OOo stuff. When we extract the 
> plugin it will come with it.

I think that would be preferable to me. It looks like doing the forrest 
plugin thing will be an easy step after we've finished setting up 
forrest to provide the desired output.

> I'll open an issue and attach a zip of the files I have modified so 
> you can get at them. However, you should be aware that these 
> enhancements need merging with changes that have been made in the OOo 
> stuff here in Forrest, there have been quite a few since I first made 
> my changes so I am not sure how easy this will be. I don't expect it 
> to be a hard job, but who nows what will turn up.

Thanks! I'll download it when I see it (I assume we'll all be notified 
of the new FOR-31x issue)...

>> To be honest, I don't even know which files will be necessary to 
>> build  the plugin. I assume they're the *openoffice* files (the below 
>> files  except openoffice-writer.sxw) but it would help to pare down 
>> the list:
>
> <snip/>
>
>> I'm thinking the plugin should have the following structure:
>> OpenOffice/
>> OpenOffice/openOffice.xmap
>> OpenOffice/resources/stylesheets/openoffice-common2forrest.xsl
>> OpenOffice/resources/stylesheets/openoffice-impress2forrest.xsl
>> OpenOffice/resources/stylesheets/openoffice-writer2forrest.xsl
>> OpenOffice/resources/stylesheets/aggregates/openoffice-writer.xml
>> OpenOffice/resources/stylesheets/aggregates/openoffice-writer.xsl
>> Is that correct?
>
> Yes. Seems you already pared the list down quite nicely.

Glad to see I got it right (you can thank the author of the Plugins 
documentation for that ;-p)! I was hoping to make certain there wasn't 
anything else.

One other thing I thought of, was the ability to add (configurable in 
forrest.properties) a bug/button on OOo translated documents along the 
lines of the Standard OpenOffice.org Button - small on this page:

http://ooodocs.sourceforge.net/graphics/banners/index.html

This would be similar to the css, html & apache forrest bug/buttons at 
the bottom of the http://forrest.apache.org/ index page. Of course, to 
use this "Get OOo" image, someone @forrest.apache.org would need to ask 
the Community Manager <community-at-openoffice.org> for permission.

In addition, after reading their site, we may need to change the plugin 
name to OpenOffice.org/ (and also the files, e.g., 
OpenOffice.org-writer2forrest.xsl, etc. but then again, IANAL)

> One small point, the xmap is called "sitemap.xmap" not 
> "openOffice.xmap".

OK. FWIW, that came from the first item in my results:

[clay@Clay-Leeds-Computer forrest]$ find . -iname *openoffice*
./plugins/demoIMSSite/src/documentation/openOffice.xmap

  Is this file something different?

> What do you mean "the download"? The idea is the same as with custom 
> skins, a config file will indicate what plugins are required to build 
> a site (this does not exist as yet). When someone does "forrest *" one 
> of the first actions of Forrest is to ensure it has the necessary 
> plugins available. Any that are missing are automaticaly downloaded 
> and installed.

By 'download' I mean 'forrest distribution'. And by "automatically 
downloaded and installed"... It'll try and download it v for you? 
Nice... But does 'it' know to use svn, etc. or would it just use curl? 
and what if curl wasn't installed?

> The plugins are not included in the original Forrest download because 
> not everyone needs them and not all plugins will be managed by the 
> Forrest community.

OK.

<snip>
>> OK. But if you can get me your 'starter' OpenOffice.org stuff you've  
>> started, that would help.
>
> It's up to you where you want to start, either extracting the existing 
> OOo code into a plugin or merging the changes I have made in the files 
> I attach to the issue into the existing Forrest work.

I can start whenever you get me the code changes you've made. If those 
changes are based on HEAD, then I'll need to run the /svn switch .../ 
command again. Can you help me along there (can you send me the 
/switch/ command so I can copy & paste)?

>>>> Once I have that working, would I have forrest cp   
>>>> [the-embedded-image(s)] *.sxw/Pictures images/ (or ack!   
>>>> ../../../resources/images/)
>>>
>>> No copying involved, it extracts the images directly from the sxw  
>>> archive. Once we have the OOo plugin working I'll put what I have 
>>> into  it and we can go from there.
>> But won't we need to generate the thumbnail/screenshot images? Those  
>> will need to be generated, if not copied.
>
> The image is read from the sx* archive using a Cocoon generator. All 
> we need to do is make that generator scale the image accordingly 
> (actually it may be the job of a Transformer rather than a generator). 
> Cocoon itself will cache the results, we need not worry about copying 
> it anywhere (at least this is how I *think* it works I'm no expert on 
> Cocoons internals, so we'll have to check that out we get to this 
> stage).
>
> Ross

Thanks! This is exciting! And also, if you can point me toward the 
Cocoon docs I should look to for this, that would help too. But if 
you're busy, this can wait...

Web Maestro Clay
-- 
Clay Leeds - <cleeds@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>


Mime
View raw message