In my humble opinion:
The most important thing that you should know are models en how powerfull
they can be used.
Models can be quite confusing, especially to programmers who've just started
using Wicket.
I remember how I struggled with the concept, when I started to use Wicket.
How and when to d
Hi!
>> > * "compressing" code by use of ids matching property names combined
>> > with CompoundPropertyModel and/or PropertyListView
>>
>> Oh.. that will lead to fragility.
>
> It can, but in my experience it hasn't. Our domain objects rarely
> change, and if they do, our unit tests catch that imm
On Thu, 28 Jul 2011 11:10:30 +0300
Martin Makundi wrote:
> > * "compressing" code by use of ids matching property names combined
> > with CompoundPropertyModel and/or PropertyListView
>
> Oh.. that will lead to fragility.
It can, but in my experience it hasn't. Our domain objects rarely
change,
> * "compressing" code by use of ids matching property names combined with
> CompoundPropertyModel and/or PropertyListView
Oh.. that will lead to fragility.
**
Martin
>
> - Tor Iver
>
> -
> To unsubscribe, e-mail: users-unsubsc
Also:
* How to avoid excessive use of Labels and AttributeModifiers (with
ResourceModels) just for l10n, by using wicket:message in the template instead
* "compressing" code by use of ids matching property names combined with
CompoundPropertyModel and/or PropertyListView
- Tor Iver
---
what hielke said +
how to
-- use images from database/filesystem
-- resources as already mentioned including shared resources..
-- show error alert next to formcomponent
-- reusability +good coding practises as already mentioned
On Thu, Jul 28, 2011 at 12:39 PM, Hielke Hoeve wrote:
> * How mode
* How models work and best practices for wicket/hibernate
* how ajax behaviors should be used
* how are resources defined and used
* how to make a multilingual site using resource models
etc
Hielke
-Original Message-
From: Jeremy Thomerson [mailto:jer...@wickettraining.com]
Sent: donder
