(note: the first of these depends on acceptance and implementation of my
suggestions concerning TurbinePullService)
1) Make UIManager skin determinable on a per-request or per-user basis.
Per-request: If the tool is configured to be loaded on a per-request
basis (see PullService suggestions) then it should determine the skin to
use by calling a selectSkin(RunData data) method. By default this would
return the skin specified in TR.properties, but a developer can write a
subclass of UIManager that overrides this method and uses
BrowserDetector for example to determine a skin to use. The developer
would then specify this subclass in the PullService config in
TR.properties rather than vanilla UIManager.
Per-user: If the tool is configured to be loaded on a per-session basis
then it can examine the user's temp hashmap for a
"org.apache.turbine.services.pull.util.UIManager.skin" attribute, and if
present use the String value there as the skin to select (falling back
on the default in TR.properties if there is no attribute or the
specified skin does not exist). UIManager would also provide a static
method setSkin(User user, String skin) to allow the application to set a
user's skin selection.
2) Have UIManager use a GenericResources member rather than a Properties
member.
This is because I'd like to have skins specify lists of things as well.
For instance my current webapp draws multi-line charts, and I want to
make the list of line colors configurable. As all the other chart
appearance properties (chart font, chart font size etc) go in the skin,
I think these should too. So I want a getResources method in UIManager
so that I can access other types apart from String.
--
Sean Legassick
[EMAIL PROTECTED]
Czlowiekiem jestem i nic co ludzkie nie jest mi obce
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
