forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: [VOTE] Usage of file.hint.ext convention
Date Mon, 02 Sep 2002 13:13:53 GMT

Marc Portier wrote:
> Steven Noels wrote:
>> Nicola Ken Barozzi wrote:
>> <snip/>

>>> Users that want to write a generic document use that dtd.
>>> All other content that must be "skinned" by forrest must be 
>>> pregenerated by other tools to give that dtd.
>> +1
> ? we are not saying that two step view means that the first step is done 
> with ant-style-tasks is it?

Also. Not only.

> "pre-generated" I also like to read as have a pipeline for it.

Yes, also this.

> as for:
>>> We still have status.xml... etc files that get automatically 
>>> transformed to that format.
>> Yep - and I like that.
> And we should allow for more of these, including user-defined ones.
> I mean: solve this in the URI design for our own future types, and make 
> it available as well.


> <snip />
>>> The point is, can we use them in statically generated documentation?
>>> We cannot.  :-/
> I know I made a similar statement on this earlier, however been thinking 
> along these lines:
>> I fail to see why, but I might be stuborn ;-)
> someone should maybe just check...
> I think the static generation process of cocoon would
> - in case it finds a link of the kind 
> href="addressing-part/name.rendering-type?hint=source-type"
> - just save the resulting file under name.rendering-type
> - currently the serializer would leave the jucky ?hint=source-type in 
> the href, but the webserver we put it on would survive that anyways 
> (since it is not going to take the parameter in account for delivering 
> static content)
> In future it would be nice if the CLI version would remove the ?-trailer 
> on none http://-leading URI's though,
> by the way Nicola: the CLI should also be the one that "relativizes" all 
> the none http://-leading hrefs in our generated html as well :-D
> that is the correct way to produce a bunch of relative interconnected 
> pages that can be placed where-ever (not just in the /forrest) on a 
> webserver. (and detaches the solution from the webapp that doesn't have 
> this concern)

Gee I didn't know they became absolute from relative, are you sure?
Can you give me an example?

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

View raw message