forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cyriaque Dupoirieux <Cyriaque.Dupoiri...@pcotech.fr>
Subject Re: Dispatcher v
Date Fri, 20 Jan 2006 13:30:05 GMT
Thorsten Scherler a écrit :
> El vie, 20-01-2006 a las 11:36 +0100, Cyriaque Dupoirieux escribió:
>   
>> Thorsten Scherler a écrit :
>>     
>>> El vie, 20-01-2006 a las 10:44 +0100, Cyriaque Dupoirieux escribió:
>>>   
>>>       
> ....
>   
>>>   
>>>       
>> Ok, but what is the content in prolog ?
>>     
>
> Any given "String" that is not within an element tag. You only can use
> certain elements such as comments, pi, ... in the prolog but not a
> string. A string *has to be* surrounded by a root element. I meant the
> example literally.
> <?xml version="1.0" encoding="UTF-8"?>
> string-prolog
> EOF or elements
>
>   
Thx, I will find what happens.
>> ....
>> For pelt we need to migrate the branding-theme-profiler.ft.
>> (But I am still thinking to drawn nearer the csszengarden xhtml style 
>> which is much more consistent and let devs easily customise with css help.
>> So I don't know if we should migrate the contract now or redesign the 
>> xhtml output - of every contracts :-[ )
>> (Maybe I am going to start a new theme for this with a design documentation)
>>     
>
> :) My dream seems to finally come through having forrest output
> csszengarden like html. A while ago I thought about the possibilities of
> such a theme (back then I called them skins): 
> http://marc.theaimsgroup.com/?l=forrest-dev&m=108861988507391&w=2
>   
I wasn't born yet ;-) .
> Count me in and yes we need a new theme for that. 
>
>   
Ok I've downloaded the source of the csszengarden page to understand 
their layout,
> Anyway still we need to look again in our default output of contracts
> and *should* try to remove design specific markup where ever possible. 
>
> e.g. search-input.fv starts with <div class="search-input"> which should
> be better extracted to the structurer to enhance re-usability of the
> contract in different themes.
>   
Ok too,
> IMO not all of the contracts need to be redesign but quite a lot, but
> this work is well invested and needs to be done in order to minimize
> maintenance for themes in general. 
>
>   
>> For common, we still miss some contracts (I think between 5 and 10...)
>>
>>     
>
> Ok, I will hopefully have time for a closer look on the weekend. Good on
> ya, Cyriaque.
>   
Good,

Cyriaque,
> salu2
>   

Mime
View raw message