Primarily I have added: removeChildren, insertAfter, insertAtIndex, prependChild, getParentsByTagName, getParentByTagName, getChildrenByTagName, getChildByTagName, getNextSibling, getPreviousSibling, setClassName, getStyles. The getNextSibling and getPreviousSibling can take a tagName. I've also tweaked: remove so that it will automatically remove observers, setStyle and getStyle to be more robust and classNames to cache the classNames object per an element. I've also tweaked the event system pretty heavily but it is way overkill and I'm looking into something different.

It isn't totally ready for the scrutiny of the public but I don't mind sharing ... it is all MIT'd. You will find lots more than just what I've mentioned here.

http://trac.brandonaaron.net/trac/browser/

I honestly had no idea I would be talking about prototype on the jQuery mailing list. Heh, I haven't even posted that link on the prototype list yet.


Back to jQuery ... how many equivalents does jQuery have to prototype?

I'm really digging the formal way of doing plugins. Sure we can all extend our favorite libraries but it is nice having something uniform and easy to implement for others. Can/Will plugins easily benefit from the build system that jQuery currently has, including documentation?

Brandon



On 8/31/06, John Beppu <[EMAIL PROTECTED]> wrote:
This may be slightly off-topic, but I'm curious about the changes you made to prototype.  What aspect of its DOM manipulation did you find lacking?

On 8/31/06, Brandon Aaron <[EMAIL PROTECTED]> wrote:
I'm a long time prototype user and have had a love/hate relationship with it. I've spent a lot of time tweaking prototype to suit my needs in the DOM manipulation area.


_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/



_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to