Hi, trying to test Wicket pages or components I find it sometimes annoying to try and figure out the paths of various components. Yes, we have the possibility to get the paths from the UI itself, but when testing a component in isolation or a page that can reached only with a long workflow, I feel it would be better to have a more direct way.
In the spirit of the print(dom) utility that we have to dump down a xml document returned by GeoServer services, I think it would be nice to have a print(Component/Page) that prints in text the component hierarchy, with ids, visibility status, and eventually the model values, something like: form [] name [John] surname [Doe] hiddenField (h) [secret] where the value is in square brackets and (h) marks hidden components. We could also consider adding a third param like the component class (optional, so it would be print(component, showClasses, showValues)) What do you think? I looked around but could not find such an utility already made. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
