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 <hielke.ho...@topicus.nl> wrote:
> * 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: donderdag 28 juli 2011 0:29
> To: users@wicket.apache.org
> Subject: RFC: Ten things every Wicket programmer must know?
>
> Hello all,
>
>  I'm writing an article for a Java magazine and would like to include
> in it a list of "ten things every Wicket programmer must know".  Of
> course, I have my list, but I'd be very curious to see what you think
> should be on that list from your own experience.  Or, put another way,
> maybe the question would be "what I wished I knew when I started Wicket"
> - what tripped you up or what made you kick yourself later?
>
>  Please reply back if you have input.  Please note that by replying,
> you are granting me full permission to use your response as part of my
> article without any attribution or payment.  If you disagree with those
> terms, please respond anyway but in your response mention your own
> terms.
>
> Best regards,
>
> --
> Jeremy Thomerson
> http://wickettraining.com
> *Need a CMS for Wicket?  Use Brix! http://brixcms.org*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
thank you,

regards,
Vineet Semwal

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to