Eelco Hillenius wrote: > > On 9/28/07, pierobo <[EMAIL PROTECTED]> wrote: >> >> I.e., in the parent HTML page he could put a block representing a browse >> able list of childs. > > Yeah, I think Wicket is very suitable for what you want to do. > >> So, I need a heavy component oriented framework, and Wicket seems to be >> suitable. >> But, for what I understood, Wicked is driven by pages. I would instead >> drive >> the presentation by some action (i.e. >> www.mycms.com/view/MyEntity/id/123), >> look into information system, find the suitable html page and then render >> it. > > You can implement that just the same. Replace your idea of actions by > pages, and use a custom URL mapping to achieve that. There's multiple > ways to do it. > > Learn how bookmarkable pages (would be your actions) work, and how to > dynamically construct Wicket pages (investigate panels). > > Eelco > >
Thanks for your reply, that's what I think after reading better this forum. And thanks to you all for remembering me that ever exists a better way to do things. Your posts about Wicket and Model 2 approaches helped me to match my OOP passion and my Web programming needs. Hope I can follow this way like I would. Bye -- View this message in context: http://www.nabble.com/Is-Wicket-suitable-for-my-CMS--tf4536847.html#a13048614 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
