Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4733427B.7010003@apache.org>
Date: Thu, 08 Nov 2007 18:08:11 +0100
From: Felix Knecht <felixk@apache.org>
Organization: apache.org
User-Agent: Thunderbird 2.0.0.6 (X11/20070802)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: AW: own widget
References: <4730131E.6080507@uib.es> <4732E065.9090104@weitling.net>
 <001601c8220d$aa472e50$306fa8c0@philosophy.pchl.co.uk>
 <8A9A3F0EF79C4FB2B7EF3D6460DF7908@corix.local>
 <E95D49245C437849A8DADBBDA9288817544C@herakles.corix.local>
 <9CC0ABC6641F48FABF150615D34F122D@corix.local>
 <E95D49245C437849A8DADBBDA9288817544D@herakles.corix.local>
 <4733278B.2070201@apache.org>
In-Reply-To: <4733278B.2070201@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

@Grzegorz
I thought Giacomo migrated the forms block to spring (cocoon-forms-1.1.0).Wouldn't it make more sense to use already the
new forms block instead of the legacy one (probably it makes configuration also easier)?

Felix

> Michel Erard pisze:
>> Hi Grzegorz, 
>>  
>> yes, I think for this example your right, perhabs it's enough when I add a new xslt. But when this is not enough, how I add a widget?
> 
> Let's assume you want to create widget named MyOwnWidget, then you will need to:
> 1. Implement MyOwnWidget class extending o.a.c.forms.formmodel.AbstractWidgetAbstractWidget
> 2. Implement complementary classes to the first one responsible for handling definition of widget:
> MyOwnWidgetDefinition (extending AbstractWidgetDefinition or similar) and
> MyOwnWidgetDefinitionBuilder (extending AbstractWidgetDefinitionBuilder).
> 3. Register your own widget (see [1]).
> 4. Write your own JX macros for your widget similar to standard macros (see [2]).
> 5. Write your own XSLT file for styling your own widget.
> 6. Integrate everything together. (consists of adding few imports so your macros and xsls are visible).
> 
> May seem like a lot of work but in a fact most of this steps are really simple. For example, for the
> most of widgets classes implementing them are really straightforward as they inherit everything from
> abstract classes.
> 
> Before you start to implement anything new I think it would be a good idea to evaluate all existing
> widgets and their varations (different styling) so you are not going to waste your time if simpler
> solution exists.
> 
> I hope that helps a little.
> 
> [1]
> http://svn.apache.org/repos/asf/cocoon/branches/cocoon-forms-1.0.0/cocoon-forms-impl/src/main/resources/META-INF/cocoon/avalon/cocoon-forms.xconf
> [2]
> http://svn.apache.org/repos/asf/cocoon/branches/cocoon-forms-1.0.0/cocoon-forms-impl/src/main/resources/org/apache/cocoon/forms/generation/jx-macros.xml
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org