hi Ricardo, it's actually 120 hours per year, and it's the last two years. so 240 hours.
On Fri, Jan 9, 2009 at 4:44 AM, Ricardo Tomasi <[email protected]> wrote: > > Yes but what happens when you find an error in your script? It might > be a very basic mistake but you won't have a clue if you don't know > javascript itself. What happens 5 years from know if a totally > different library, with different syntax, takes over? > > I agree with Peter Higgins, it's much more useful to teach the basics > first, then introduce jQuery, if they got the very basics then they > can learn the rest on their own. It's like teaching someone to use the > Blueprint CSS framework and not explaining what classes really are. > They`ll find themselves lost at the first adversity. > > - ricardo > > Do you mean 2 hours a week for 3 years? That's enough to learn well 5 > different languages :D > > On Jan 8, 8:30 pm, Kean <[email protected]> wrote: >> Your audience are designers, they will pick up jQuery faster because >> they think in CSS. >> >> At what point do you teach them javascript? >> When you teach them how to create plugins for jQuery. >> >> I hope this helps. >> >> On Jan 8, 2:13 pm, Nikola <[email protected]> wrote: >> >> > Why not integrate the basic "JavaScript Fundamentals" in each jQuery >> > lesson. You could show some general examples and explain the >> > rudimentary JavaScript principal (I'm thinking a 15 minute >> > introduction...) then teach the jQuery and demonstrate how and why >> > jQuery is the "write less, do more" JavaScript library.. This way, >> > students get the gist of the JavaScript while learning jQuery. This >> > may not be as desirable as learning jQuery on top of a strong >> > JavaScript foundation but it can certainly help them to become >> > stronger jQuery developers while giving them an introductory >> > foundation in JavaScript principals.
