I can only support that statement. jQuery is something of the past and should not be a requirement for a new technology.
svsdehh
grych
Creator of Drab
Thanks for those comments, folks. I have something to think about now 
About jQuery, Drab is modular and you don’t have to use it if you don’t want to. For now it is a default one, but I am planning to change it in a near future (and rename it to Drab.JQuery to give a space for a future non-jquery, first-choice default module).
I’ve chosen jQuery because it is easy and almost everyone knows it. And I just wanted to focus on the core of the library. And if you want to explain Drab in a short sentence, you can say “it is like jQuery, but server-side”
@OvermindDL1, thanks for an idea of the polymer-drab. This is really interesting and it could be a core idea of a brand new Drab module. I think we could go a step further - we don’t need post function! What about if the following would just work:
<span drab-wire style="height: [[blah]]">Message: [[bloop]]</span>
def clicked_some_button(_socket, _) do
blah = "100px"
bloop = "You are Drabbed"
[blah: blah, bloop: bloop]
end
System could update the interface based on what the event handler returned.
1
bitman
@grych Since you seem inclined to re-work some of the Drab syntax, I also recommend you look at the fusetools.com API for inspiration.
Fuse is a very young mobile SDK which makes a lot of previously hard things easy to do. https://www.fusetools.com/
1
OvermindDL1
That would indeed be entirely possible.
I quite like the template system in Polymer, it was designed to follow the WebComponents spec directly to the letter, which since it has been in flux a bit then Polymer has had a few minorly breaking changes with fallbacks in most cases for when it changes to match the spec again, but the spec is now pretty well set in stone, and the fallback to use unsupported browsers is just the webcomponent(-lite).js polyfill, which is used in quite a few libraries now including Polymer.
Still need some way to specify if setting variables global to the app or local to the element though, that is a big thing in polymer, everything is scoped to certain ‘areas’, which makes you not need to worry about things. Perhaps do the same, have no global scope but you have to decorate (via an attribute) certain root nodes where scoping happens?
1
grych
Creator of Drab
Here you go: Drab: Server Side User Interface Access
It is not very sophisticated. Well, it is rather absolutely primitive ! But I think it is quite well description how broadcasting works in Drab.
3
AstonJ
Max
@grych First i´d like to thank you for a great project you´ve started.
What is your roadmap for it? Are you committed to elixir / Drab on a long term basis or is it just something (Drab) you do for a proof of concept?
I´m coming from meteor and experienced many projects which ended up dead after a while.
2
grych
Creator of Drab
Hey @Max,
I understand you concerns. One of the reason I made Drab is because the projects I’ve been interested in - first Nagare, then Volt Framework, were abandoned.
I consider Drab beyond the proof of concept - in the beta stage. Drab.Core API is stable now, I am not planning to change it. About Drab.Query, despite the comments in this thread, I want to keep the existing API. Drab has the integration (end-to-end) tests, documentation (could be improved, I know) and the tutorial. I am surprised myself how mature it looks 
The rough plan for the future is:
- minor changes in the next version, 0.3.5, described in TODO.md
- head to 0.5.0, the next “major” release with the new main module (so make Drab.Query optional)
The new module in 0.5.0 is not to replace Drab.Query (it will stay and will be supported). I started with the jQuery, as it was the easiest way to archive my first goals - to prove it works, and it can be usable. Drab.Query is in fact just a bunch of helper functions, everything could be done using Drab.Core only; for ex the following function:
Drab.Query.select(socket, attr: :href, from: "#selector")
translates directly to:
Drab.Core.execjs(socket, "$('#selector').attr('href')")
The new main module will not rely on any existing JS library, it rather should be a new approach, more elixir/phoenix-like. I had some great suggestions in this thread, and I have some my ideas - I will be back with some RFC later.
Anyway, building Drab is not my full-time job, I am doing it on my free time only. Any help would be appreciated
5
grych
Creator of Drab
Hi folks,
someone asked me (on the Drab Chat!) how hard would be to add the presence list to the Chat Example. I found quite helpful to build it, as it seems to be a good way to teach Drabs onconnect and ondisconnect callbacks.
Here it goes: Drab: Server Side User Interface Access
Again, please treat it only as a learning case. There are much better ways to track users presence in Phoenix
4
