igor.vaynberg wrote:
>
> at its core all a cms does is display some user generated content. that
> can
> be accomplished by simply doing this:
>
> class cmspage extends webpage {
> public cmspage(pageparameters params) {
> long pageid=params.getpageid();
> string html=database.loadpa
Shams Imam wrote:
>
> Then you could maintain a java class corresponding each html file the user
> can create.
> When the user saves his html you could store meta information for that
> html
> file like what all wicket-panels it uses. Then inisde the java class you
> can
> process this meta inf
igor.vaynberg wrote:
>
> for what it is worth i will be creating a cms in the near future using
> wicket. my idea is simple. the cms is a single wicket page. the users have
> a
> special tag they use to define dynamic components like type=foo param1=param2/>. the page itself has a single repe
Shams Ali-2 wrote:
>
> Hi,
>
> I think u might consider using getVariation()of WebPage class and
> dynamically generated htmls along with some tricks in the java code :).
>
> Hope it helps.
>
> Shams
>
I need the opposite :-), static HTML pages and dynamic management...
If you want, give a
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
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
> listv
Eelco Hillenius wrote:
>
> On 9/28/07, pierobo <[EMAIL PROTECTED]> wrote:
>>
>> I'm doing an evaluation of some java web frameworks for doing the
>> presentation layer of our CMS.
>> We already have the backend, made with Spring/Hibernate.
>>
>
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.
>
&
I'm doing an evaluation of some java web frameworks for doing the
presentation layer of our CMS.
We already have the backend, made with Spring/Hibernate.
The behaviour of the CMS should be:
1) (Power) user draws the data model he want to store in the CMS (a sort of
entity-relation diagram);
2) Th
