Forrest questions

[Victor Mote <vi...@outfitr.com>]

Joerg, Keiron, et al:

I want to add my congratulations for the good work on the new web site. It
not only looks good, but loads noticeably faster on my connection. I also
see (and like) the "dev" tab.

As I understand it, the web site will eventually be updated daily
automatically. This raises the question in my mind of how we (or any other
project for that matter) will handle the differences between released
versions and versions under development. Right now, for example, we have
some doc that is basically for 0.20.4, and that we would want most users to
find. However, we also have docs that are being updated frequently that are
related to 1.0 (or the trunk or HEAD, if you will), which developers will
want to find, and which those using cvs will want to find. I think it is
useful to have both of these on our web site, perhaps on different tabs
(??).

Also, I have an html document that pulls together our "Implemented" and
"Limitations" pages into one table with a column for each of the
implementation compliance levels, color-coded to show what is complete and
what is not. I did not see a DTD on the Forrest web site that fits this type
of information. However, it looks like we can tell it not to validate
certain documents. I'll be glad to convert it to XML with a stylesheet for
HTML, or submit it as HTML. I'll also be glad to build and submit a DTD to
Forrest, as this might be useful for other projects as well. I'm just not
sure what is easier for you guys to deal with right now. What do you prefer?

Victor Mote


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Forrest questions

[Keiron Liddle <ke...@aftexsw.com>]

On Thu, 2002-11-07 at 10:04, Victor Mote wrote:
> Joerg, Keiron, et al:
> 
> I want to add my congratulations for the good work on the new web site. It
> not only looks good, but loads noticeably faster on my connection. I also
> see (and like) the "dev" tab.
> 
> As I understand it, the web site will eventually be updated daily
> automatically. This raises the question in my mind of how we (or any other
> project for that matter) will handle the differences between released
> versions and versions under development. Right now, for example, we have
> some doc that is basically for 0.20.4, and that we would want most users to
> find. However, we also have docs that are being updated frequently that are
> related to 1.0 (or the trunk or HEAD, if you will), which developers will
> want to find, and which those using cvs will want to find. I think it is
> useful to have both of these on our web site, perhaps on different tabs
> (??).

Some of these issues have been raised with forrest, but not answered as
far as I know.

The "dev" tab is actually meant to be the user etc. docs for 1.0dev,
maybe a better name could be used.



> Also, I have an html document that pulls together our "Implemented" and
> "Limitations" pages into one table with a column for each of the
> implementation compliance levels, color-coded to show what is complete and
> what is not. I did not see a DTD on the Forrest web site that fits this type
> of information. However, it looks like we can tell it not to validate
> certain documents. I'll be glad to convert it to XML with a stylesheet for
> HTML, or submit it as HTML. I'll also be glad to build and submit a DTD to
> Forrest, as this might be useful for other projects as well. I'm just not
> sure what is easier for you guys to deal with right now. What do you prefer?

With a stylesheet would probably be better.





---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org