On Tue, Mar 3, 2009 at 17:35, Diodeus <diod...@gmail.com> wrote:

>
> Is there any plan to remedy this situation?


If you look at the development on master since 1.6.0.3, you can see that
some significant effort has been put into re-organizing Prototype modules
and better usage of the module pattern in JavaScript.

However, main modules like Hash, Template, Enumerable, etc. are going to
stay in the global namespace until some major release where the core team
decides to pull them under the Prototype namespace. It is not certain when
will that happen, but a year ago (or more) I showed how it's fairly easy to
namespace Prototype yourself with few minor changes to the library. Any
project like Bespin can use this approach if it wants to bundle Prototype
and nobody has to wait for the prototype core team to do it.

However, the core team definitely decided (or so they sounded) to stop
extending DOM elements in the future major release. It is just too slow in
IE and has bitten back on several occasions in other browsers that
implemented some of the methods natively (if I recall correctly).

It is not clear will Prototype ever stop extending native prototypes like
Function, Array, Number, Event, etc. I vote no, because if Prototype ever
stops extending DOM nodes, extending native prototypes, and touching the
rest of the runtime environment all-together, it will cease to be the
"Prototype" library.

--~--~---------~--~----~------------~-------~--~----~
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 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to