cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeroen Reijn <>
Subject Re: RFC: Changes to CForms in 2.1.11-dev
Date Thu, 28 Dec 2006 09:26:02 GMT

Jeremy Quinn wrote:
> Hi All
> I hope you all had a good Christmas.
> Santa's little helpers have been busy working on CForms over the holiday 
> break :)
> Below is a list of changes I have in my local repo, ready to commit. I 
> would like to get feedback on these changes, in case of dissent, or 
> usecases I have not fully understood.
> 1. Updated to use Dojo 0.4.1 -- brings lots of improvements, bug fixes 
> and broader browser support.

> 2. Introduction of widget namespaces, allows lazy loading of widgets via 
> lookup from a manifest.

Sounds interesting.

> 3. Dojo debugging is now turned on and off via an optional sitemap 
> parameter.

> 4. The contents of the optional <fi:init/> tag is now inserted after the 
> scripts to load dojo etc.
> 5. TODO: cocoon.forms.* to take over from forms_* in forms_lib.js.

This sounds like a good idea to me.

> Notes:
> The upgrade to Dojo 0.4.1 brings us many advantages, but may break some 
> user's custom widgets due to changes in some of the APIs. The work 
> required to adapt the existing forms and ajax widgets was pretty minor.
> The widgets that come with 0.4.1 are much improved. This will make it 
> far easier to replace the legacy javascripts like htmlarea and the 
> mattkruse-libs with their dojo equivalents, while supporting a wider 
> range of browsers.

Hmm I'm still not sure if the Dojo rich text editor is capable of all 
HTMLArea functionalities. Do your changes allow me to still configure my 
own rich text editor for certain elements in my cforms page?

> The main rationale for these changes has been to reduce the amount of 
> javascript that gets loaded by a CForms page. Currently everything 
> possible gets loaded, regardless of whether it gets used or not.

I'm all +1 on that.


View raw message