ram it do something. WebComponent is equally simple but less often
useful because it can't be a parent to other components.
- Original Message -
From: Jeremy Thomerson
Sent: 07/28/11 01:29 AM
To: users@wicket.apache.org
Subject: RFC: Ten things every Wicket programmer mus
Hi Jeremy,
I think the most important things a wicket programmer should know relate
to building their own set of resuable components.Here are my top ten
on that theme:
1. Build a reusable set of components tailored for your business domain.
2. Solve a few problems then push up the commo
Velocity. Wicket-Velocity project.
-
Software documentation is like sex: when it is good, it is very, very good; and
when it is bad, it is still better than nothing!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/RFC-Ten-things-every-Wicket-programmer-m
On Wed, 27 Jul 2011 18:29:22 -0400
Jeremy Thomerson wrote:
> 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 shoul
My Top 10 (some already mentioned):
1. Use LoadableDetachableModels
2. DefaultModels get detached otherwise you need to detach your model
manually (as Dan mentioned)
3. Setup components to pull in their data and state, typically via
models. This includes pulling in a components isV
Hi!
I don't recall who the author is and the page is currently down (500
server error), but
http://www.small-improvements.com/10-things-about-apache-wicket-i-love
is a post I enjoyed reading earlier this year.
Regards,
Bertrand
On 27/07/2011 6:29 PM, Jeremy Thomerson wrote:
Hello all,
1. Wicket's IOC integrations are really easy to get started with, but there
are some gotchas. Since they inject serializable proxies* *to dependencies
instead of the dependencies themselves, the dependency gets
retrieved/created from Guice/Spring each time a page is deserialized.
Therefore, it's ve
1. How "static" resources work. For a newcomer this can be
shocking/frustrating.
2. Models are a context that holds a reference to a model.
On Wed, Jul 27, 2011 at 5:21 PM, Scott Swank wrote:
> Jeremy,
>
> I just threw together the following, which indicates that at least to
> me Models are wor
Jeremy,
I just threw together the following, which indicates that at least to
me Models are worth 3 of your 10 items.
1. Most components have a backing object of some sort. This object is
referenced via a Model. Significantly, the type of the component and
the model match (e.g. Label has an IMode
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 t
10 matches
Mail list logo
