You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/06/27 10:17:35 UTC
[RT] New Target: sub-sitemap
I was just wondering if it would be possible to make a new
target for forrest that creates only a subsitemap for cocoon
instead of a full blown webapp?
If you use a defined Cocoon version where you put this subsitemap
into, I think, technically there should only be a few problems:
- additional jars (no problem, could be put into ${target}/WEB-INF/lib
- additional config (no real problem, the xpatch tool could patch
everything (cocoon.xconf, web.xml, sitemap etc.)
- links and references - this could be the hardest part, I don't know
If everything (stylesheets, images, documents) is linked and referenced
relative, moving it into a subdirectory (subsitemap) should be
no problem. If there are references to the root of the webapp
they have to be changed.
What do you think about the idea? I think this is a common use-case,
because often you have a (cocoon) webapp and simply want to put
some (dynamially generated) content into it. For example, the cocoon
demo could use this for it's own documentation as well.
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
http://radio.weblogs.com/0107211/
Re: Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Stefano Mazzocchi <st...@apache.org>.
on 6/30/03 8:50 AM Steven Noels wrote:
> On 30/06/2003 15:34 Nicola Ken Barozzi wrote:
>
>
>>But you do make valid points.
>
>
> He always does. Big toothbrush.
>
>
>>Here is a counterproposal:
>>
>>1 - since we have basically voted to be part of the Cocoon project,
>> give all Cocoon developers access to Forrest CVS
>
>
> AFAIU, we agreed enthusiastically that the karma barrier for Cocoon
> committers to Forrest CVS should be drastically lowered. From the
> Forrest devs however, the way I read it there was reluctancy in stating
> that this essentially means becoming a Cocoon subproject - maybe the
> time isn't there yet, or might perhaps never come.
>
>
>>2 - Forrest should be able to be used as a Cocoon block.
>
>
> +1
>
> The current blocks implementation however doesn't easily allows for
> externaly maintained bloks.
sorry for jumping in late.
I plan to work on start implementing "real blocks" for cocoon as soon as
cocoon 2.1 is out final. at that point, forrest (and lenya and linotype
and the portal framework and many of the current cocoon blocks) can
really live as a block.
I just suggest to be patient and avoid doing something that you would
have to regret in a few months.
--
Stefano.
Re: Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Steven Noels <st...@outerthought.org>.
On 30/06/2003 15:34 Nicola Ken Barozzi wrote:
> But you do make valid points.
He always does. Big toothbrush.
> Here is a counterproposal:
>
> 1 - since we have basically voted to be part of the Cocoon project,
> give all Cocoon developers access to Forrest CVS
AFAIU, we agreed enthusiastically that the karma barrier for Cocoon
committers to Forrest CVS should be drastically lowered. From the
Forrest devs however, the way I read it there was reluctancy in stating
that this essentially means becoming a Cocoon subproject - maybe the
time isn't there yet, or might perhaps never come.
> 2 - Forrest should be able to be used as a Cocoon block.
+1
The current blocks implementation however doesn't easily allows for
externaly maintained bloks.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote, On 30/06/2003 15.21:
...
> Off in RT mode a bit..
>
> Every time I upgrade Forrest's jars, I think that Forrest should really
> just be a Cocoon block. Despite its 20mb, there really isn't that much
> _content_ in Forrest. A sitemap, some DTDs, a couple of skins, and an
> Ant-driven build process.
>
> That the 'core' of Forrest is so small leads me to wonder if Cocoon
> shouldn't just include what it needs of Forrest internally.
...
> What do people think?
Forrest is still just scratching the surfance of what it should do.
It should use Lenya underneath for a real CMS. It can integrate blogging
stuff from Linotype. It has a site updater.
These are things that have nothing to do with core Cocoon, which the
cocoon CVS repo and project are about.
Community-wise, Forrest is a different place, and it's IMHO correct to
keep it this way... do you imagine Forrest users and developers being
part of the cocoon lists?
If the point is about Forrest packaging, well, I understand what you
mean, it seems strange to have to update Cocoon. But I see more Forrest
as a pre-packaged and running Cocoon distro, in the future also with Lenya.
I doubt we will get much more users in moving to cocoon CVS, remember
the old docs system, and how much it was fixed? ;-)
Basing Forrest development on fixed jars is not a shortcoming but a
blessing that makes us able to not work on sand.
Nope, it makes sense to remain separate as now.
But you do make valid points. Here is a counterproposal:
1 - since we have basically voted to be part of the Cocoon project,
give all Cocoon developers access to Forrest CVS
2 - Forrest should be able to be used as a Cocoon block.
Too bad that blocks based on xslt,sitemaps,xml like Forrest
don't yet truly exist.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote, On 01/07/2003 11.16:
> On Mon, Jun 30, 2003 at 03:34:08PM +0200, Nicola Ken Barozzi wrote:
...
>>Nope, it makes sense to remain separate as now.
>
> Yep, fully agree with you that Cocoon and Forrest have distinct
> identities and shouldn't merge any time soon.
>
> However, most of my email wasn't about that.
Sorry, I misread I guess.
> I'm just suggesting copying
> some Forrest files into Cocoon. It's like a disk cache in an operating
> system, where some data gets duplicated closer to where it's used, in
> order to improve performance. Every now and then, we synch the 'cache'
> (Cocoon CVS) with the 'disk' (Forrest CVS). That synch price is lower
> than the cost of Cocoon developers having to constantly access the
> 'disk'.
Ok, now I get it, I thought the other way around, as you started by
assuming now that Cocoon is the disk from where you get updates.
I remember we have already had this discussion. The major point was that
documentation has to be able to be written and published regardless of
the state of the Cocoon CVS. Having a separate and "stable" doc system
was regarded as a plus, and I still stand by this idea.
What's so difficult for Cocoon users to have to
cd xml-forrest
cvs update
build
for every Forrest update?
For us, we can do a similar thing, by adding a script to the Ant task
for cocoon synchro, as you have done with the script. So anyone can test
Cocoon changes from Forrest anytime.
Gump should also be able to run a Forrest test and see that it works
with latest Cocoon, no?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Jeff Turner <je...@apache.org>.
On Mon, Jun 30, 2003 at 03:34:08PM +0200, Nicola Ken Barozzi wrote:
...
> Forrest is still just scratching the surfance of what it should do.
> It should use Lenya underneath for a real CMS. It can integrate blogging
> stuff from Linotype. It has a site updater.
> These are things that have nothing to do with core Cocoon, which the
> cocoon CVS repo and project are about.
>
> Community-wise, Forrest is a different place, and it's IMHO correct to
> keep it this way... do you imagine Forrest users and developers being
> part of the cocoon lists?
>
> If the point is about Forrest packaging, well, I understand what you
> mean, it seems strange to have to update Cocoon. But I see more Forrest
> as a pre-packaged and running Cocoon distro, in the future also with Lenya.
>
> I doubt we will get much more users in moving to cocoon CVS, remember
> the old docs system, and how much it was fixed? ;-)
> Basing Forrest development on fixed jars is not a shortcoming but a
> blessing that makes us able to not work on sand.
>
> Nope, it makes sense to remain separate as now.
Yep, fully agree with you that Cocoon and Forrest have distinct
identities and shouldn't merge any time soon.
However, most of my email wasn't about that. I'm just suggesting copying
some Forrest files into Cocoon. It's like a disk cache in an operating
system, where some data gets duplicated closer to where it's used, in
order to improve performance. Every now and then, we synch the 'cache'
(Cocoon CVS) with the 'disk' (Forrest CVS). That synch price is lower
than the cost of Cocoon developers having to constantly access the
'disk'.
--Jeff
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
Re: Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote, On 30/06/2003 15.21:
...
> Off in RT mode a bit..
>
> Every time I upgrade Forrest's jars, I think that Forrest should really
> just be a Cocoon block. Despite its 20mb, there really isn't that much
> _content_ in Forrest. A sitemap, some DTDs, a couple of skins, and an
> Ant-driven build process.
>
> That the 'core' of Forrest is so small leads me to wonder if Cocoon
> shouldn't just include what it needs of Forrest internally.
...
> What do people think?
Forrest is still just scratching the surfance of what it should do.
It should use Lenya underneath for a real CMS. It can integrate blogging
stuff from Linotype. It has a site updater.
These are things that have nothing to do with core Cocoon, which the
cocoon CVS repo and project are about.
Community-wise, Forrest is a different place, and it's IMHO correct to
keep it this way... do you imagine Forrest users and developers being
part of the cocoon lists?
If the point is about Forrest packaging, well, I understand what you
mean, it seems strange to have to update Cocoon. But I see more Forrest
as a pre-packaged and running Cocoon distro, in the future also with Lenya.
I doubt we will get much more users in moving to cocoon CVS, remember
the old docs system, and how much it was fixed? ;-)
Basing Forrest development on fixed jars is not a shortcoming but a
blessing that makes us able to not work on sand.
Nope, it makes sense to remain separate as now.
But you do make valid points. Here is a counterproposal:
1 - since we have basically voted to be part of the Cocoon project,
give all Cocoon developers access to Forrest CVS
2 - Forrest should be able to be used as a Cocoon block.
Too bad that blocks based on xslt,sitemaps,xml like Forrest
don't yet truly exist.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Back to home-grown docs?
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Le Lundi, 30 juin 2003, à 15:21 Europe/Zurich, Jeff Turner a écrit :
> ...Every time I upgrade Forrest's jars, I think that Forrest should
> really
> just be a Cocoon block...
I definitely like the idea.
Earlier I proposed to include a binary version of Forrest in the Cocoon
CVS to avoid the dependency problem, but this kills more birds with the
same stone, in a much lighter way.
And Forrest is a good showcase of what Cocoon can do, so I'm all +1 on
this.
-Bertrand
Re: Back to home-grown docs?
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Le Lundi, 30 juin 2003, à 15:21 Europe/Zurich, Jeff Turner a écrit :
> ...Every time I upgrade Forrest's jars, I think that Forrest should
> really
> just be a Cocoon block...
I definitely like the idea.
Earlier I proposed to include a binary version of Forrest in the Cocoon
CVS to avoid the dependency problem, but this kills more birds with the
same stone, in a much lighter way.
And Forrest is a good showcase of what Cocoon can do, so I'm all +1 on
this.
-Bertrand
Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Jeff Turner <je...@apache.org>.
On Fri, Jun 27, 2003 at 10:17:35AM +0200, Carsten Ziegeler wrote:
> I was just wondering if it would be possible to make a new
> target for forrest that creates only a subsitemap for cocoon
> instead of a full blown webapp?
>
> If you use a defined Cocoon version where you put this subsitemap
> into, I think, technically there should only be a few problems:
> - additional jars (no problem, could be put into ${target}/WEB-INF/lib
> - additional config (no real problem, the xpatch tool could patch
> everything (cocoon.xconf, web.xml, sitemap etc.)
> - links and references - this could be the hardest part, I don't know
> If everything (stylesheets, images, documents) is linked and referenced
> relative, moving it into a subdirectory (subsitemap) should be
> no problem. If there are references to the root of the webapp
> they have to be changed.
Only real problem is that we rely on cocoon:// URLs in quite a few
places. This was necessary because cocoon: URLs are resolved relative to
their original caller. So if cocoon:/subdir/A calls cocoon://B, who
calls cocoon:/C, then it's as if A called cocoon:/subdir/C.
We could work around this by adding a {root} sitemap variable.
> What do you think about the idea? I think this is a common use-case,
> because often you have a (cocoon) webapp and simply want to put
> some (dynamially generated) content into it. For example, the cocoon
> demo could use this for it's own documentation as well.
Off in RT mode a bit..
Every time I upgrade Forrest's jars, I think that Forrest should really
just be a Cocoon block. Despite its 20mb, there really isn't that much
_content_ in Forrest. A sitemap, some DTDs, a couple of skins, and an
Ant-driven build process.
That the 'core' of Forrest is so small leads me to wonder if Cocoon
shouldn't just include what it needs of Forrest internally. That would
be:
The forrest-css skin: 128k
The v12 or v20a DTD : 31k
A bunch of sitemaps : 124k
Image resources : 20k
Stylesheet resources: 131k
resolver.jar (ant) : 68k
-----
502k
Most Forrest developers are also Cocoon developers, so I suspect the cost
of keeping these in synch is lower than the cost to Cocoon developers of
having to deal with Forrest as a separate entity.
The result would be that Cocoon eliminates a dependency, and Forrest
gains a bunch of indirect contributors, as improvements to the Cocoon doc
system get fed back into Forrest. Plus (and this is the bit that appeals
to me) any Cocoon breakage that affects Forrest will be Cocoon's problem
before it becomes Forrest's ;)
Practically, this amounts to:
1) In Cocoon's existing src/documentation/* doc system, synchronize
stylesheets, DTDs and images with Forrest's.
2) If everything works, call a vote on cocoon-docs to remove the Forrest
Ant targets, and use the built-in system.
What do people think?
--Jeff
> Carsten
>
> Carsten Ziegeler
> Open Source Group, S&N AG
> http://radio.weblogs.com/0107211/
Back to home-grown docs? (Re: [RT] New Target: sub-sitemap)
Posted by Jeff Turner <je...@apache.org>.
On Fri, Jun 27, 2003 at 10:17:35AM +0200, Carsten Ziegeler wrote:
> I was just wondering if it would be possible to make a new
> target for forrest that creates only a subsitemap for cocoon
> instead of a full blown webapp?
>
> If you use a defined Cocoon version where you put this subsitemap
> into, I think, technically there should only be a few problems:
> - additional jars (no problem, could be put into ${target}/WEB-INF/lib
> - additional config (no real problem, the xpatch tool could patch
> everything (cocoon.xconf, web.xml, sitemap etc.)
> - links and references - this could be the hardest part, I don't know
> If everything (stylesheets, images, documents) is linked and referenced
> relative, moving it into a subdirectory (subsitemap) should be
> no problem. If there are references to the root of the webapp
> they have to be changed.
Only real problem is that we rely on cocoon:// URLs in quite a few
places. This was necessary because cocoon: URLs are resolved relative to
their original caller. So if cocoon:/subdir/A calls cocoon://B, who
calls cocoon:/C, then it's as if A called cocoon:/subdir/C.
We could work around this by adding a {root} sitemap variable.
> What do you think about the idea? I think this is a common use-case,
> because often you have a (cocoon) webapp and simply want to put
> some (dynamially generated) content into it. For example, the cocoon
> demo could use this for it's own documentation as well.
Off in RT mode a bit..
Every time I upgrade Forrest's jars, I think that Forrest should really
just be a Cocoon block. Despite its 20mb, there really isn't that much
_content_ in Forrest. A sitemap, some DTDs, a couple of skins, and an
Ant-driven build process.
That the 'core' of Forrest is so small leads me to wonder if Cocoon
shouldn't just include what it needs of Forrest internally. That would
be:
The forrest-css skin: 128k
The v12 or v20a DTD : 31k
A bunch of sitemaps : 124k
Image resources : 20k
Stylesheet resources: 131k
resolver.jar (ant) : 68k
-----
502k
Most Forrest developers are also Cocoon developers, so I suspect the cost
of keeping these in synch is lower than the cost to Cocoon developers of
having to deal with Forrest as a separate entity.
The result would be that Cocoon eliminates a dependency, and Forrest
gains a bunch of indirect contributors, as improvements to the Cocoon doc
system get fed back into Forrest. Plus (and this is the bit that appeals
to me) any Cocoon breakage that affects Forrest will be Cocoon's problem
before it becomes Forrest's ;)
Practically, this amounts to:
1) In Cocoon's existing src/documentation/* doc system, synchronize
stylesheets, DTDs and images with Forrest's.
2) If everything works, call a vote on cocoon-docs to remove the Forrest
Ant targets, and use the built-in system.
What do people think?
--Jeff
> Carsten
>
> Carsten Ziegeler
> Open Source Group, S&N AG
> http://radio.weblogs.com/0107211/