tbranyen/backbone.layoutmanager

A layout and template manager for Backbone.js applications.

Tim Branyen

@tbranyen

Sorry you happen to be one that most likely experiences that particular bug

foligny

@foligny

Thanks Tim, no worries.

Simen Bekkhus

@SimenB

Is there any particular reason why I can't define views as a function? This would match Backbone's functionality where most (all?) attributes can either be defined statically or as a function

I realise I can achieve what I want in beforeRender using setViews, but I like how declarative views are

Tim Branyen

@tbranyen

That feature could definitely be added @SimenB

Joshy Cyriac

@joshy

Hi Tim, it seems the domain layoutmanager.org has been expired

Tim Branyen

@tbranyen

Darn, I saw notices about it. Thanks for the heads up!

Tim Branyen

@tbranyen

@SimenB looks like we had some weirdness with QUnit and calling the async start() method inside of then. basically need to do then(function() { start(); }) instead of then(start)

Simen Bekkhus

@SimenB

Did tests break? or just weird behavior?

Tim Branyen

@tbranyen

Tests broke

My guess is that qunit had that 'breaking change' rolled up into a patch release which we picked up accidentally

good to have it fixed anyways

It was just test file changes, nothing in the source

t. m. k.

@teehemkay

Hi All.

I've noticed something strange: there are two versions of layoutmanager in the npm repository: layoutmanager and backbone.layoutmanager.

t. m. k.

@teehemkay

They both point to the same git repository but they have some subtle differences in that they require different versions on backbone.
layoutmanager requires backbone 1.2.1 but backbone.layoutmanager requires backbone 1.1.2. This is a bit confusing.
Looking on github I can't find the version of layoutmanager that was published in npm as layoutmanager.

There are some useful change in backbone 1.2.x to enable its use without jQuery which I'm interested in so I guess my question is what's the status on supporting backbone 1.2.x?

Thanks!

Tim Branyen

@tbranyen

@teehemkay heya, i think someone is trying to fully support it here: https://github.com/tbranyen/backbone.layoutmanager/issues/481#issuecomment-155997951

But keep in mind if you're only using layoutmanager on the client side, it already supports backbone 1.2.0

t. m. k.

@teehemkay

@tbranyen Thanks for the pointer!

Attila Egyed

@tsm91

hello, it might be a dumb question but is it possible to use layout manager without template rendering?

The server will render all views and will pass a html string over ajax that i will append to the dom.

Tim Branyen

@tbranyen

@tsm91 how are you rendering the backend?

@tsm91 layoutmanager has the ability to render in Node and maintain the render tree (much like react). would allow you to eliminate the initial render, and then take over on the client side. if you are using something like asp.net or php (non-node) stuff and just want to hook into the markup and progressively enhance it, i'm thinking a tree/component approach with redux might be a good bet

Attila Egyed

@tsm91

yes, the latter approach with php

hmm you are saying i should use redux and not backbone? i am not quite familiar with bb , neither redux. so i dont mind

Attila Egyed

@tsm91

but im not exactly sure how redux will help in this scenario. can you describe the stack that comes with your approach in a little more detail?

so yes, a php server will render the initial page (blade templating of laravel) and any additional template will probably be rendered on the server too and passed over xhr as a string

Eugene

@godknowsiamgood

Hello! how can I get access to parent view from child view?

Tim Branyen

@tbranyen

Can you pass a reference to the child from the parent?

childView.parentView = this;
this.setView(childView);

Eugene

@godknowsiamgood

sure, I wonder why there is no standard approach in a library

Tim Branyen

@tbranyen

Because developers are finding two way traversal isn't a good way to structure apps

Depending on knowing the parent in a reusable View isn't a good idea typically

Eugene

@godknowsiamgood

clear

And what is the best way to make child views be draggable (some sort of grid)? I tried set mousedown event on child view and then add mousemove on window where update absolute position of child view. Is this a right way to make it?

Tim Branyen

@tbranyen

Yeah, if you wanted to add it back in, you could do something like this:

LayoutManager.configure({
  parentView: function() { return this.__manager__.parent; }
})

That would add a parentView method that returns whatever layoutmanager thinks the parent view is

Hrm, there are native HTML5 drag/drop APIs now

Can you use those?

Instead of implementing it from scratch

Eugene

@godknowsiamgood

I need some very interactive drag-n-drop with animations, grid restructure in dynamic etc... I will look in to it

Tim Branyen

@tbranyen

Ah okay

huang.xinghui

@huang-x-h

Hello everyone, dose someone have problem by using views property?

View this issues #495

Tim Branyen

@tbranyen

@huang-x-h It's probably best to avoid that property

Use setViews instead

You can use it, and it'll work for simple cases, but since it's defined on the prototype it'll have limitations

I can leave you a better comment in the issue in a bit, I don't use layoutmanager anymore, but I don't want to leave you hanging

huang.xinghui

@huang-x-h

Thanks for your answer. Does something can replace layoutmanager? Marionettejs? It's too complex.

huang.xinghui

@huang-x-h

And does layoutmanager will not maintain in feature?

Tim Branyen

@tbranyen

@huang-x-h hard to say

Where communities thrive

People

Repo info

Activity