Yeah, I like it so far. Instead of the package images, it might be nice to have some simple illustrations (or none in the case it handles components that everybody knows) and it would be awsome to have short code samples with them. Like:

** Label.* Outputs a single string. See the "HelloWorld" sample.

Java:
add(new Label("message", "Hello World!"));

HTML:
<span wicket:id="message" id="message">Message goes here</span>



OK. I have started doing this.

Here: http://blogs.sun.com/roller/page/geertjan/?anchor=wicket_markup_html_webcomponent_voor

Before I go further, do you agree that it makes sense to provide code within a context? In other words, look at the code snippets for MultiLineLabel. Do you agree that putting LESS code there would not be a good idea because the context of the MultiLineLabel would be lost?

I have put the MultiLineLabel in bold -- both in the Java and in the HTML -- to highlight the point of the code snippet: the fact that it is ABOUT MultiLineLabel.

Before going further with these snippets, I'd like to hear back from at least Eelco about whether this is the right direction.

-- Gj


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to