After my last post I went away to play in the code for a while.
Mostly to see what is necessary to isolate a minmal set of
classes related to Property handling.
What I found is:
1) Property is ubiquitous: every client class knows what package
it lives in. As a planning point, I better think
John Austin wrote:
After my last post I went away to play in the code for a while.
Mostly to see what is necessary to isolate a minmal set of
classes related to Property handling.
What I found is:
1) Property is ubiquitous: every client class knows what package
it lives in. As a planning
--- Peter B. West [EMAIL PROTECTED] wrote:
And now for a little digression on code generation.
My own view of code
generation by XSLT transformation can be summed up
as:
Why, Peter, you're in disagreement with everyone else
on this issue! (So what else is new? ;)
* the canonical
Glen Mazza wrote:
--- Peter B. West [EMAIL PROTECTED] wrote:
And now for a little digression on code generation.
My own view of code
generation by XSLT transformation can be summed up
as:
Why, Peter, you're in disagreement with everyone else
on this issue! (So what else is new? ;)
Everyone
J.Pietschmann wrote:
Peter B. West wrote:
More less than more, I should think. Parsing is inherently generic.
E.g., I assume that you would use the same tokenizer and first-level
parser.
At the tokenizer level, sure. However, the spec provides for
a wildly varying spectrum of
with unsynchronized. That was
extremely encouraging news, and is presumably down to improvements in
the JVM.
I myself take issue with:
- Property handling is hard to understand, with a gadzillion of
indirections and odd instanceof and casts and of course, the
XSL generated code
Peter B. West wrote:
J.Pietschmann wrote:
And yes, it is absolutley choc-a-bloc with instancesof and casts, which,
Should read absolutely chock-a-block; it is not to be confused with
the consumption of chocolate.
- Have a FONode method which goes through the attribute list and
+ gets
J.Pietschmann wrote:
There should be no need to actually store for many properties most
of the data types which can be specified in an XML attribute, for
example font-size can always be resolved to an absolute value. Bad
things are for example alignment-adjust which must still store an
Property Handling
-
During XML Parsing, the FO tree is constructed. For each FO object (some
subclass of FObj), the tree builder then passes the list of all
attributes specified on the FO element to the handleAttrs method. This
method converts the attribute specifications
