Hippo is based on the Cocoon XML/Java framework so it pays to think more in terms of XML and schemas when you come to use it in anger. You don't entend a Page Type as you might a Java class; you configure it using types.xml and the 6 dimension meta-date (e.g. Page Schema, Layout, I18n, business-logic, css, etc). There are a wide range of 'built-in' widgets available to gather the data for your publishable XML file. There are some examples of how to bind these through your layout and rules to the instance of the XML schema . It pays to get your head around how CForms work! When you do you have a sohisticated and powerful environment that connects Content through workflow to a UI with all the extensibiliy of the Cocoon pattern.
So, there isn't a simple answer to your question but I hope you will have been convinced to dis a bit deeper into the documentation and experiment with defining your first Content type, Regards On 08/12/2007, Paolo Mottadelli <[EMAIL PROTECTED]> wrote: > > Hi All, > we have a 'page' template. > We want to extend it to create a 'x-page' one, that inherits all the > 'page' properties and adds some others. > let's say: > > 'page' has: > _ title > _ body > > 'x-page' has: > _ title > _ body > _ date > > We don't want to duplicate the code used to difine the 'page' > template; we want to extend it. > Is there any simple way to do that? > Thank you very much! > > Paolo > > -- > Paolo Mottadelli > http://www.paolomottadelli.com > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
