I agree with Jared. If the audience is mostly skilled with HTML and CSS, they are likely to be missing some programming concepts even more fundamental than OOP, like the idea that you can take a piece of code and put it in a function so you can call it in several different places. Remember that HTML and CSS don't even have such a concept: All you can do is copy and paste.
So you may need to introduce them to the basic idea of a *function* before - or while - you introduce them to OOP. Really if you can even just do that you will have done a world of good. I see so much front-end code where someone has a magic 10-line block of jQuery code, and when they want to use it for another DOM element they copy and paste the block and change the selector. Because in HTML or CSS that is how you would *have* to do it. I would stay away from any comparison of different kinds of techniques such as new vs. object literals, prototypes vs. class-based inheritance, etc. Pick one approach and present it well - that's all you will have time for, and barely that. -Mike -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
