forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cyriaque Dupoirieux <>
Subject Re: Cleaning up v2 - preparing a dispatcher release
Date Mon, 05 Dec 2005 13:07:59 GMT

When will I have to change my *.fv and my contracts ?
I mean, when will I have to update my :
              <forrest:property name="nav-section-toc" nugget="get.tov">
by the contract attribute :

And when will I have to use standalone contracts ?

At the moment, I am waiting for you because you change so many things 
that I don't want to investigate on such or such problem whereas you may 
totally change the way it works.
(That is I don't want to correct something like a pipeline or a 
stylesheet whereas you are going to remove it ;-) )


*Cyri@que Dupoirieux* <>
( 	Tél : - Fax :
Mobile :
+ 	PCO Technologies <>
Burolines - 2 ter rue Marcel Doret
31700 Blagnac

Thorsten Scherler a écrit :

>El lun, 05-12-2005 a las 12:08 +0100, Thorsten Scherler escribió:
>>Hi all,
>>how should we proceed for cleaning up v2?
>>I will soon commit a first working version of the DispatcherTransformer.
>>That means that 75% of the pipelines in structurer/themer will be gone.
>>I would like to use this opportunity and create the final internal
>>plugin (dispatcher) which should replace skins and old views (incl. v2).
>>I want to write this plugin from scratch (meaning to add pipeline by
>>This plugin should contain the structurer and themer as components but
>>not anymore as 2 separate plugins. Further since the markup of contracts
>>have changed I want to use the opportunity to base the dispatcher
>>internally completely on xhtml2. Meaning all contracts are expecting
>>xhtml2 and *not* xdocs as source format.
>In addition the dispatcher will use the new property system that Ross
>used in some plugins. Meaning *all* dispatcher specific properties
>should be removed from the
>b) forrest.core.xconf (2 step)

View raw message