The role of events in Thorax

[Patrick Mulder]

Hi!

I am exploring the advanced use of Events with Backbone, and found https://github.com/ModelN/backbone.geppetto  - which tries to encapsulate commands for events. There is this basic demo: http://jsbin.com/uleXOjOx/15 - but the usage is a bit more in the context of MarionetteJS.

I also got one feedback to look closer at: https://github.com/marionettejs/backbone.marionette/blob/master/docs/marionette.application.module.md

Now, what's the approach to managing events with Thorax? Especially, for fetching new data on a new page and/or rendering subviews. (In the example above, one could decrease/increase the counters after filter selection for example)

Thanks!

Patrick

[Noel Kendall]

I like the pub/sub pattern. It's easy to extend when incorporating new function. It's clean. AFAIK the pubsub approaches out there for Backbone would still apply. I stumbled on Thorax after getting far enough into a development to realize that it would a heap of grunt work to continue building a large app without layout management. That, and wanting to subclass Backbone.View - which Thorax appears to take in stride. Interested to know what you find on the events topic. Joined the group to participate and learn more.

[Patrick Mulder]

Thanks Noel for the feedback!

The pub/sub is indeed the core of scalable applications.

Would be great to hear more of your experiences with learning Thorax / Handlebars application design.

Have fun!

Patrick

--
You received this message because you are subscribed to the Google Groups "Thoraxjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thoraxjs+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.