On Sun, 25 Sep 2005 01:22 am, Andreas L Delmelle wrote:
> On Sep 24, 2005, at 19:09, Andreas L Delmelle wrote:
> > As to how to integrate this: no clear idea ATM, but I'll give it
> > some thought.
> > Maybe Finn or others have a few ideas to add?
> On second thought, maybe all you really need is to subclass
> EnumProperty to DominantBaselineProperty, and give it three instance
> variables (or an additional ScaledBaselineTable variable)
> corresponding to what is referred to as the
> dominant-baseline-identifier,
> baseline-table and baseline-table-font-size.
> The subclass could add one (or three) additional getXXX() methods,
> which would return the associated value(s).
> getValue() or getEnum() would always return the original enum value,
> but the additional getters would provide access to the
> scaled-baseline-table that is the result of the enum value...
> What do you and Finn or others familiar with the fo.properties
> package think about that? Would this work?

Hmm, not sure about this one. The actual rules for computing his 
compound value are actually a bit involved and require information 
possibly not readily available to the property system.

Yes, let's ask others on this list for input...

> Cheers,
> Andreas


Reply via email to