Monday, 2 December 2013< ^ >
Arjan has set the subject to: Zotonic - The Erlang Web Framework & CMS
Room Configuration

[09:01:35] cillian.deroiste joins the room
[09:04:59] cillian.deroiste leaves the room
[09:30:01] arjan joins the room
[09:58:44] Maas joins the room
[11:37:13] Maas leaves the room
[12:53:24] <Kaos> Marc Worrell, arjan: as you know, I'm working on "ztl", the "zotonic template language" which is erlydtl with some custom extensions.
[12:53:55] <Kaos> I was thinking if we should host ztl as a standalone project.. or it that's a backwards idea..
[12:55:12] <Marc Worrell> It couldn't really run without all the internal zotonic apis, can it?
[12:55:17] <Kaos> there's two points for the question. a) while I develop it, I wouldn't need to keep up with master, doing rebases etc.. and b) when it is released, others might want to use our template stuff in other non-zotonic projects..
[12:55:36] <Kaos> could be that, yeah..
[12:55:47] <Marc Worrell> If we can define a clean(ish) api, then it is good to keep separate.
[12:56:06] <Marc Worrell> Keeping separate in different apps is definitely the way we want to go forward anyway.
[12:56:09] <Kaos> we could pass in module names to use for the specifics, that way it would be easy to override..
[12:56:11] <Marc Worrell> (with modules etc as well)
[12:56:46] <Marc Worrell> Yep, and if we just mix those modules names in the compiled/generated code then it won't affect runtime performance.
[12:57:07] <Kaos> yeah, I'd like to see more separation of concerns.. but we'd have to keep an eye out so it doesn't turn into 50 repo dependency nightmare either...
[12:57:15] <Kaos> indeed.
[12:57:47] <Kaos> It will be easier to test when we can contain it in its own repo, too..
[12:58:22] <Kaos> or, rather, it's easier to have boundaries on what to test..
[12:59:19] <Kaos> that was actually the third point, which I forgot about, but was the reason I brought it up in the first place, namely c) easier to test the template stuff..
[13:08:19] Maas joins the room
[13:08:25] <Kaos> hmm.. there's one major show stopper for it though.. and that is comparison. I want my tests to compare the result of the old (current) version to the new one
[13:13:50] <Kaos> Marc Worrell: why have you included the elog dependency in zotonic's rebar.config file?
[13:14:34] <Marc Worrell> No, I didn't
[13:14:38] <Kaos> as that one points to zotonic/elog while emqtt's rebar.config points to erylee/elog.. which results in a conflict error message from rebar: http://pastebin.com/HHu3MFKf
[13:14:40] <Marc Worrell> Did I?
[13:14:42] <Marc Worrell> hmmm
[13:14:47] <Marc Worrell> Let me check
[13:15:08] <Marc Worrell> Oh, then I did that for emqtt
[13:15:09] <Kaos> https://github.com/zotonic/zotonic/blob/master/rebar.config#L36
[13:15:50] <Kaos> I guess we could update our fork of emqtt to use zotonic/elog, and drop line 36 from zotonic/rebar.config.. right?
[13:15:55] <Marc Worrell> rebar is really brain dead
[13:16:20] <Maas> :-) indeed.
[13:16:24] <Kaos> well... the config does point to two different forks of the same project.. :p
[13:16:50] <Marc Worrell> This is a normal thing to happen when you mix projects.
[13:16:57] <Kaos> certainly
[13:17:15] <Marc Worrell> So the zotonic.app config should be leading, without changing all .configs of all projects
[13:17:26] <Kaos> there's a third issue, and that is that you may already have a number of the deps projects in erlangs lib path..
[13:18:00] <Marc Worrell> yeah, but in that case it should be a warning, and not an ERROR
[13:18:21] <Marc Worrell> Is there a way to overrule sub-project definitions?
[13:18:24] <Kaos> hah, then rebar got the wrong version of elog.. as it started with the sub dirs (guessing)
[13:18:33] <Kaos> no idea..
[13:18:55] <Marc Worrell> Rebar should make a dependency graph with priorities, based on the names of the deps
[13:18:57] <Kaos> I think rebar has grown into a monster of hard to follow undocumented features
[13:19:07] <Marc Worrell> and then start checking them out
[13:19:21] <Kaos> indeed... there's room for a lot of improvements in rebar :)
[13:19:38] <Marc Worrell> for now, just remove the elog line from the zotonic config
[13:20:02] <Marc Worrell> keep the emqtt branch as-is, as that one will be merged into the main emqtt soon
[13:20:35] <Kaos> hah.. I see the only change you did to elog was to switch fork of a dep project..
[13:20:46] <Kaos> which feels like a fix for what we just encountered here..
[13:23:15] Steffen Hanikel joins the room
[14:14:51] <z-bot> [mvw] http://en.wikipedia.org/wiki/Zoton
[14:24:27] <Maas> http://www.dokteronline.com/en/zoton-fastab/
[14:24:39] <Maas> Keep out of reach of children. :-)
[14:26:04] <arjan> this weekend somebody said to me,
[14:26:18] <arjan> "I keep bumping into this softonic website of yours"
[14:26:19] <arjan> http://en.softonic.com/
[14:26:23] <arjan> not really ours ;)
[14:26:54] <Marc Worrell> softonic? never heard of that one
[14:27:51] <z-bot> [mvw] @Maas: :-)
[14:51:35] Steffen Hanikel leaves the room
[14:58:04] Maas leaves the room
[15:23:01] Steffen Hanikel joins the room
[15:47:08] Steffen Hanikel leaves the room
[16:07:36] Steffen Hanikel joins the room
[17:57:01] arjan leaves the room
[19:22:30] arjan joins the room
[19:41:38] arjan leaves the room
[19:43:15] cillian.deroiste joins the room
[20:09:34] arjan joins the room
[20:20:10] Maas joins the room
[20:47:29] jeff.5nines joins the room
[20:55:31] Maas leaves the room
[20:58:49] arjan leaves the room
[21:05:33] Maas joins the room
[21:08:00] arjan joins the room
[21:16:14] arjan leaves the room
[22:26:38] jeff.5nines leaves the room
[22:27:22] Mawuli joins the room
[22:59:05] arjan joins the room
[23:17:57] arjan leaves the room
Powered by ejabberd Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!