[
https://issues.apache.org/jira/browse/WICKET-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693979#action_12693979
]
Jeremy Thomerson commented on WICKET-670:
-----------------------------------------
Took it to discussion on dev@ and everyone was favorable.
I am starting development on this in my experimental branch.
Here were the additional comments from the thread ():
*** Martin Grigorov:
Additional candidate for this sub-project:
- org.apache.wicket.markup.html.debug.PageView (wicket sub-project)
(maybe you wont be able to move it for 1.4)
*** Igor Vaynberg:
martijn and matej and i talked about having a floating console that
can be enabled at runtime and that would host all these kinds of
tools. so basically extending or encorporating our existing ajax
console into something much more powerful. seems like if we move away
from having these tools as pages and making them panels we can create
a console.
*** Jeremy Thomerson:
Yes - I agree. I think that would be the next step. I've been doing some work
on a PHP site lately - which at first I thought I was going to hate. But
everyone at that company only knew PHP - so I chose to go with Symfony [1] -
and I've enjoyed it. Anyway, the point is - they have a great floating toolbar
at the top right of the screen in development mode that gives you each query
that was run, logging output for that request, timing for different cycles of
the request, etc. It's great.
I'd love to build something like it that would allow you to register various
contributors to add different details to the debug bar.
> Bring back the inspector!
> -------------------------
>
> Key: WICKET-670
> URL: https://issues.apache.org/jira/browse/WICKET-670
> Project: Wicket
> Issue Type: Wish
> Components: wicket
> Affects Versions: 1.4-M1
> Reporter: Jonathan Locke
> Priority: Minor
> Fix For: 1.5-M1
>
>
> My copy of the inspector is completely broken. It's a shame that this useful
> tool is not really supported anymore. It gives people a sense of confidence
> when they can navigate their wicket session and see all the components with
> the inspector.
> To bring the inspector back, we could do the following things:
> 1. fix the inspector
> - it needs to factor out the stack trace metadata so sizes of things are
> more accurate
> - my inspector causes every page viewed after using it to fail with a page
> expired exception (!)
> 2. add a security setting setInspectorEnabled() which defaults to false
> (disabled) and unless
> the inspector is explicitly enabled, the constructor of every publicly
> accessible bookmarkable
> page in the inspector package throws an IllegalStateException() with an
> explanation of what
> you must do to safely use the inspector in your application (add security to
> the pages via
> wicket-auth-roles or some other means and call setInspectorEnabled(true)).
> then we can all enjoy the return of the inspector!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
