Still nobody??
fero wrote: > > Hi. Is there any way in this framework how to separate app logic and > presentation. I dont want to store all app behavior (which button is > eneabled for this user with this role, what happens when button is > pressed...) in the web page. > > This is my first wicket application and I was using state machine (SM) as > in swing. Every state represents one webpage but every state has it > interanal state as well (eg. weather editing is enabled...). SM is stored > in session and when new state comes it does in initialization > setResponsePage. When a button is pressed it only call processEvent(Event > e) on the state machine which delegates it to current state. > > It was ok but I have problem with back button in web browser. Wicket has > this problem solved. How can I use this wicket feature to synchronize my > SM? Or should I take another approach? Eg. state will be stored in a > webpage.. > > I like this approach more than code directly in webpage because it is very > readable. > > Thanks for your suggestions. > > Fero > > -- View this message in context: http://www.nabble.com/Presentation-and-application-logic-separation-tf4341077.html#a12372777 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
