Three quick questions getting started with Wicket (I'm sure I'll have more later, but I'm glad to document what I learn on the Wiki--I like documenting what I discover). I've only started playing around but, assuming that a few things can be handled, I think I'm going to choose Wicket:
1) In one place, my site needs to use frames. (Yes, I know they're unpopular, but it is important here). There will only be one nav/control frame while the other will just contain content). Will this cause any problems with Wicket? Can I use the existing Models to do this? 2) I am going to be doing some basic AJAX stuff. I know that Wicket doesn't yet have formal support for it, but I presume that loading some "mini-pages" via XmlHttpRequest from some Javascript in my pgaes won't break anything? Correct. 3) I want to maintain state for my users when the come back, but I don't want them to have to register. I assume I should get/set a cookie using the RequestCycle's WebResponse? [BTW: When you do work on AJAX support, I highly recommend using the DojoToolkit. It's just getting underway, but it has a huge amount of support in the Javascript/DHTML world and will probably become the de facto standard. I also mentioned this on the Issue Tracker.] Thank you very much! ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
