Re: Ten things every Wicket programmer must know?
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 detach them, how to use them when using an ORM-framework, etc. Ted 2011/7/28 Carl-Eric Menzel > 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, and if they do, our unit tests catch that immediately. The page > doesn't even render if the property model doesn't work, so if you have > a simple "tester.startPage(MyPage.class);" you're safe enough in most > cases. > > This is actually a good point to make for the list: > > - Unit test everything you can using WicketTester. It doesn't do > everything, but it's invaluable as a smoke test at the very least. If > possible, try and check stuff like visibility and enabled state of > your components too. > > Carl-Eric > www.wicketbuch.de > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: Ten things every Wicket programmer must know?
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 immediately. It will bias towards not refactoring domain objects and it migh require thorough coverage of junit tests (... which is good). > The page doesn't even render if the property model doesn't work, so if you > have > a simple "tester.startPage(MyPage.class);" you're safe enough in most > cases. That's a smoke test, but you might need to see the page in various states (repeaters, popups, etc.). > - Unit test everything you can using WicketTester. It doesn't do > everything, but it's invaluable as a smoke test at the very least. If > possible, try and check stuff like visibility and enabled state of > your components too. I agree. But the more thorough your tests are the more covered you are, though the more costly it is and more costly to make changes. For example we have lots of prototype/beta user interfaces and it simply isn't practical to make thorough junit tests for all and we refactor a lot so compounds are not an option. ** Martin > > Carl-Eric > www.wicketbuch.de > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ten things every Wicket programmer must know?
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, and if they do, our unit tests catch that immediately. The page doesn't even render if the property model doesn't work, so if you have a simple "tester.startPage(MyPage.class);" you're safe enough in most cases. This is actually a good point to make for the list: - Unit test everything you can using WicketTester. It doesn't do everything, but it's invaluable as a smoke test at the very least. If possible, try and check stuff like visibility and enabled state of your components too. Carl-Eric www.wicketbuch.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ten things every Wicket programmer must know?
> * "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-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Ten things every Wicket programmer must know?
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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Ten things every Wicket programmer must know?
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 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
RE: Ten things every Wicket programmer must know?
* 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
