Hopbot log for 2009-02-25 - Helma IRC channel: #helma on irc.freenode.net

2009-02-25:

[0:02] <bard> hi all, I'd like to start playing with helma ng, any hint about a good starting point? (I'm at the "java -jar run.jar" and "print('hello world')" stage)
[0:13] <hannesw> bard: did you try running one of the bundled apps? java -jar run.jar apps/demo/main.js
[0:15] <bard> no, I didn't know I could just feed main to run.jar (and the late hour doesn't help my imagination apparently :)). thanks for the pointer
[0:18] <bard> hannesw: how unreasonable would it be to start writing now on helma-ng an app eventually targeted for production? (I'm comfortable with some level of unreasonableness :) and don't mind hacking the framework itself when needed)
[0:20] <hannesw> bard: there is some amount of change yet to come
[0:20] <hannesw> so it's not really frozen. but it should't be too hard to follow, either
[0:21] <hannesw> IMO the biggest missing piece is a fully featured persistence/O/R mapper
[0:21] <hannesw> it really depends on what you need
[0:23] <bard> hannesw: if that's the biggest missing piece, I can totally live with it, since I plan on using couchdb anyway
[0:24] <hannesw> great! I have adapted the couchdb js api to work with helma ng, in case you need it
[0:24] <bard> sweet
[0:26] <bard> by the way, what is the primary repository nowadays? svn or git? (or the real question: can I just track, and possibly contribute via, the latter?)
[0:27] <hannesw> here it is: http://helma.pastebin.com/fccb9882
[0:28] <hannesw> actually, the github repository is a mirror of the svn
[0:28] <hannesw> but I'm not really happy with that, because i can't easily merge git branches...
[0:28] <bard> I see
[0:29] <hannesw> right now, it doesn't matter. if you want to use git locally, it's conveneint to clone the github repository i guess
[0:29] <bard> couchdb module saved, thanks a lot :)
[0:29] <hannesw> it's a few months old, might have changed in the meantime.
[0:29] <bard> well, I suppose I could use git-svn against the primary repo
[0:30] <bard> and stay up to date while still having topic branches and local commits
[0:30] <hannesw> yes
[0:32] <hannesw> it's late here, off to bed
[0:32] <bard> here too (gmt+1). good night!
[0:32] <hannesw> :-) good night
[9:23] <hannesw> good morning
[9:23] <hannesw> quick poll - simono, zumbrunn, earl_
[9:23] <hannesw> should we move to serverjs securable modules naming?
[9:24] <hannesw> "/" as separator, "." for relative current directory, ".." for relative parent directory
[9:24] <hannesw> what do you think?
[9:24] <hannesw> having explicit current/parent dir tokens is nice, IMO
[9:25] * zumbrunn likes the dot syntax when using modules.helma.file syntax
[9:26] <zumbrunn> when talking about a string argument, I anyway always preferred the slashes
[9:26] <hannesw> zumbrunn: ok, that's js dot syntax, so that's out of discussion
[9:26] <hannesw> yes, talking about "str/ings"
[12:09] <simono> late vote: "/" as seperator in strings seems alright. the alternative would be "." i presume and then we don't have rel imports?
[12:54] <zumbrunn> or to support both, I guess
[12:54] <zumbrunn> but I think it is better to just switch to slashes
[12:58] <simono> so with "." as seperator and supporint grelative imports I could write "..foo.bar.test.js" :)
[12:58] <simono> ^^supporting relative imports
[14:18] <hannesw> zumbrunn: you're such an inclusive guy ;-)
[14:18] <hannesw> i'm really in favor of deciding here. either-or
[14:19] <zumbrunn> right, and if we want to be compatible with the current serverjs proposal, that means switching to slashes
[14:20] <zumbrunn> unless we want to go and convince them of using dots instead :-)
[14:21] * zumbrunn is checking whether that was actually written into the proposal...
[14:22] <zumbrunn> yes, it was
[14:23] <zumbrunn> (slashes, that is)
[15:12] <simono> well i'm pro slashes, if that wasn't clear
[18:06] <hannesw> ok, will convert to slashes tomorrow. I'm really happy for the explicit relative links.
[18:06] <hannesw> right now we try relative first, absolute later
[18:06] <hannesw> it's always better to be explicit.
[18:07] <hannesw> the only problem i see is with possible security problems, like using ../../ to get out of the module root

 

 

In the channel now:

Logs by date: