Awesome, I’ll give that a try when next I’m working on it. 
It’s safe to just send that as javascript from elixir via on_connect or so?
OvermindDL1
grych
Creator of Drab
I would rather send it on load fro elixir, as with on connect you might end with multiple callbacks
OvermindDL1
Also, what is the recommended way to kill the session when, say, they logged out, thus killing all their other open browser windows and connections. I kill the websocket entirely via disconnect but they are able to reconnect using the same token that Drab supplied, is there any way to mark it as invalid and prevent reconnection as I’m not able to override the socket initialization with drab?
grych
Creator of Drab
This is because of the max_age of the token, it is set to 86400. I am going to allow you to set it.
OvermindDL1
A cache of sessions (I have my own API so as long as I can plug it in) to check against on websocket connections with the associated session token is how I do it.
Ah right, that was added in later, it wasn’t possible for an early period of time there. ^.^
Actually I prefer very very short tokens but I also like to be able to send token updates. Like on another websocket connection that is long-lived a new token is sent across to the client periodically that they can use to reconnect with if the connection dies (I have it set to 15 minutes tokens refreshed after 10 minutes to allow a 5 minute delay of no-contact else a page refresh is required). Keeping a long-lived token means it can be re-used more easily.
EDIT: For note, the token usually just packs a session ID, of which ‘that’ also can independently be elapsed via the database/cache.
grych
Creator of Drab
I see. Now I think it is out of Drab scope, but we might build something like in a future, as it may be useful, especially for beginners!
Also, what I am still thinking of, and may be connected with your idea, is to build some abstraction (session) over the socket, which would be used to survive disconnections. So the handlers, instead of socket, would get some session (browser or even user) id, and if you run the background process (not linked to the handler) you may proceed even in case of the disconnection in the meantime.
You may do something like this now, just broadcasting to the topic, but it is one-way communication only - trying to read from the browser on disconnected socket returns {:error, :disconnected} and you must deal with it yourself.
It may also store the messages sent during disconnection, so after reconnect browser will run all remaining code.
Also, we could provide a “waiting for reconnect” API, like:
defhandler handle_event(session, _payload) do
spawn fn ->
do_some_long_process()
x = query_one(session, "#input1", :value) do
on {:ok, x} -> x
after 50000 -> raise "gone forever"
end
end
end
But, as I said, it is rather a future stuff.
Yep, it was added after you persuaded me to do it
grych
Creator of Drab
v0.9.1 is out - jQueryless Boostrap Modal
Hi guys,
I’ve just released v0.9.1, where the most important change is the Drab.Modal is not dependent on jQuery anymore! And because of this, I have included it to the default modules, so it works out of the box (important for beginners).
Modal can be extremely useful, when you need a user input. Imagine that your function runs some SQL update, and you want to ask whether we should commit or rollback. With Drab.Modal.alert it is easier than anything:
case alert(socket, "DB update", "#{no_rows} updated.", buttons: [ok: "Commit", cancel: "Rollback"]) do
{:ok, _} -> commit(db, query)
{:cancel, _} -> rollback(db, query)
end
Modal can also have some inputs inside, in this case it returns their values as a second element of the return tuple.
iex(5)> alert socket, "Title", "<input name='fname'><input name='lname'>"
{:ok, %{"fname" => "Grzegorz", "lname" => "Brzęczyszczykiewicz"}}
This is a bootstrap modal, so it obviously needs bootstrap. But everything is prepared to add more css frameworks. I will add Foundation support in the spare time.
Drab.Query is (and will be) the only one module which is jQuery dependent. Long way since the first version announced here almost two years ago, as Drab - the jQuery in Elixir
antalvarenga
I’m trying to setup drab in my existing app, but I just can’t get it to work. Followed every step in the installation guide and tried the simple PageController test. The only thing that shows when I run iex -S mix phx.server is
19:31:47.314 [info] Compiling Drab partial: lib/risk_web/templates/page/index.html.drab (giydamrugmztimrw)
But nothing changes in the template. Any ideas on what could be the problem? Phoenix version is 1.3 and elixir is 1.6.
I also checked the manual installation and everything was in place.
OvermindDL1
Elaborate? Like ‘how’ is the template not changing? You do only have a *.drab version of the template and not a *.eex version too yes? o.O