That's a good analysis, and what we usually go through when we decide on
an attribute or a skin property.
I personally don't think we'd need it at the specific level, which I've
been calling 'per instance'. I think global to the processTrain within
an application/skin is good enough.
- Jeanne
[EMAIL PROTECTED] wrote:
Hello,
I could do that as well since it would indeed be a nice enhancement,
However, I don't know what would be best between a skin property and a tag
attribute. Pro of skin property is that since the skin knows what kind of
images it use, it would be the best placed to know how many station can be
safely rendered. However, skin property is global and will prevent any
overload at specific level. Maybe we could have both, a
-default-visible-number-stations and a tag atttribute, the tag attribute,
if present would be the one used?
Regards,
Simon Lessard
Fujitsu Consulting
----- Forwarded by Simon Lessard/NOTES on 2006-07-06 16:26 -----
Jeanne Waldman <[EMAIL PROTECTED]>
2006-07-06 16:20
Please respond to adffaces-user
To: [email protected]
cc:
Subject: Re: ProcessTrain Number of "Stops" before
"segmenting" configurable?
This could be an enhancement. It would be a good example of using a
skinning property.
You could add a skin property, like -ora-number-visible-stations (note,
I'll have to follow through on the thread regarding changing the -ora-
to something else).
So in the skin file you'd do this:
af|processTrain {-ora-number-visible-stations: 10 }
(The default would be 6)
Then we'd need to change the train renderer to honor this number instead
of hard-coding it to 6. Then ALL processTrain components that are
defined in the application will use this property value defined in the
skin.
- Jeanne
[EMAIL PROTECTED] wrote:
Hello,
Threshold is currently fixed to 6 visible stations and add a 7th that is
the arrow pointing to the next set of steps. This parameter is not
configurable at this time.
Sorry,
Simon Lessard
Fujitsu Consulting
