i think two things will alleviate this problem. the first is building modular applications where there are relatively few components on a panel/page/form/unit... but as you point out, this first option may reduce overall complexity, but it will never give you a transparent view of the application from the markup. i think the second more important thing that will eventually fix this whole issue is the creation of eclipse/netbeans/idea plugins for wicket. one can imagine a little red squiggly appearing underneath component names that don't have matching code on the java side... or a tooltip that shows you what type of component is being referenced in your markup file when you hover over the "wicket-xyz" name. in general, there is a whole world of possibilities there for supporting serious RAD development of wicket apps in IDEs. there might even be a little money to be made.
jon
[EMAIL PROTECTED] wrote:
I am running into some issues with how easily I can create and reference components without things starting to get out of hand.
For example, if I a am creating a new page (call it MyPage.html and MyPage.java) and that page uses/references components from another package (or some third party wicket library), there is really no way to tell where that component came from without looking at the MyPage.java file directly.
By just looking at the MyPage.html file it begins to get difficult to distguish one component from another strictly by its name when you are using a lot components in a page and across a large application. Here is a very simple example:
MyPage.html: <html> <body> <span id = "wicket-somewidget"/>
<span id = "wicket-fancylabel"/> </body> </html>
From looking at the component being reference above, "somewidget", Ireally can't tell what type it is or where it came from without going to the java class file MyPage.java. It also gets more difficult if that widget is actually is created in a subclass of MyPage.java or some helper class.
I suppose I can put a comment in the html file just before referencing the component like:
MyPage.html <html> <body> <!-- "somewidget" is of type com.acme.widgets.SomeWidget --> <span id = "wicket-somewidget"/>
<!-- "fancylabel" is of type com.acme.widgets.FancyLabel --> <span id = "wicket-fancylabel"/> </body> </html>
But I was wondering if wicket should deal with this directly by requiring the type of component to be defined in the html file? It also might be helpful for future wicket tools that may aggregate the components of a page together to give GUI designers a more compete picture of what they are building.
Is there a way to do something like this now? Can anyone give me any advice on how to best reference a large number of components when building a large application.
Thanks, Sam
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
