LosTechies - Latest Comments

Re: References, Routing, And The Event Aggregator: Coordinating Views In Backbone.js

Dgabriel — Wed, 16 May 2012 10:02:26 -0000

I just started working on my first very complex backbone app, and you have saved me a lot of pain, agony, and irritation here. Thank you.

Re: Zombies! RUN! (Managing Page Transitions In Backbone Apps)

Ansjob — Tue, 15 May 2012 13:52:48 -0000

Really neat solution to this problem. Love it!

Re: Workflow In Backbone Apps: Triggering View Events From DOM Events

dagda1 — Tue, 15 May 2012 09:47:29 -0000

I've used Backbone and Ember in roughly equal amounts and the Ember bindings model is a much leaner, looser coupled and all round better way of dealing with things.

I can have several parts of my app updating from one change using bindings. For example:

http://bit.ly/KYFmW5

In the above example I have a queryBinding where I specify the path to the bound object. Once that object changes, I perform a transform and the change gets published to any subscribers like the queryDidChange handler in the above gist. The from path specifies the path to the object that it is bound to. I can have several other observers throughout my app and observers on these observers etc. and this is all synchronised beautifully without me having to write any additional code.

BTW, I use Backbone.Marionette on any legacy backbone apps and it has been a real time saver. It really does take the pain out of backbone.

Re: Git: Oops. I Forgot To Add Those New Files Before Committing

Guest — Mon, 14 May 2012 02:33:05 -0000

Nice.

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

dagda1 — Mon, 14 May 2012 00:58:58 -0000

I think Ember like bindings is one of the main things missing from backbone. These keep the code loosely coupled and lean. You do have the events object in Backbone but you have to write all the code to create and trigger the event. The bindings model in Ember is very rich.

Re: Zombies! RUN! (Managing Page Transitions In Backbone Apps)

Cristhian Valencia — Fri, 11 May 2012 18:54:45 -0000

Excelente articulo muchas gracias.
Yo intente realizarlo de una forma alternativa y obtuve lo siguiente:

http://stackoverflow.com/a/105...

Re: Don’t Execute A Backbone.js Route Handler From Your Code

chandra — Fri, 11 May 2012 05:59:43 -0000

This is good, but what about when you have to wait for an asynchronous response when the user submits a form to change view, the router needs to wait for the async success callback to fire before routing to the new view. I read your articles, and I see they are very helpful. Thanks!

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

Dustin Boston — Thu, 10 May 2012 17:54:24 -0000

Yay controllers in Backbone! Love it!

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

kamranayub — Thu, 10 May 2012 17:20:27 -0000

I think Node.js helps with this pattern a bit; I dislike seeing all the nested stuff so I end up separating things into smaller chunks, which makes the "big" methods much smaller and easy to read.

For example, I was doing a screen scraping proof of concept and what I *could* have done was do a deeply nested monster that went through about 4 HTTP requests and processed the results, but I didn't, I created separate handlers for each step of the process and just separated them out so I could reduce redundant code and add error handling in the process. It was a simple proof but just by doing it in Node forced me to restructure how I did it.

Re: Composite Views: Tree Structures, Tables, And More

Joshua Anderson — Thu, 10 May 2012 16:08:08 -0000

Well thought out; backbone.js doesn't consider relationships inside items. This is great, that you have thought this thoroughly. Thank you Derek for your time.

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

Derick Bailey — Thu, 10 May 2012 13:58:02 -0000

I really need to read Clean Code. I think I have it on my Kindle, but have never got around to it. :P

And yeah, the asynchronous bit with the callbacks kind of drives me nuts some times. There's a handful of things that can be done to reduce the nesting of callbacks, but sometimes that ends up reducing the readability and understandability of the code, for the sake of keeping it "clean". It's hard to find those balances.

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

Tyronemichael — Thu, 10 May 2012 13:38:56 -0000

I needed this. I am constantly looking for patterns with regards to large scale applications and backbone.js. The premise of the simplicity and organization backbone provides is easily said than done. I definitely need to find a pattern that seprates logic into more readable and maintainable codebase. This definitely provides an idea so thank you!

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

Peter Rust — Thu, 10 May 2012 13:21:31 -0000

Great article as always, Derick!

It's very similar in concept to "The Stepdown Rule", from a book I highly recommend: Clean Code by Robert C. Martin (the chapter on Functions, section on "One Level of Abstraction per Function, Reading Code from Top to Bottom")

Except, of course, for the asynchronous part.

Just playing around a little, one could imagine it written using node.js conventions (a callback as the final argument that takes an err object for error handling). The pseudo-return-value(s) of a closeable form/dialog would be provided to the callback (after the err object):

getEmployeeDetail(function(err, employee) {
selectManager(employee, function(err) {
employee.save();
});
});

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

Wwwboy — Thu, 10 May 2012 13:19:50 -0000

Nice work!
Such articles help me and others to get new way of thinking and developing programms!Thanks alot!

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

Derick Bailey — Thu, 10 May 2012 10:35:18 -0000

yeah, i've seen that a few times. i'm not a fan of configurable state machines like that. something about that pattern and style has always bothered me, and I invariably end up fighting the state machine framework instead of having it facilitate my workflow in a more controlled manner.

Re: Modeling Explicit Workflow With Code, In JavaScript And Backbone Apps

David Madden — Thu, 10 May 2012 10:07:41 -0000

Interesting article.

Have you come across this post: http://freshbrewedcode.com/jim...

Looks like there is a bit of crossover in what you are trying to achieve.

Re: Wrapping $.ajax In A Thin “Command” Framework For Backbone Apps

Romain Tribes — Wed, 09 May 2012 17:02:19 -0000

Damned, it's great! Thanks for that.

Re: Zombies! RUN! (Managing Page Transitions In Backbone Apps)

Amit Garg — Wed, 09 May 2012 08:28:15 -0000

Everytime I search for Backbone .. I land on your page.. then the search ends.. Thank you very much .. Keep posting..

Re: Backbone.js And JavaScript Garbage Collection

Jason — Tue, 08 May 2012 17:33:08 -0000

If this were expanded, do you think it could be of use?
https://github.com/jstrimpel/e...

Re: Stop Using Backbone As If It Were A Stateless Web Server

Libor Nenadál — Tue, 08 May 2012 11:35:06 -0000

Well quite a lot of words for one simple thing - use route for routing to items (views), not for actions. ;-)

Re: Don’t Do Role-Based Authorization Checks; Do Activity-Based Checks

Warren Sentient — Mon, 07 May 2012 08:58:52 -0000

Thank you for the excellent article.

Re: Wrapping $.ajax In A Thin “Command” Framework For Backbone Apps

Derick Bailey — Sun, 06 May 2012 15:31:21 -0000

yeah, someone else pointed that out to me on twitter as well. it looks exactly what i've done, only with far more features and stability :) definitely something i want to look in to when i have time.

Re: Wrapping $.ajax In A Thin “Command” Framework For Backbone Apps

Stof — Sun, 06 May 2012 15:27:13 -0000

This is an interesting read. I also found http://amplifyjs.com/api/reque... which seems to address a similar use case (and more feature AFAICS). What do you think about it ?

Re: Wrapping $.ajax In A Thin “Command” Framework For Backbone Apps

Dominik — Fri, 04 May 2012 12:53:18 -0000

Very neat and clean solution. Thank you for sharing.

Re: Binding A Backbone View To A Model, To Enable and Disable A Button

Neha — Fri, 04 May 2012 02:14:59 -0000

Thanks.. useful tutorial.