Re: [PATCH] upgrade javadocs

["J.Pietschmann" <j3...@yahoo.de>]

Victor Mote wrote:
> FOP Developers:
> 
> PATCH
> =========
Well, applied.

J.Pietschmann


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

RE: [PATCH] upgrade javadocs

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

On Fri, 2002-09-13 at 09:11, Victor Mote wrote:
> Thanks. I'll jump back over to that thread & continue with it shortly. I am
> currently working on a document that comprehensively lists the W3C standard
> objects & properties in columns for the 3 levels of compliance, and FOP's
> support for them.

Do you know about the fo schema that is in cvs. I think this already has
a lot of that information.
look in: docs/foschema/

> Also, has any thought been given toward merging the development branch
> changes into the trunk? It might be better to do that sooner rather than
> later: 1) it might eliminate some duplicate documentation and style cleanup
> work, 2) it might make it easier for more developers (especially us lighter
> ones) to move over to trunk work. The only drawback I can see is that it
> probably means merging twice. However, my experience with merges leads me to
> believe that there aren't any great efficiencies gained from doing them in
> bigger batches. In other words, doing a big merge now, and a smaller one
> later (for bug fixes) probably won't cost much, if any, more than doing one
> big one later.

Thats a good idea.
Only some of the changes apply. This would make it easier to keep track
of the appropriate changes that need to be added to the trunk.

I don't think it will be possible or useful to do a large merge.


Keiron



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

RE: [PATCH] upgrade javadocs

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

J.Pietschmann wrote:

> Victor Mote wrote:
> > FOP Developers:
> >
> > PATCH
> > =========
> Well, applied.

Thanks. I'll jump back over to that thread & continue with it shortly. I am
currently working on a document that comprehensively lists the W3C standard
objects & properties in columns for the 3 levels of compliance, and FOP's
support for them. It combines information that is currently on 2 or 3 pages
on the FOP site & hopefully can serve not only to tell users what to expect,
but also as a kind of checklist for developers working toward compliance. I
haven't bothered to learn our current documentation scheme, thinking that
Forrest will be implemented soon. Are we close enough on Forrest that I
should just wait a bit? (Not prodding, just inquiring.)

Also, has any thought been given toward merging the development branch
changes into the trunk? It might be better to do that sooner rather than
later: 1) it might eliminate some duplicate documentation and style cleanup
work, 2) it might make it easier for more developers (especially us lighter
ones) to move over to trunk work. The only drawback I can see is that it
probably means merging twice. However, my experience with merges leads me to
believe that there aren't any great efficiencies gained from doing them in
bigger batches. In other words, doing a big merge now, and a smaller one
later (for bug fixes) probably won't cost much, if any, more than doing one
big one later.

Vic


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