what should i do if i want to show a confirmation alert before drab-click runs?
for example>
Reset← Click!- Are you sure? [cancel/ok ← Click!]
- run drab function
robobakery
grych
Creator of Drab
There are two easy ways:
- Using
Drab.Waiter- this is a module to allow you to wait synchronously for the user input. See example: Drab: Server Side User Interface Access - Using
Drab.Modal.alert/4, which shows you a nice bootstrap modal. But this requires jQuery (as bootstrap does). Here is a good example - it shows modal to ask if the processing should go on.
robobakery
thanks, I like the way Drab.Waiter treats user input. it is so simple.
but on it’s documentation, i couldn’t find a clue how to use it with window.confirm()
waiter(socket) do
on "selector1", "event_name", fn (sender) ->
end
...
end
what am i missing?
grych
Creator of Drab
Well, if you want to use confirm() there is no need to use waiter! confirm() is already waiting for the user input:
{:ok, confirmed?) = exec_js socket, "window.confirm('Sure?')"
Just remember about the timeout. The default is 5 seconds, and after this you will get {:timeout, "timed out after 5000 ms."}.
{:ok, confirmed?) = exec_js socket, "window.confirm('Sure?')", timeout: :infinity
robobakery
Vance
So a quick question, I guess. Drab looks great. But how, exactly, do you use Drab in the sense of integrating with the rest of your app?
So say I have a a task on my dashboard, and I use a dropdown menu to assign it to an employee. That fires off a Drab handler, and then what? In my Commander do I import all my Contexts and call the update functions on that, or does all of that live in my Controller, or what?
Also, when you render a partial, does it call the corresponding Phoenix Controller for that template and all the plugs, etc that live in that Controller?
I like the idea of a bunch of shared controllers so I can have my “master” controller that mostly just lays out the page and calls a bunch of rendered partial templates, and Drab can update those things. But how does this work in practice with actually updating my database and responding to updates made elsewhere in the app?
I want to, for example, have a “edit” or “new” form for part of my page, and post the data to the server without reloading the entire page, yet other parts of the page get updated from that post, or other viewers of the page. What’s the basic workflow for that kind of thing? Are the Commanders essentially replacements for the Controller at that point?
Thanks, Drab looks awesome!
grych
Creator of Drab
Short answer is: Yes. And no 
Controller is a module containing functions, which are triggered by the outside world - http requests, like GET or POST.
Commander is a module containing functions, which are triggered by the outside world - JS events, like “onclick” or “onsubmit”. So I would rather say that the commander is a replacement for a JavaScript controller of some framework. The only difference is that the event handlers run on the server-side
Controller uses routings to find out which function it should run, based on the http request (“/post/1” launches MyApp.MyController.show etc).
Commander does not use any routings. It knows which commander to use, because it knows which controller was used to render the page. So this event on <button drab-click='show_user'>
would run MyApp.MyCommander.show_user. Or you can use drab-click='MyApp.,OtherCommander.show_user' to route it directly.
At the beginning of the project I was thinking about putting the event handlers in the controllers, but I think creating another entity just for the event handlers was a good idea. You still have a MVC application, but “C” is for commander
Yes.
If you want to update the part of the page with some partial, you use Phoenix.View.render_to_string/3 to get a html, and push it to the page.
poke socket, live_partial1: render_to_string("partial1.html", color: "#aaaabb")
The above uses render_to_string/2 helper, more info here.
It all depends on you. If you want to create 100% drabbed application, you may only render the page with the controller, and then do all the edits with the commander.
grych
Creator of Drab
Now it is possible, you may pass options to Phoenix.Channel. To turn off the logs:
config :drab, :phoenix_channel_options, [log_handle_in: false]
grych
Creator of Drab
Girls and boys, Drab v0.7.5 is out!
This version finally contains all the features of Shared Commanders I wanted to introduce, especially magic updates for living assigns in the specific shared commander - see the new demo example.
Now I am planning to focus on the living assigns again, as I have an idea how to completely remove all the limitations of the engine. Then, two big features must be introduced before we reach 1.0: event handler test framework and optimistic updates. Also, the project needs a code and documentation review, as the core evolved from the proof of concept page and never been changed
I’ll be on the Warsaw conference next week, if someone want to meet and have a chat.
OvermindDL1
Whoo!
Very nice! Reusable components are so convenient.
I’m curious how this will be done, just like embedded javascript or something?