Actually, I don't think it is too bad to go for a one page thing. You can get a long way by switching panels etc. And Ajax heavy pages probably look more like that too. The only thing to consider is whether you want some of your destinations to be bookmarkable.
Eelco > > > Question 3: > > In our design, we want the customer to be able to lay the > > components in a simple, stacked, sequential layout for the future, so > > we actually have one Page/PageLayer, which gets the order of the > > components and calls them accordingly. So I will probably be using > > something like ListView with sequential Panels inside, which will be > > the actual components. Has anyone tried something similar, meaning a > > one page app instead of the regular multiple pages approach? Will > > there be any problems bugging me in the future if I choose this approach? > > > > This is possible. But wouldn't be my solution. > Don;t make big monolitic things. Divide it and make easy to use small > things. > you can ofcourse use panels and use setVisible or replace panels in the main > page. > > johan > > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
