Yes...and I'm repeating myself here Igorbut that'll be fantastic.
On 5/5/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
but its still confusing as hell to have a constructor like
DropDownChoice(String, IModel, IModel)
it just plain sucks
generics will make it much better
DropDownChoice(Str
but its still confusing as hell to have a constructor likeDropDownChoice(String, IModel, IModel)it just plain sucksgenerics will make it much betterDropDownChoice(String, IModel, IModel>)
then at a glance you know where things go.and yes IModel is a tricky beast, mainly because it is so flexible. t
I've never built an app in Swing in my life...so I can't relate. I'm
guessing you'll have lots of users/developers like me going forward
who are in the same boat.
The basic concepts of using a model to populate and access items in
List-bound widgets is very easy to understand...it's when I had t
That's exactly what I said later in my email - once I feel that I'm
not such an amateur in the ways of WicketI'll be glad to
contribute. Even with the concepts I'm still a beginner so I'm not
all that valuable yet.
I'm not dumping on you guys, you've been an incredible help and I
couldn't ha
One thing I found particularly awkward was how models work in some ofthe form widgets,
i.e. DropDownChoice, ListMultipleChoice, etc. Thisis where I found the Wicket learning curve was greater because itwasn't nearly as intuitive as I had expected.Strange thing is they work exactly like Swing Comb
On 5/5/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
Please don't get the impression that I'm entirely without complaints
with my Wicket learning experience.
Hurry, it's an open source project, and anyone can contribute to make
it better! I think so far we have been taking our users quite
seriou
Please don't get the impression that I'm entirely without complaints
with my Wicket learning experience.
One thing I found particularly awkward was how models work in some of
the form widgets, i.e. DropDownChoice, ListMultipleChoice, etc. This
is where I found the Wicket learning curve was great
Hi Ashley,
only some points answered, but maybe the answers are helpful.
Ashley Aitken schrieb:
Clone by serialisation? I guess you mean you serialise and then
un/de-serialise. So you don't serialise to save to disk?
Java has no deep-copy mechanism. Serialization can be used as a workaro
Johan Compagner wrote:
there are other examples
What if a new link doesn't make a new page? But just sets a new modelobject?
Good example! It seems to me that the most common case would be simply
creating a new page in a new window. In this case I can't see why it is
necessary to clone the
almost but not exactly :) if you have fallback in your cluster the session would be replicated from user's node to the backup-buddy node, or multicast to all nodes, or whatever - depending on your fallback strategy. so in this case the session is replicated on every request. but, if you have a fas
there are other examplesWhat if a new link doesn't make a new page? But just sets a new modelobject?We don't test for history anymore. We only do that when we don't detect cookiesIf there are cookies then it works from page 0.
johanOn 5/5/06, John Patterson <[EMAIL PROTECTED]> wrote:
John Patterson
Hello again Igor (et al.),I hope you don't mind me following up your reply. I promise (fingers-crossed) I'll stop after this post ;-)On 05/05/2006, at 2:35 PM, Igor Vaynberg wrote:On 5/4/06, Ashley Aitken <[EMAIL PROTECTED]> wrote: So the pages are only serialised when the session is serialised for
John Patterson wrote:
I thought that whenever I click on a link, a new page object is created?
If the link opens in a new window then why would the page need to exist
in the old page map at all? It was never shown in that window.
So I can understand the use case, can you give me an example
Johan Compagner wrote:
Yes that is it.
The page that you are showing now in a different window can also be
displayed in another window.
So we can't move it because it also have to exist with its different
versions in the pagemap it came from.
I thought that whenever I click on a link, a ne
I don't fully understand why wicket needs to clone the page rather than just moving the page into the new page map?I believe Wicket does this so it can operate correctly no matter which path the user choose (
e.g. to continue in the new page, to still work in the old page, or both). Cloning (thro
Hi John (et al.),On 05/05/2006, at 7:46 PM, John Patterson wrote:Ashley Aitken wrote: So the pages are only serialised when the session is serialised for replication. I am not sure how Wicket (or if it is even within Wicket's scope) handles replication/clustering, but if one were using sticking se
Ashley Aitken wrote:
So the pages are only serialised when the session is serialised for
replication. I am not sure how Wicket (or if it is even within Wicket's
scope) handles replication/clustering, but if one were using sticking
sessions (sessions mapped to the same server in the cluster) th
On 5/4/06, Ashley Aitken <[EMAIL PROTECTED]> wrote:
So the pages are only serialised when the session is serialised for replication. I am not sure how Wicket (or if it is even within Wicket's scope) handles replication/clustering, but if one were using sticking sessions (sessions mapped to the sam
Hello Igor (et al.),Thank you for your reply and explanations.the top container of components in wicket is the page. session keeps references to x number of pages for callbacks and backbutton support. so these are only serialized when replication of the session occurs. So the pages are only seriali
Hi Vincent (et al.),I'm about 90% finished w/ a Wicket/EJB3 (JBoss) storefront solution for my company to start doing consumer web sales. In my personal opinion, Wicket + EJB3 is the holy grail of Java web development...and I'm not being dramatic. It would be hard to convince me to use another fr
with all the talent in this thread its amazing how fast it can deteriorate :)-IgorOn 5/4/06, Nathan Hamblen <
[EMAIL PROTECTED]> wrote:Timo Stamm wrote:> MVC is not Struts! (MVC is *much* older.) I wouldn't even say that
> Struts is MVC.Yeah, but, it's a lost cause. The word anyway. The concept is
Timo Stamm wrote:
> MVC is not Struts! (MVC is *much* older.) I wouldn't even say that
> Struts is MVC.
Yeah, but, it's a lost cause. The word anyway. The concept is enshrined
in component based frameworks, so we can confidently roll our eyes
whenever those Rails barbarians describe the activities
22 matches
Mail list logo
