(⊃｡•́‿•̀｡)⊃━☆ﾟ.*･｡ﾟ The Backbone Framework: http://marionettejs.com
there’s a handful of things on v5 that are buggy in the alpha though.. not sure about where that’s going. But with Backbone gaining some momentum who knows?
renderView will throw without it
export function renderView(view) {
if (view._isRendered) {
return;
}
if (!view.supportsRenderLifecycle) {
view.triggerMethod('before:render', view);
}
view.render();
view._isRendered = true;
if (!view.supportsRenderLifecycle) {
view.triggerMethod('render', view);
}
}so, i believe, for every not mn5 view.
so, my custom view should have
triggerMethod() {} or supportsRenderLifecycle: true
so I think nooping the
triggerMethod or setting those two flags to true is effectively the same thing
well it’s definitely the same thing.. but I believe not actually triggering those events is ok.
....
if (!view.supportsRenderLifecycle && view.triggerMethod) {
view.triggerMethod('render', view);
}
well so I don’t remember when but we added a mixin for supporting backbone views https://github.com/marionettejs/backbone.marionette/blob/master/docs/events.class.md#supporting-backbone-views
but all it does is add a
triggerMethod function
i just not really understand why to trigger something on a view without
1) if my custom view has
2) if i do not know about mn render life cycle and internaly have
supportsRenderLifecycle while rendering.1) if my custom view has
render and there some code related to render event why i cant implement it in my render?2) if i do not know about mn render life cycle and internaly have
render hook for other purpose i definitely will get side effect after rendering my view in a mn region
Paul, what do you think about some marionetteConfig in Mn5?
what if there will be one:
export const marionetteConfig = {
DomApi: DefaultDomApi,
viewRenderer: DefaultViewRenderer,
.... // other configurations
}and in a view it could be:
- Dom: DomApi,
+ getDomApi() {
return marionetteConfig.DomApi
}
...and changing the domApi will be like
import { marionetteConfig } from 'backbone.marionette';
marionetteConfig.DomApi = MyDomApi;
And the issue is poorly written, but there’ll be a second option marionettejs/marionette#3
which is essentially making v5 like v4 or very close
Hey, very "general" question... I'm runnin Marionette 3.5 in a webpack build, using "import"
Now, should I
import Marionette from 'backbone.marionette';or
import Marionette from 'backbone.marionette/lib/backbone.marionette.esm';or
import {View} from "backbone.marionette";Or any other?
Any advantages of one or the other? Tree-Shaking maybe?
dom:refresh reflects when the contents of a view's el change in the DOM, and dom:remove reflects when the contents of a view’s el are about to change in the DOM.
These events are ideal to setup any external DOM listeners such as jQuery plugins that use DOM within the el of the view and not the view's el itself.
that’s assuming the jQuery plugin cares that the DOM is attached to the document, which many do.
ok, thx.
as i can see, destroy is a disposal pattern implementation.
under the hood there is only
there are definitely own events exists after destroy, also jquery and dom elements too, and options object
is it not worth to clean everything, i suppose ?
as i can see, destroy is a disposal pattern implementation.
under the hood there is only
.stopListening() in mn destroy cycle.there are definitely own events exists after destroy, also jquery and dom elements too, and options object
is it not worth to clean everything, i suppose ?
this.stopListening();
this.off();
for(let prop in this) {
delete this[prop]
}
@paulfalgout
i tried to say that
btw, not sure i am understand what the difference between _events and _listeners. I mean that i know what it means in terms of backbone
just cant get why stopListening but not off.
correct me if i am wrong - instance will be GC if there is no other reference to this instance, no mater how many other instances its pointing, right?
...
i think i got this while write this big message.
stopListenning exactly removes other instances links
this.listenTo(this is not equal this.on( :)) only that.btw, not sure i am understand what the difference between _events and _listeners. I mean that i know what it means in terms of backbone
just cant get why stopListening but not off.
correct me if i am wrong - instance will be GC if there is no other reference to this instance, no mater how many other instances its pointing, right?
...
i think i got this while write this big message.
stopListenning exactly removes other instances links
there’s no reason to ever do
this.listenTo(this as it is exactly like this.on except that it keeps a 2nd hash of objects it references.. which is particularly not useful when listening to self.