[
https://issues.apache.org/jira/browse/WICKET-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558849#action_12558849
]
seitz edited comment on WICKET-599 at 1/14/08 3:39 PM:
--------------------------------------------------------------
also, a component may register itself via the Initializer concept.
again eg jmx-panel: when wicket-jmx.jar is in the classpath, the jmx-panel is
added automagically, so users don't have to bother registering widgets
manually, only to get compilation errors when the jar is removed.
it should still be possible to turn certain widgets "off".
was (Author: seitz):
also, a component may register itself via the Initializer concept.
again eg jmx-panel: when wicket-jmx.jar is in the classpath, the jmx-panel is
added automagically added, so users don't have to bother about it.
it should still be possible to turn certain widgets off manually.
> Add Development Mode dashboard widget when deployed in development mode
> -----------------------------------------------------------------------
>
> Key: WICKET-599
> URL: https://issues.apache.org/jira/browse/WICKET-599
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Affects Versions: 1.3.0-beta1
> Reporter: Martijn Dashorst
> Fix For: 1.4-M1
>
> Attachments: screenshot-1.jpg
>
>
> It is considered bad practise to deploy your wicket application in
> development mode in a production environment. Because several features
> beneficial to development will make an application behave less than optimal
> when confronted with lots of users and requests.
> The idea is to extend the Wicket Ajax Debug link and make it a full fledged
> panel that is *always* visible when working in development mode. There will
> not be a setting to turn this off. If someone wants to have the development
> features available in a production environment, these can be enabled using
> the settings object.
> Another idea, thanks to Korbinian Bachl is to add the Inspector Bug to this
> widget, to enable introspection of the components on the page.
> The widget should be movable (so it does not obscure other markup elements),
> and it should have a hide link to enable screen shots whilst still in
> development mode (very useful when writing articles and books).
> A screen shot for this feature can be seen attached to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
