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
pierobo wrote:
Nino.Martinez wrote:
Hi pierobo
I think you need to take a look at listview.. I know you want to let the
user just plainly design the page but what if you gave them a more
graphical editor. That way you could have a general page that had a
listview and added all the components the user selected on his editor
page..
Problem really are that theres a one to one mapping between html and
wicket components. This also is the case with listview, but in your
listview you can have one or more placeholders that will be populated
runtime.. If you do this in conjuction with giving the user the
posibility for uploading special stylesheets then it should be the same
i guess? What do you say?
regards Nino
Thanks for your reply, Nino, but the main features of my CMS are:
1) A structured content capability, with an editor to define the model
2) The freedom of layout
In these times of Ajax and CSS, people love to do their layout. This is the
advantages I would provide, else there is no reason to do the (n+1)-th
CMS...
Surely there are valid reasons for the actual Wicket structure, but I think
that a runtime-inspectable html page not bound to a Java counterpart would
be very useful.
Bye
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
