(⊃｡•́‿•̀｡)⊃━☆ﾟ.*･｡ﾟ The Backbone Framework: http://marionettejs.com
because of popperjs specifics
not trying :) i did it
i can show with screen, its hard to explain
and the well formed view is not all
there can be active interface elements ready for user interaction, so, go through just template strings is not the case
there can be active interface elements ready for user interaction, so, go through just template strings is not the case
my initial thought would be to make some sort of Mn Behavior that 1.) creates a popover with an empty Region in it, and 2.) emits some lifecycle and status events for popover. Then you could hook into these events to show complex child views. Something like:
class Promotion extends Marionette.View
template: _.template '''
<%- name %>
<%- price %>
<button data-popover>
Details
</button>
<button class="js-buy-item">Buy</button>
'''
behaviors: [ Popover ]
onPopoverInitialize: (popover) ->
popover.region.show new DetailsView(model: @model)
this solution is not acceptable in some cases and is not as universal as it can be.
behavior or mixin - this is does not matter.
the important thing how to render content view.
i prefer to take out region from behavior/mixin just to be able create a standalone versions of any tooltip/popover.
in case of just modal view its pretty trivial.
the main goal of using popperjs for popover or tooltips is ability to put content element in a correct place and visually stick with the reference
the variants of possible layouts is very big and it seems that popperjs has solved all possible variants and works well
the mechanic of popperjs is that you have to provide some content dom element which must be present in the dom
and this is thing i've woried about: i can render content view at least by two different ways: just call
currently i am stick with simple
and this is seems to me wrong
i believe its better to render and attach standalone view in some region.
and now we are comming close to question i really want to ask
if i create a region in the dom and render in it a popoverview and popperjs will detach view.el and reattach it to correct place, is it safe enough to use regions?
behavior or mixin - this is does not matter.
the important thing how to render content view.
i prefer to take out region from behavior/mixin just to be able create a standalone versions of any tooltip/popover.
in case of just modal view its pretty trivial.
the main goal of using popperjs for popover or tooltips is ability to put content element in a correct place and visually stick with the reference
the variants of possible layouts is very big and it seems that popperjs has solved all possible variants and works well
the mechanic of popperjs is that you have to provide some content dom element which must be present in the dom
and this is thing i've woried about: i can render content view at least by two different ways: just call
render or use stand alone region with showcurrently i am stick with simple
view.$el.appendTo(document.body)';view.render;and this is seems to me wrong
i believe its better to render and attach standalone view in some region.
and now we are comming close to question i really want to ask
if i create a region in the dom and render in it a popoverview and popperjs will detach view.el and reattach it to correct place, is it safe enough to use regions?
typically it'll render everything before both attach events, but that's not guaranteed
For one, there's no reason you couldn't do this:
onBeforeAttach() {
this.render();
}No doubt you'd shouldn't do that, but it certainly can occur.
without any black magic from the dev side
so, the first one - attach events after all render events. ok
ah, collectionView's childView has same logic? render events then attach events ?
why this is work
childViewTriggers: {
'control:change':'control:change'
},
onControlChange() {
console.log('ok!');
},and this is not work?
childViewEvents: {
'control:change'() {
console.log('ok');
}
},i believe i did something interesting but in general i think that both should work, but its not :-/
It does work. If it's not working it isn't the
childViewEvents that isn't working. https://jsfiddle.net/c621xa8g/
i.e., the use of
() instead of : after control:change?
as Paul said and i was pretty sure before both things should work.
but in my case
but in my case
childViewEvents didnt. now i have to find out what exactly i did which broke this behavior
now, i am thinking how to do this in more gentle way.
i still need pass some childViewEvents but without wiping prototype one.
i still need pass some childViewEvents but without wiping prototype one.
i have some universal trigger which invokes triggerMethod or trigger on given context.
and occasionally it throws an error some where in the deep of backbone
and occasionally it throws an error some where in the deep of backbone
Uncaught (in promise) TypeError: callback.apply is not a function
it happens on some internal backbone eventsapi method
// Reduces the event callbacks into a map of `{event: onceWrapper}`.
// `offer` unbinds the `onceWrapper` after it has been called.
var onceMap = function(map, name, callback, offer)i believe the error happens of course because of me, something wrong with context events hash and i will find the error, somewhen.
but thing i realy dont understand is in this piece of code which exactly throws an error
its a part of my trigger function
.....
if (context.triggerMethod) {
try {
return context.triggerMethod(event, ...args);
} catch (e) {
return context.triggerMethod(event, ...args);
}
} else {
return context.trigger(event, ...args)
}as you can see, there is a some kind of dark magic with try catch block.
the context.triggerMethod(event, ...args); in try block effectively throws an exception mentioned above.
i expect that i will see the error anyway because i do same call in catch block and second exception should happens, but its not.
on the second call everything is fine.
just... wtf?
i was thought that i can do this
this.once('resolved','destroy'), don't know why i decided that backbone event allow string literals for callbacks
I'm not aware. I believe the most updated definition is via https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/backbone.marionette/index.d.ts and it's on 3.3.
I'm having some problems with setting up a marionette object with channelName and radioRequests but later when I do channel.request('foo') there seem to be no one listening. I'm having a feeling it has something to do with different Backbone.Radio instances between what is setup by Marionette and what I get when I do const Radio = require('backbone.radio') but not sure. Any tips? :)