When I first started looking at Wicket it was all about Borders for page templating and consistency. Recently, evaluating Wicket again, I see Markup Inheritance is boasted quite a bit, including the article on JavaLobby.
My question is, is MI now the preferred way to layout multiple pages keeping
it is easier to use), but there are still plenty good use cases
for Border. MI for example can not be used inside a Panel or Borderbordering a specifc html tag/region (compared to the whole Page orPanel as MI does).JuergenOn 4/12/06, Gregg Bolinger
[EMAIL PROTECTED] wrote: When I first started
/12/06, Gregg Bolinger [EMAIL PROTECTED] wrote: Interesting that you mention that about Panels. I have been trying to use
Panel and MI without success.Basically, I have a BasePage that contains a reference to my Header (which extends Panel and has it's own contents) and I have the Header.html.But
I just purchased Pro Wicket today and have made it almost through chapter 3. I've submitted about 4-5 Errata's so far. Just small things that the technical reviewer probably should have caught since most are source code errors.
Aside from that, I am enjoying the book. I admit that I haven't looked
That doesn't really contain Erik was stating. At least not that I could find. If you look here, http://myfaces.apache.org/tomahawk/index.html and then on the left there is a Components section with information about each component. That's what Wicket needs for both the core and extension
/body
/html
Thanks for any tips:
Gregg Bolinger
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere
DOH!!! Thanks. Geez.
Martijn Dashorst wrote:
The line in your markup: form id=manageColorsForm
should be:
form WICKET:id=manageColorsForm
Martijn
On 2/4/07, Gregg Bolinger [EMAIL PROTECTED] wrote:
I can't figure out what the heck I am doing wrong. Been reading Pro
Wicket
