Wicket
  1. Wicket
  2. WICKET-599

Add Development Mode dashboard widget when deployed in development mode

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3.0-beta1
    • Fix Version/s: None
    • Component/s: wicket
    • Labels:
      None

      Description

      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.

      1. screenshot-1.jpg
        10 kB
        Martijn Dashorst

        Activity

        Hide
        Gerolf Seitz added a comment -

        just a quick thought:
        how about providing some sort of "plugin-architecture" so that other components can contribute to the dashboard.
        eg. the jmx-panel could contribute a link that opens a modal window or a popup with the actual jmx-panel inside.

        as a consequence, too many widgets could lead to the dashboad using too much space, so a mechanism to either hide (like martijn suggested) or somehow expand/collapse the dashboard would come in handy.

        Show
        Gerolf Seitz added a comment - just a quick thought: how about providing some sort of "plugin-architecture" so that other components can contribute to the dashboard. eg. the jmx-panel could contribute a link that opens a modal window or a popup with the actual jmx-panel inside. as a consequence, too many widgets could lead to the dashboad using too much space, so a mechanism to either hide (like martijn suggested) or somehow expand/collapse the dashboard would come in handy.
        Hide
        Igor Vaynberg added a comment -

        a couple of thoughts

        i like the plugin idea

        what it can do is either provide a small and large views. initially it can can start out small and when the user clicks the + sign next to it it will expand - kinda like collapse/expand. that way it is up to the plugin to decide if it wants to open a bigger part of itself in a modal simply by not providing a large view and having a link in the small view that opens the modal...

        Show
        Igor Vaynberg added a comment - a couple of thoughts i like the plugin idea what it can do is either provide a small and large views. initially it can can start out small and when the user clicks the + sign next to it it will expand - kinda like collapse/expand. that way it is up to the plugin to decide if it wants to open a bigger part of itself in a modal simply by not providing a large view and having a link in the small view that opens the modal...
        Hide
        Gerolf Seitz added a comment - - edited

        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".

        Show
        Gerolf Seitz added a comment - - edited 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".
        Hide
        Martijn Dashorst added a comment -

        see also WICKET-670

        Show
        Martijn Dashorst added a comment - see also WICKET-670
        Hide
        James Perry added a comment -

        I suggest that this dashboard's "look & feel" should be congruent with its counterpart - Ajax debug dashboard - so it doesn't aesthetically clash.

        Show
        James Perry added a comment - I suggest that this dashboard's "look & feel" should be congruent with its counterpart - Ajax debug dashboard - so it doesn't aesthetically clash.

          People

          • Assignee:
            Unassigned
            Reporter:
            Martijn Dashorst
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development