Good luck with such solutions. If you want to build things like that, you've got basically two approaches. Use GWT (or something alike) - code logic in limited subset of java and have it magically translated to javascript. This seems somewhat fragile and limiting to me, but I don't have enough experience with it to judge.
Other approach is to build the thing using "raw" javascript. Now I've done quite a lot of javascript work, and i can tell you that it's not the most productive way. Java (as any strongly typed) language has tremendous maintainability and refactoring advantage. Compared to that, javascript with all it's quirks, browser specific implementation (hell, it's not even called JavaScript in IE) and a cumbersome object model (no, i don't think prototyping is that cool), weak static checking and no refactoring support doesn't seem to be the right development platform to me. -Matej 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. > > 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] > >
