Sounds like a plan to me if the organizers want to run with a backbone.js night.
I don't have much of a summary as I was expecting to have some time to come up with what I would talk about, but I was also thinking really basic. Such as:
- Deciding when to make a separate view.
- Making re-usable views.
- Moving view logic from child views to parent views with event delegation.
- (aside) Show how awesome $.Deferred is.
- Basic, basics like why you'll probably only need one router.
- Admit my undying love for underscore.js
Let's see what the group organizers decide then organize off the list if they want to go with it.
On Wed, Feb 6, 2013 at 3:00 PM, Adam Terlson <[address removed]>
This is funny, I was just about to suggest doing a talk as well about BackboneJS, providing a moderately-opinionated approach to how things can/should be structured, how to unit test it, etc and was going to solicit the group for someone to pair with on it.
Give structure where none exists
- Establish conventions and "best practices" to aid in unit-testability and maximum separation of concerns
- Avoid touching the DOM manually via jQuery and doing things the "backbone way" instead
- Show a unit test that achieves near 100% coverage of a view, leverages mocks and doesn't ever touch the DOM or call the server.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
To learn more about Adam Terlson, visit his/her member profile