RE: FYI: New Sitemap Treeprocessor for 2.2

2004-03-23 Thread Carsten Ziegeler
Sent: Monday, March 22, 2004 12:10 PM > To: [EMAIL PROTECTED] > Subject: Re: FYI: New Sitemap Treeprocessor for 2.2 > > Carsten Ziegeler wrote: > > >Sylvain Wallez wrote: > > > > > >>>Hi, > >>> > >>>to avoid double efforts in

RE: FYI: New Sitemap Treeprocessor for 2.2

2004-03-22 Thread Carsten Ziegeler
Sylvain Wallez wrote: > > Ah yeah. But we still need ServiceSelector. > Sure, by Container independent I mean "avalon compatible container independent". Of course, we rely on all the apis provided by the avalon framework - but nothing more. > > Ah, so please commit your PC in the CVS :-) > O

Re: FYI: New Sitemap Treeprocessor for 2.2

2004-03-22 Thread Sylvain Wallez
Carsten Ziegeler wrote: Sylvain Wallez wrote: Hi, to avoid double efforts in the same area, I just wanted to inform you that I will try to write a new tree processor for 2.2 in the next few days. Why? There are several reasons: - Reverting to ECM in 2.2 requires some changes to the tre

RE: FYI: New Sitemap Treeprocessor for 2.2

2004-03-22 Thread Carsten Ziegeler
Sylvain Wallez wrote: > > >Hi, > > > >to avoid double efforts in the same area, I just wanted to > inform you that I will try to write a new tree processor for > 2.2 in the next few days. > > > >Why? There are several reasons: > >- Reverting to ECM in 2.2 requires some changes to the tree > pr

Re: FYI: New Sitemap Treeprocessor for 2.2

2004-03-22 Thread Sylvain Wallez
Carsten Ziegeler wrote: Hi, to avoid double efforts in the same area, I just wanted to inform you that I will try to write a new tree processor for 2.2 in the next few days. Why? There are several reasons: - Reverting to ECM in 2.2 requires some changes to the tree processor used in 2.1.x anyway

Re: FYI: New Sitemap Treeprocessor for 2.2

2004-03-20 Thread Reinhard Pötz
Carsten Ziegeler wrote: Hi, to avoid double efforts in the same area, I just wanted to inform you that I will try to write a new tree processor for 2.2 in the next few days. Why? There are several reasons: - Reverting to ECM in 2.2 requires some changes to the tree processor used in 2.1.x anyway