[ https://issues.apache.org/jira/browse/WICKET-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juergen Donnerstag updated WICKET-2380: --------------------------------------- Attachment: wicket-2380.patch "I agree with you if i now want to set a setting. I am always thinking what was it. Resource? app? Markup?" If that is the main issue, than we could simply create a class Settings (see attachment) which implements all IXXSettings interfaces via dummy methods. You could than bookmark our/your javadoc page for Settings and voila you have your searchable doc. Copying the javadocs from the various interfaces to the respective Settings method though would be a pain. Meaning, you can't open Settings.java and easily search through the file. > 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: wicket-2380.patch, 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.