You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Sylvain Wallez <sy...@apache.org> on 2005/02/11 22:44:40 UTC

[vote] Removing ScriptableWidget in CForms

Hi all,

When removing all restrictions on the FOM (cocoon.request, 
cocoon.session, etc) compared to it's Java equivalent, we also decided 
to simply use a standard Rhino wrappper around the regular Java objects, 
and abandon the specific wrappers that provide more confusion than real 
added value.

Such specific JS wrappers also exist in CForms through the "form.model" 
construct which uses ScriptableWidget. Regular Rhino wrappers are also 
available using form.lookupWidget().

So I'd like to remove "form.model" so that we only have the regular 
wrappers, in the same way that we decided for the FOM: issue a 
deprecation warning 2.1.7 and remove in 2.2.

Please cast your votes.

Here's my +1.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }


Re: [vote] Removing ScriptableWidget in CForms

Posted by Carsten Ziegeler <cz...@apache.org>.
Sylvain Wallez wrote:
> 
> So I'd like to remove "form.model" so that we only have the regular 
> wrappers, in the same way that we decided for the FOM: issue a 
> deprecation warning 2.1.7 and remove in 2.2.
> 
> Please cast your votes.
> 
+1

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Re: [vote] Removing ScriptableWidget in CForms

Posted by Antonio Gallardo <ag...@agssa.net>.
On Vie, 11 de Febrero de 2005, 15:44, Sylvain Wallez dijo:
> Hi all,
>
> When removing all restrictions on the FOM (cocoon.request,
> cocoon.session, etc) compared to it's Java equivalent, we also decided
> to simply use a standard Rhino wrappper around the regular Java objects,
> and abandon the specific wrappers that provide more confusion than real
> added value.
>
> Such specific JS wrappers also exist in CForms through the "form.model"
> construct which uses ScriptableWidget. Regular Rhino wrappers are also
> available using form.lookupWidget().
>
> So I'd like to remove "form.model" so that we only have the regular
> wrappers, in the same way that we decided for the FOM: issue a
> deprecation warning 2.1.7 and remove in 2.2.
>
> Please cast your votes.
>
> Here's my +1.

+1

Best Regards,

Antonio Gallardo


Re: [vote] Removing ScriptableWidget in CForms

Posted by Leszek Gawron <lg...@apache.org>.
Sylvain Wallez wrote:
> Hi all,
> 
> When removing all restrictions on the FOM (cocoon.request, 
> cocoon.session, etc) compared to it's Java equivalent, we also decided 
> to simply use a standard Rhino wrappper around the regular Java objects, 
> and abandon the specific wrappers that provide more confusion than real 
> added value.
> 
> Such specific JS wrappers also exist in CForms through the "form.model" 
> construct which uses ScriptableWidget. Regular Rhino wrappers are also 
> available using form.lookupWidget().
> 
> So I'd like to remove "form.model" so that we only have the regular 
> wrappers, in the same way that we decided for the FOM: issue a 
> deprecation warning 2.1.7 and remove in 2.2.
> 
> Please cast your votes.
> 
> Here's my +1.
+1. form.model was not exposed in javascript event handlers and this 
usually led to confusion.

-- 
Leszek Gawron                                                 MobileBox
lgawron@apache.org                              http://www.mobilebox.pl