forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject XHTML2 branch or not (was Re: [jira] Commented: (FOR-655) Create sample document for XHTML2 subset)
Date Mon, 05 Sep 2005 07:35:38 GMT
David Crossley wrote:
> Ross Gardler wrote:
> 
>>I guess we will create a branch to work in as part of the Forrest 
>>Tuesday thing. We will, most likely start off with a new seed site that 
>>uses XHTML2 as the source files. We then need to convert forrest:views 
>>to work with these input files rather than with Xdocs.
> 
> 
> Evidently we don't need a branch:
> http://marc.theaimsgroup.com/?l=forrest-dev&m=112530884006740

Hmmm... I'm not sure about that, I thought the whole outcome of our 
recent discussions about using SVN for better management was that we 
kept trunk stable and used branches for major new functionality.

I'm concerned about adding yet more pipelines to our already 
overstretched sitemaps. They are confusing enough as it is, lets not 
make them worse before we refactor them. My suggestion to use a branch 
is driven by the fact that I would like to rip out the parts of the 
sitemap that will no longer be relevant after the conversion to XHTML2 
(XDoc pipelines for example).

I'd like to see much cleaner sitemaps as a result of this work. However, 
this *will* break backward compatability for a period since we need to 
extract processing from core into plugins. Hence I think we need a branch.

But, ther is an alternative ...

It can be done without a branch, if we do it as an internal plugin so 
that we are not touching the core sitemaps. The core is scheduled for a 
major refactoring using the locatiomap, it seems counter productive to 
add more complexity to those pipelines before doing that work.

I therefore propose that we start an internal plugin that has the 
relevant pipelines, complete with refactoring.

But wait...

We said we would modify forrest:views to work with XHTML and the 
internal.views plugin already has a copy of most of the pipelines in it. 
We can't go replacing the existing internal.views plugin beause people 
are using that. I therefore further propose that this new XHTML2 
internal plugin is also a new forrest:views internal plugin, in which we 
refactor for the locationmap.

Am I trying to do too much all at once or are all these things 
complimentary?

If this is too much all at once then we need a branch in order to be 
sure we don't break trunk.

Ross

Mime
View raw message