I agree with Jerod about the binding part. Here's the modified list
that I would suggest (probably that was my own learning curve) :

1. Master the $ function
2. Use instance methods to perform common tasks on elements
3. Master event observing
4. Use Enumerable to manage collections
5. Master binding and understand closures
6. Push the envelope with Ajax
7. Treat functions like first-class objects
8. Master the $$ function with event delegation
9. Write class-based JavaScript
10. Managing custom events

The first 4 items would suggest that one has to get familiar with the
"wrapping" property of Prototype over the usual Javascript programming
for cross-platform scripting, and error-less coding. Everything to
acquire good programming habits and use the library methods propertyl.

The next 2 items jumps in the "fun" part (the why people want to learn
Prototype in the first place).

The last 4 items goes more in depth in making the scripts more
maintainable, object-oriented, and structured. One could argue that
making the script more OO and structured should be in the top
priority, but I think that even though I agree, up to these points,
Prototype may well be used on casual personal sites and hobby coding,
and these do not necessarily "need" that kind of structure in their

Of course, this list could be argued for a long time, but I think that
the general idea is the same.


On Nov 18, 11:05 pm, "Jerod Venema" <[EMAIL PROTECTED]> wrote:
> I like TJs list. However, I'd move "binding" up in priority.
> Despite it being a more "advanced" use of javascript, it's vital to
> understanding the items listed as 3 and 4 (events and AJAX [callbacks]).
> -Jerod Venema
> On Tue, Nov 18, 2008 at 8:57 PM, Andrew Dupont <[EMAIL PROTECTED]>wrote:
> > On Nov 18, 4:11 am, "T.J. Crowder" <[EMAIL PROTECTED]> wrote:
> > > That list falls neatly into two categories:  Basic techniques not
> > > requiring *too* much in terms of conceptual understanding (the first
> > > five items), then more conceptual (and powerful) stuff (the last five
> > > items).  I probably would have put Enumerable lower down except that
> > > it goes well with the "basic techniques" group.
> > Yeah, that's the hard part. I think $$ and Enumerable go together
> > because so many novice use cases for Enumerable will involve filtering
> > DOM result sets. So I'd be inclined to move $$ to #5.
> > > Nit-picking, "Treat functions like first-class objects" sounds as
> > > though they aren't, but we're treating them like they are.  I'd say
> > > the focus should be on the student learning that in JavaScript,
> > > functions *are* first-class objects.  It's one of the most powerful
> > > concepts in the language.
> > The phrasing assumes that the user probably hasn't come from a
> > language where functions _are_ first-class objects; that's all that
> > was intended.
> > Thanks for your feedback, everyone.
> > Cheers,
> > Andrew
> --
> Jerod Venema
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