[
https://issues.apache.org/jira/browse/WICKET-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915271#action_12915271
]
Sven Ludwig edited comment on WICKET-2380 at 9/27/10 7:00 AM:
--------------------------------------------------------------
In our project we successfully established an API called WindowSettings, which
from the developers point-of-view replaces PopupSettings. We wanted to expose
such settings via normal properties. Compared to our API, PopupSettings has a
pretty complex usage, when you consider inexperienced developers or
externalized configuration. I vote for this API improvement to be included.
Please find a suggestion for the class WindowSettings attached (english javadoc
to be written).
was (Author: sludwig):
Suggestion for clear and really-easy-to-use WindowSettings.
> Simplify settings API
> ---------------------
>
> Key: WICKET-2380
> URL: https://issues.apache.org/jira/browse/WICKET-2380
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.0
> Reporter: John Patterson
> Attachments: WindowSettings.java
>
>
> There are a million and one settings for wicket and I normally don't have the
> faintest idea in where to look for them. Content assist does not help much
> because the Application API is enormous. I suggest making a single
> Application getter getSettings() which then has getSessionSettings(),
> getDebugSettings, getFrameworkSettings(), getResourceSettings() ...
> What would really make it easier for me to use is if there was also a
> combined option: getAllSettings() that returned a delegate object that
> implements all of the settings interfaces ISessionSettings etc.
> This uber-settings "view" would make it a lot easier to find a setting which
> you know the name of but not wether of which type it is.
> Just an idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
