Yeah. I actually think I proposed something like this, or at least +1-ed one at more than a year ago. You'll have to dig in the archives to find out why other people didn't agree back then, but I still think it's much easier for users to discover something just because it has an obvious name, and not to worry about that one extra class.
Eelco On 5/4/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
In my work project, I've added and frequently use an EmptyPanel which is simply a panel with empty markup. Although you can do the same thing with WebMarkupContainer or implement this yourself, it does seem like a nice conceptual addition, particularly for newbies who might not think "hmm... i want an empty panel instead of this fancy panel if the user isn't logged in... oh WebMarkupContainer looks about right..." ;-) Anyway, I thought I'd mention it in case others feel this would be a nice addition to core. -- View this message in context: http://www.nabble.com/EmptyPanel--tf3692546.html#a10324363 Sent from the Wicket - Dev mailing list archive at Nabble.com.
