Nino.Martinez wrote:
>
> Yes, but I dont see how this is not possible done with the solution I
> suggest, unless you actually want the user to produce the html file
> themselves...?
>
> -Nino
>
>
If you mean an editor I could write to manage authoring of user's pages, it
is not what I need. There are plenty of CMS that do that, much better then I
could...
Yes, I would let the users (power users) write the pages themselves. And
then put wicket markup when they want to wire the structured data. This is
reasonable for an html designer, thanks to Wicket's simple syntax.
Yet, I could provide blocks of grouped data. E.g. for a ecommerce page, with
a model Order 1-->N Product, I could provide a Wicket component that shows
the list of Products, wired with actual page's order.
For now, it's only brainstormig. I've the working persistence layer, and now
I'm evaluating a presentation framework. So, further ideas are welcome :-)
This is a possible approach with Wicket that came to my mind, but I'm a
newbie of it: HTML written by user take place in a given subdir. When a page
from this subdir is requested, the Wicket filter pass it to the parser, that
checks and manage the Wicket components found.
Don't know if this task is compatible with actual lifecycle of Wicket pages,
and/or its API.
Just digging... :working:
--
View this message in context:
http://www.nabble.com/Is-Wicket-suitable-for-my-CMS--tf4536847.html#a13189803
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
