Hi Mislav

Thanks for taking the time to provide a reply.

The new Element constructor will definitely be useful, and cleanly gets
around the createElement issue without altering the dom.
I didn't realise that prototype had a no dom method meddling policy, at
least not until I read #7744 and then it was too late :)
I guess its similar to the Builder class, looking at your example, in


On 5/1/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> On 5/1/07, Gareth Evans <[EMAIL PROTECTED]> wrote:
> >
> > Apologies, I actually searched and found #7744
> > http://dev.rubyonrails.org/ticket/7744
> >
> > Gareth
> >
> Gareth,
> The intention is good, but the idea - not so much. While Prototype does
> tons of great stuff to built-in prototypes, adds methods and fixes bugs,
> until now we never messed around with original DOM methods.
> What we will do (and already have - check the dom branch in SVN) is turn
> Element into a constructor, so you will be able to:
>   var ele = new Element('div', { attr: value, ... })
> This will be available in 1.5.2. You can of course steal it from the
> branch and use earlier than that.
> >

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to