You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Thorsten Scherler <th...@wyona.com> on 2006/04/05 12:02:40 UTC

Re: Improving Forrest/OpenOffice.org integration

Hi all, hi David Eisenberg,

I included David in cc since he is the original author of the
odt-to-xhtml stylesheet and has contributed his work to the ASF. Thanks
again.

El mié, 05-04-2006 a las 09:50 +0100, Ross Gardler escribió:
> Web Maestro Clay wrote:
> > On Apr 2, 2006, at 5:35 AM, Ross Gardler wrote:
> > 
> >> Ross Gardler wrote:
> >>
> >>> Web Maestro Clay wrote:
> >>>
> >>>> I've been given the go-ahead to work on Forrest's OpenOffice.org   
> >>>> functionality
> >>>
> >>> Excellent!!
> >>>
> >>>> Would it make more sense to 'leave' the OpenOffice.org plugin  
> >>>> alone,  and focus instead on creating a new OpenDocument plugin,  
> >>>> since it  doesn't appear to have as many styling issues?
> >>>
> >>> +1 to starting afresh and working on an OpenDocument plugin instead.
> >>
> >>
> >> One other tip. When I did the Resume plugin I used a simple  generator 
> >> for SXW files [1]. This replaces the rather hacky way of  reading the 
> >> zipped SXW files in the OOo plugin. I never found the  time to make it 
> >> work for other OOo formats and put it into the OOo  plugin.
> >>
> >> Perhaps your work is the perfect opportunity to do this. It's  pretty 
> >> simple (as long as you know a little Java) and improves  performance 
> >> considerably.
> >>
> >> Ross
> >>
> >> [1] http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/ 
> >> plugins/org.apache.forrest.plugin.input.Resume/src/java/org/apache/ 
> >> forrest/generation/
> > 
> > 
> > I took a look at that, and it looks interesting. However, I think the  
> > Lenya OpenDocument module looks like a better route to go (do you  agree?).
> 
> Never looked at it, but it has received more attention, so it would not 
> surprise me if it is a better approach.

I worked on the lenya opendocument module not so long ago. I will be
happy to assist to convert the module to a lenya module *and* forrest
plugin (at the same time) if lenya-devs are happy with that. 

> 
> > I've checked out this code from Lenya, and will take a look at how I  
> > can 'convert' to forrest. My first step will be to essentially search  & 
> > replace for 'lenya' and replace with 'forrest'.
> 
> Lets try not to cut and paste. We are lucky enough to have a couple of 
> Lenya devs here, perhaps they can make a suggestion. I'm thinking of a 
> Cocoon block that both projects can make use of.
> 
> (WARNING: I have not even looked at the Lenya code for this, so I may be 
> sending us down a dead end - use your own judgment)

No, Ross you are right, thanks for pointing it out. I am unsure about
the block thing because I never had he time to look closer on that, but
even without to convert it to a block one can pretty fast EXTEND the
module to be used in forrest as plugin as well.

> 
> > I'll also try to  make 
> > it match the Forrest plugin nomenclature and infrastructure as  closely 
> > as possible (pathnames, and class names, etc.).
> 
> If we need to cut and paste then we may as well do this too. However, if 
> it is possible for us to build block from the Lenya code base, without 
> bringing loads of extra stuff we don't need, that would be better.
> 
> > Of course,  it's 
> > possible I'll do more harm than good, but we'll see how it goes...
> 
> Fortune favours the brave, Good luck ;-)

I will try to make some changes and commit them to lenya so that forrest
can use the lenya module directly without copy and paste. 

Further I just assigned 
http://issues.apache.org/bugzilla/show_bug.cgi?id=39134 to myself and will 
incooperate the xsl (now that it is as well Apache 2 license thanks to David Eisenberg, 
who changed the license after Renaud Richardet asked for it - *big* thanks to both).

Basicly we need to extract all xsl code into helper stylesheet to reuse
them for lenya (who needs a special trigger element) and forrest (who
needs xdocs). Further lenya and the stylesheet from
http://books.evc-cit.info/odf_utils/odt_to_xhtml.html are converting odt
to xhtml, so we need to convert after this to xdocs.

Clay, you may as well be interested in 

http://svn.wyona.com/repos/public/lenya/modules/opendocument/

anonymous:anonymous

Where the xsl is already incooperated since the current one in lenya is
very limited regarding style.

Thanks Clay to try lenya and I am more then glad to point you to 
http://svn.apache.org/viewcvs.cgi/lenya/sandbox/doco/
where we started to have lenya and forrest working side by side. So far
me and David Crossley are the only one that have committed so far so do
not expect a big thing yet, but like always help welcome. ;)

BTW Clay since IMO we should do the work over in lenya you may want to
submit your patches regarding the odt module to lenya bugzilla. Then
more lenya devs can help.

TIA

salu2
-- 
Thorsten Scherler
COO Spain
Wyona Inc.  -  Open Source Content Management  -  Apache Lenya
http://www.wyona.com                   http://lenya.apache.org
thorsten.scherler@wyona.com                thorsten@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org


Re: Improving Forrest/OpenOffice.org integration

Posted by Web Maestro Clay <th...@gmail.com>.
On Apr 5, 2006, at 3:02 AM, Thorsten Scherler wrote:
> El mié, 05-04-2006 a las 09:50 +0100, Ross Gardler escribió:
>> Web Maestro Clay wrote:
>>> I took a look at that, and it looks interesting. However, I think  
>>> the
>>> Lenya OpenDocument module looks like a better route to go (do  
>>> you  agree?).
>>
>> Never looked at it, but it has received more attention, so it  
>> would not
>> surprise me if it is a better approach.

The primary thing that attracted me to it, was that IIRC, the current  
Forrest OOo plugin is not as optimized in its transformation of SXW  
documents as some of Cocoon's newer ODT functionality[1]. I don't  
have a 'net connection ATM, so I can't 'look', but I believe it  
discussed newer serializers for reading files, which I don't believe  
are being utilized by the current OOo plugin.

> I worked on the lenya opendocument module not so long ago. I will be
> happy to assist to convert the module to a lenya module *and* forrest
> plugin (at the same time) if lenya-devs are happy with that.

Great news!

>>> I've checked out this code from Lenya, and will take a look at how I
>>> can 'convert' to forrest. My first step will be to essentially  
>>> search  &
>>> replace for 'lenya' and replace with 'forrest'.
>>
>> Lets try not to cut and paste. We are lucky enough to have a  
>> couple of
>> Lenya devs here, perhaps they can make a suggestion. I'm thinking  
>> of a
>> Cocoon block that both projects can make use of.
>>
>> (WARNING: I have not even looked at the Lenya code for this, so I  
>> may be
>> sending us down a dead end - use your own judgment)
>
> No, Ross you are right, thanks for pointing it out. I am unsure about
> the block thing because I never had he time to look closer on that,  
> but
> even without to convert it to a block one can pretty fast EXTEND the
> module to be used in forrest as plugin as well.

Sounds great to me. I'll do what I can to help. One thing that's  
never been clear to me, is whether or not .odt correlates just to  
OOo's 'Writer' (.sxw) only, or if it's also for Spreadsheets,  
Presentation files, etc.

>>> I'll also try to  make
>>> it match the Forrest plugin nomenclature and infrastructure as   
>>> closely
>>> as possible (pathnames, and class names, etc.).
>>
>> If we need to cut and paste then we may as well do this too.  
>> However, if
>> it is possible for us to build block from the Lenya code base,  
>> without
>> bringing loads of extra stuff we don't need, that would be better.

I'll wait then.

>>> Of course,  it's
>>> possible I'll do more harm than good, but we'll see how it goes...
>>
>> Fortune favours the brave, Good luck ;-)
>
> I will try to make some changes and commit them to lenya so that  
> forrest
> can use the lenya module directly without copy and paste.
>
> Further I just assigned
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39134 to myself  
> and will
> incooperate the xsl (now that it is as well Apache 2 license thanks  
> to David Eisenberg,
> who changed the license after Renaud Richardet asked for it - *big*  
> thanks to both).
>
> Basicly we need to extract all xsl code into helper stylesheet to  
> reuse
> them for lenya (who needs a special trigger element) and forrest (who
> needs xdocs). Further lenya and the stylesheet from
> http://books.evc-cit.info/odf_utils/odt_to_xhtml.html are  
> converting odt
> to xhtml, so we need to convert after this to xdocs.

Let me know what 'I' can to do to help. I already downloaded the  
Lenya OpenDocument plugin^H^H^H^H^H Module. I haven't played with  
Lenya too much, yet though.

The great thing, is that the client will likely get a content  
management system (in addition to a documentation system based on  
OpenDocument). One thing the client needs, though--and this may be a  
little off-topic--is a self-contained version of the document, which  
does not require an internet connection (the build/site/ content I  
would get if I ran `forrest`).

> Clay, you may as well be interested in
>
> http://svn.wyona.com/repos/public/lenya/modules/opendocument/
>
> anonymous:anonymous
>
> Where the xsl is already incooperated since the current one in  
> lenya is
> very limited regarding style.
>
> Thanks Clay to try lenya and I am more then glad to point you to
> http://svn.apache.org/viewcvs.cgi/lenya/sandbox/doco/
> where we started to have lenya and forrest working side by side. So  
> far
> me and David Crossley are the only one that have committed so far  
> so do
> not expect a big thing yet, but like always help welcome. ;)

I am eager to contribute what I can. But at present (aside from  
joining the Lenya mailing list, and downloading the Lenya  
OpenDocument Module, I don't know what to do. I'll study this[2] and  
the XSL code for extracting the data stylesheets (see above where I  
grabbed [2] from), and see if I get any ideas.

> BTW Clay since IMO we should do the work over in lenya you may want to
> submit your patches regarding the odt module to lenya bugzilla. Then
> more lenya devs can help.

Will do. Grazie mille (thanks a million!) again for your help!

> TIA
>
> salu2
> -- 
> Thorsten Scherler
> COO Spain
> Wyona Inc.  -  Open Source Content Management  -  Apache Lenya
> http://www.wyona.com                   http://lenya.apache.org
> thorsten.scherler@wyona.com                thorsten@apache.org
>

[1]
http://137.207.120.195:8080/cocoon/wampum/repo/OpenOfficeRocks.odt

[2]
http://books.evc-cit.info/odf_utils/odt_to_xhtml.html

Clay Leeds
webmaestro@mac.com

My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet






Clay Leeds
the.webmaestro@gmail.com

My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet




Re: Improving Forrest/OpenOffice.org integration

Posted by Clay Leeds <we...@mac.com>.
On Apr 5, 2006, at 3:02 AM, Thorsten Scherler wrote:
> El mié, 05-04-2006 a las 09:50 +0100, Ross Gardler escribió:
>> Web Maestro Clay wrote:
>>> I took a look at that, and it looks interesting. However, I think  
>>> the
>>> Lenya OpenDocument module looks like a better route to go (do  
>>> you  agree?).
>>
>> Never looked at it, but it has received more attention, so it  
>> would not
>> surprise me if it is a better approach.

The primary thing that attracted me to it, was that IIRC, the current  
Forrest OOo plugin is not as optimized in its transformation of SXW  
documents as some of Cocoon's newer ODT functionality[1]. I don't  
have a 'net connection ATM, so I can't 'look', but I believe it  
discussed newer serializers for reading files, which I don't believe  
are being utilized by the current OOo plugin.

> I worked on the lenya opendocument module not so long ago. I will be
> happy to assist to convert the module to a lenya module *and* forrest
> plugin (at the same time) if lenya-devs are happy with that.

Great news!

>>> I've checked out this code from Lenya, and will take a look at how I
>>> can 'convert' to forrest. My first step will be to essentially  
>>> search  &
>>> replace for 'lenya' and replace with 'forrest'.
>>
>> Lets try not to cut and paste. We are lucky enough to have a  
>> couple of
>> Lenya devs here, perhaps they can make a suggestion. I'm thinking  
>> of a
>> Cocoon block that both projects can make use of.
>>
>> (WARNING: I have not even looked at the Lenya code for this, so I  
>> may be
>> sending us down a dead end - use your own judgment)
>
> No, Ross you are right, thanks for pointing it out. I am unsure about
> the block thing because I never had he time to look closer on that,  
> but
> even without to convert it to a block one can pretty fast EXTEND the
> module to be used in forrest as plugin as well.

Sounds great to me. I'll do what I can to help. One thing that's  
never been clear to me, is whether or not .odt correlates just to  
OOo's 'Writer' (.sxw) only, or if it's also for Spreadsheets,  
Presentation files, etc.

>>> I'll also try to  make
>>> it match the Forrest plugin nomenclature and infrastructure as   
>>> closely
>>> as possible (pathnames, and class names, etc.).
>>
>> If we need to cut and paste then we may as well do this too.  
>> However, if
>> it is possible for us to build block from the Lenya code base,  
>> without
>> bringing loads of extra stuff we don't need, that would be better.

I'll wait then.

>>> Of course,  it's
>>> possible I'll do more harm than good, but we'll see how it goes...
>>
>> Fortune favours the brave, Good luck ;-)
>
> I will try to make some changes and commit them to lenya so that  
> forrest
> can use the lenya module directly without copy and paste.
>
> Further I just assigned
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39134 to myself  
> and will
> incooperate the xsl (now that it is as well Apache 2 license thanks  
> to David Eisenberg,
> who changed the license after Renaud Richardet asked for it - *big*  
> thanks to both).
>
> Basicly we need to extract all xsl code into helper stylesheet to  
> reuse
> them for lenya (who needs a special trigger element) and forrest (who
> needs xdocs). Further lenya and the stylesheet from
> http://books.evc-cit.info/odf_utils/odt_to_xhtml.html are  
> converting odt
> to xhtml, so we need to convert after this to xdocs.

Let me know what 'I' can to do to help. I already downloaded the  
Lenya OpenDocument plugin^H^H^H^H^H Module. I haven't played with  
Lenya too much, yet though.

The great thing, is that the client will likely get a content  
management system (in addition to a documentation system based on  
OpenDocument). One thing the client needs, though--and this may be a  
little off-topic--is a self-contained version of the document, which  
does not require an internet connection (the build/site/ content I  
would get if I ran `forrest`).

> Clay, you may as well be interested in
>
> http://svn.wyona.com/repos/public/lenya/modules/opendocument/
>
> anonymous:anonymous
>
> Where the xsl is already incooperated since the current one in  
> lenya is
> very limited regarding style.
>
> Thanks Clay to try lenya and I am more then glad to point you to
> http://svn.apache.org/viewcvs.cgi/lenya/sandbox/doco/
> where we started to have lenya and forrest working side by side. So  
> far
> me and David Crossley are the only one that have committed so far  
> so do
> not expect a big thing yet, but like always help welcome. ;)

I am eager to contribute what I can. But at present (aside from  
joining the Lenya mailing list, and downloading the Lenya  
OpenDocument Module, I don't know what to do. I'll study this[2] and  
the XSL code for extracting the data stylesheets (see above where I  
grabbed [2] from), and see if I get any ideas.

> BTW Clay since IMO we should do the work over in lenya you may want to
> submit your patches regarding the odt module to lenya bugzilla. Then
> more lenya devs can help.

Will do. Grazie mille (thanks a million!) again for your help!

> TIA
>
> salu2
> -- 
> Thorsten Scherler
> COO Spain
> Wyona Inc.  -  Open Source Content Management  -  Apache Lenya
> http://www.wyona.com                   http://lenya.apache.org
> thorsten.scherler@wyona.com                thorsten@apache.org
>

[1]
http://137.207.120.195:8080/cocoon/wampum/repo/OpenOfficeRocks.odt

[2]
http://books.evc-cit.info/odf_utils/odt_to_xhtml.html

Clay Leeds
webmaestro@mac.com

My religion is simple. My religion is kindness.
-- HH Dalai Lama of Tibet