On 9/1/07, Kirk Israel <[EMAIL PROTECTED]> wrote: > > > > > Wicket is not for newbie OOP developers. We don't pretend that it is. > That > > was never the goal. You need rather solid OO skills to get Wicket. But > if > > you want to learn, I think Wicket is a pretty good "material". > > I'm going to go out on a limb - because I'm sure there are plenty of > anecdotal exceptions, and maybe it'll sound too defensive anyway - > that it's not just pure OO skills that come in useful to bring to the > Wicket party, but expereince with OO UI Skills, and specifically > Swing.
i have just about zero swing experience :) -igor An interesting concept in thinking about Model 2+, homegrown > approaches is how Ajax and DHTM change things. One option new browser > technologies are allowing is MUCH of the work to be moved to the > client, with HTTP only being used when storing things on the server or > at least in the session. So your scenario of multifaceted, stateful > things would really need a good ponder for me to consider how I'd do > that in HTTP-centric approaches. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
