Also, while I used fo:element constants in my
experiment, it is clear to
me that such an approach does not work well for
extension elements.
[Glen Mazza]
Oh no--I hope you don't mean we have to revert to
strings for those?
No, not at all. It is just that the element id's for extensions must be
Glen Mazza wrote:
There's about 10-15 differences between Alt-Design and
HEAD (my unresearched guess), and getting us on to INT
constants--the no-brainer--removes one of them. Peter
hopefully will start to see more of the "theory" of
Alt-Design in HEAD, if not exactly the same
implementation (e.g.
--- Finn Bock <[EMAIL PROTECTED]> wrote:
> I think Peter was refering to the fact that you
> placed the file in the
> src/java/org/apache/fop/fo/
> directory, but it used to be in the
> org.apache.fop.fo.properties.
> package. Indeed, the package statement in the
> Constants still reads
>
[Glen Mazza]
It's been in that location for at least several
months--it's just that we never saw it because it was
autogenerated and never checked into CVS. (As for its
location--it is used by the FO classes and it also has
some FO constants and other enumerations in there, so
it is OK remaining
It's been in that location for at least several
months--it's just that we never saw it because it was
autogenerated and never checked into CVS. (As for its
location--it is used by the FO classes and it also has
some FO constants and other enumerations in there, so
it is OK remaining there, I think
> -Original Message-
> From: Peter B. West [mailto:[EMAIL PROTECTED]
> >
> >
> > 1.1 xml-fop/src/java/org/apache/fop/fo/Constants.java
> >
> > Index: Constants.java
> > ===
> > /* $Id: Constants.java,v
[EMAIL PROTECTED] wrote:
gmazza 2003/12/14 17:07:50
Modified:.build.xml
src/codegen propinc.xsl
Added: src/codegen constants.xml constants.xsl foelements.xml
src/java/org/apache/fop/fo Constants.java
Removed: src/codegen allprops.xml g
