Yes, for the first version I will just simply allow to put JS as a string. I’d like to use ElixirScript, but as you know it is not possible yet.
grych
Creator of Drab
grych
Creator of Drab
grych
Creator of Drab
Ladies and Gentlemen,
I’ve just released v0.7.7. It is a very important release, may call it experimental, because I’ve completely changed the way how Drab.Live renders the poke updates.
All Drab.Live limits should not exist anymore.
I strongly encourage everyone to give it a try and give me a feedback in case of failure.
grych
Creator of Drab
Drab v0.8.0 has landed!
codename: rm priv/drab.live.cache
The artifact of the ancient era, DETS cache for metadata from compiled Drab.Live templates, finally reached the end. Since this release, Drab stores every template metadata in the separate module. The compilation time is a fraction of the previous now. Everyone is happy.
This is a significant change, so please upgrade and report any issues
Batou99
Hi:
I don’t know if this is the right place to ask a question but here I go.
I’m trying Drab and using it with Bootstrap eonasdan datetimepicker. That component fires a dp.change event instead of a pure change event when date is changed. I added on a .drab template
<%= text_input @f, :start_date, drab: "dp.change:start_date_changed", class: "form-control datepicker", "data-date-format": "YYYY-MM-DD" %>
And ofc added the appropriate function in the commander but the event is not being picked up. If I manually set an on(dp.change) binding in the console it picks the event ok.
Is there a limitation on custom events on Drab? I’ve been reading the js code and it seems that it should not be the case.
Any help would be appreciated!
Cheers
Lorenzo
grych
Creator of Drab
Hi @Batou,
congratulations, you’ve found a bug!
This is probably because now Drab defines client side events in a very, hmm, naive way. Actually it is:
function update_event_handler(node, event, func) {
// TODO: learn more about event listeners
// node.removeEventListener(event, func)
// node.addEventListener(event, func)
node["on" + event] = func;
}
As you can see in TODO, I am aware of how poor is this “solution”, it supposed to be a temporary for a proof of concept… But it was always something more important to fix/improve.
Maybe someone with the better knowledge of JS may help? One of the issues is that this function may be called multiple times during the life of the page (as someone update the part of the page from the server, for example), and we don’t want the elixir event handlers to be called multiple times.
It is a right place. And, if you be so kind and create an issue on a github, so it won’t be fogotten.
OvermindDL1
The proper way would be to use addEventListener/removeEventListener with a unique key for the function event, then using the key you can store a name in the data section on the element for later lookup (or stored somewhere else or whatever) so you can cancel it without getting many duplicates.
Things like someElement["on" + event] = blah; should never ever ever be done.
grych
Creator of Drab
Agreed. Unfortunately, in the complex project like Drab, I had to simplify some stuff to move forward. Otherwise I would never publish even the proof of concept 
In my defense, at least I realized that it is poor and TODO myself to learn more about it…
grych
Creator of Drab
Hi all,
this is a request for comment on the proposed, stable API for Drab. There will be an API changes, sorry for that, but this is a last moment, when we reach 1.0 all will be fixed forever.
I think the most painful change will be that one to Drab.Live.peek. It will not return a value, but standard {:ok, value} tuple. Of course there will be a corresponding peek!.