At the risk of being a jerk, here is my hard-won opinion about
client-side frameworks: Just. Don't.
After using them on a dozen projects (including PANDA) I can
confidently say that unless you're building a TODO list, they will
almost certainly cause more harm than good. Here are some things I've
learned that I've found can take the place of various parts of a
framework without all the things that suck about them:
Ideas:
* class encapsulation and inheritance - Javascript: The Good Parts by
Crockford is the place to start
* the module pattern - google it, wrap your head around the
variations, its a double win because other libs will make more sense
and you can apply it yourself
* other design patterns - esp. Singleton, PubSub, and Facade. For
larger projects Mixin and Controller too.
* code conventions - Crockford's or somebody else's (here is my
team's:
https://github.com/nprapps/bestpractices/blob/master/javascript.md)
* code organization - IMHO, the single most valuable thing frameworks
give you is a motivation to put JS in multiple files, but you can also
just do that
* jquery's "on" - click is dead to me.
* client-side templating - see below
Libraries:
* jquery.js - always more
* underscore.js - functional programming and templating
* hasher.js - routing
* signals.js - custom event binding
* moment.js - dates the right way
All of these are lightweight libraries that will give you tools, but
won't force pain-in-the-ass patterns on you.
One man's two cents,
C
> --
> You received this message because you are subscribed to the Google Groups
> "Hack Tyler" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
hacktyler+...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.