Hi Tim, I did that 30 minutes ago, together with the check-reload flag :) So the treeprocessor is now a real replacement for the compiled version.
Carsten > -----Original Message----- > From: Timothy Larson [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 31, 2003 3:26 PM > To: [EMAIL PROTECTED] > Subject: Re: Sitemap-Engine for 2.0.5 > > > In cocoon.xconf the "file" attribute of the sitemap is ignored by > the treeprocessor. In the old engine, the "file" attribute allowed > control over where the root sitemap.xmap was placed and what > it was named. > > If you remove the old engine, could you make the treeprocessor > respect the "file" attribute, please? > > Tim > > >>>> [EMAIL PROTECTED] 01/31/03 06:58AM >>> > >Carsten Ziegeler dijo: > >> Is anyone against making the treeprocessor the default engine > for 2.0.5? > > > >I am in favor of making the treeprocessor the default engine for 2.0.5. > > > >> Is anyone against removing the stylesheet engine? I don't think that we > >> have to keep it for compatibility issues. > > > >Is there a diference? I thinked the use of that is transparently for the > >user view. If this is true. I think you can remove it. What kind of > >compatibiliy issue can raise the change? > > > >Maybe there is only a sentimental issue from the author of the piece of > >code. ;-) > > > >Best Regards, > > > >Antonio Gallardo. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
