You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Simon Pepping <sp...@leverkruid.nl> on 2004/01/07 21:37:16 UTC
Attribute processing order (was: Re: [Bug 25803] - [PATCH] PropertyList: Fixes to convertAttributeToProperty and findBaseProperty)
On Thu, Jan 01, 2004 at 12:20:09AM -0000, bugzilla@apache.org wrote:
> ------- Additional Comments From pbwest@powerup.com.au 2004-01-01 00:20 -------
> Alt-Design addresses this problem by the simple expedient of processing
> properties in integer property number order.
In main that is not possible. When a compound attribute is
encountered, a compound property is made in which the components are
set to default values. Then the specified component is set to the
specified value. After this it cannot be told which components were
specified by the user and which were defaulted by the
program. Therefore, before dealing with the compound attribute, the
base attribute should be processed if that is specified as well.
This would be different if the compound property would not be filled
with default components, but with null components.
Regards, Simon
--
Simon Pepping
email: spepping@leverkruid.nl
home page: http://www.leverkruid.nl
public key: http://www.leverkruid.nl/personal/sp.asc
fingerprint: E3BF 7295 9AA8 8B8A C01A 219D FAAC 088C 6B28 F549
Re: Attribute processing order
Posted by "Peter B. West" <pb...@powerup.com.au>.
Simon Pepping wrote:
> On Thu, Jan 01, 2004 at 12:20:09AM -0000, bugzilla@apache.org wrote:
>
>>------- Additional Comments From pbwest@powerup.com.au 2004-01-01 00:20 -------
>>Alt-Design addresses this problem by the simple expedient of processing
>>properties in integer property number order.
>
>
> In main that is not possible. When a compound attribute is
> encountered, a compound property is made in which the components are
> set to default values. Then the specified component is set to the
> specified value. After this it cannot be told which components were
> specified by the user and which were defaulted by the
> program. Therefore, before dealing with the compound attribute, the
> base attribute should be processed if that is specified as well.
>
> This would be different if the compound property would not be filled
> with default components, but with null components.
That's why a flat property space is not only feasible, but desirable.
Compound properties are an unnecessary complication.
Peter
--
Peter B. West <http://www.powerup.com.au/~pbwest/resume.html>