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

2009-04-12:

[0:00] <hannesw__> jack will be supported, but it probably won't be the only connector
[0:00] <gozala> I was thinking that it would be nice to have something on top of jack
[0:00] <hannesw__> but generally, the webapp framework will become more than jack
[0:01] <hannesw__> the main thin i dislike about jack is the naming in the env object, with caps-lock names etc
[0:01] <gozala> so if someone will decide to move some other framework he will be able to take app some modules from helma and deploy there
[0:02] <hannesw__> yes, on top of jack
[0:02] <gozala> cool
[0:02] <hannesw__> well my preferred solution would be to change the jack naming conventions a bit so we could make our framework build on top of it
[0:03] <hannesw__> with the current cgi-like env object, we probably would replace the env object with our own request object
[0:03] <hannesw__> and it would be nicer if we could just augment it.
[0:03] <hannesw__> but that's for another day.
[0:04] <gozala> ok I will pull the changes now ;)
[0:04] <hannesw__> don't forget: getter -> get, setter -> set
[0:05] <gozala> so in case if you can drop some task to me mail me or just put it on mailing list
[0:05] <gozala> yeap I sew the patch
[0:05] <gozala> :)
[0:05] <hannesw__> ok, I'll think about it!
[0:05] <gozala> btw there is one more bug in request I'll drop you a patch later
[0:05] <hannesw__> ok
[11:55] <leobm> /msg NickServ leobm jfwijbmw!
[12:33] <decke> leobm_: you should change your password because you typed it in plaintext and hopbot will log it...
[12:34] <leobm_> decke: yes I did it already
[18:40] <liamMT> hiya - are there plans for any kind of unified persistence api in helma ng, or is it more likely that it will just end up being a handful of implementations for different backends?
[18:52] <hannesw> hi liamMT: i think we won't pretend to implement one unified api unless it's actually true
[18:52] <liamMT> hehe - that sounds pretty sane
[18:52] <hannesw> in helma 1, we have one api for relational and our own file based db (mostly for development)
[18:52] <liamMT> I see
[18:53] <hannesw> and it's quite a leaky abstraction...
[18:53] <hannesw> many things only working on relational db
[18:53] <liamMT> it occurred to me that maybe the datamapper (ruby db framework) approach might not be so bad
[18:53] <liamMT> would be a fair amount of work to port, but they have a nice api that supports relational and non-relational adapters
[18:53] <hannesw> have to look at that.
[18:53] <liamMT> just a thought, though :)
[18:54] <hannesw> thanks for the hint. I'm not too familiar with ruby, but I'll have a look
[18:55] <hannesw> I'm just working on google filestore api, and porting the storage demo app over to it.
[18:55] <hannesw> looks pretty good already
[18:55] <liamMT> gotchya - I've been working a bit with MongoDB lately, which is quite nice, and am thinking about wrapping that up to play with
[18:55] <hannesw> cool
[18:56] <liamMT> is there any info I should check out before diving in, other than the general modules/scopes pages in the wiki?
[18:57] <liamMT> I really like the way helma ng lays out, btw - seems very clean and simple. congrats :)
[19:01] <hannesw> thanks :-)
[19:02] <hannesw> well, documentation is a bit scarse (yet)
[19:02] <hannesw> but I try to help out on the mailing list and here on irc
[19:03] <liamMT> yeah - it's taken a little while to wade through it, but all the code is quite readable which helps a lot
[19:04] <hannesw> otherwise: the wiki: http://dev.helma.org/ng/
[19:04] <hannesw> but there's not a lot yet.
[19:06] <liamMT> ok, cool. thanks
[19:09] <rsaccon> hannesw: about google filestore api you mentioned, did you mean appengine db api ?
[19:10] <hannesw> oops, yes.
[19:10] <hannesw> i meant datastore api, as that's the name of the package: http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/datastore/package-summary.html
[19:12] <liamMT> hannesw: is your code for that public anywhere? I imagine that would be a pretty helpful place to look for examples/strategies
[19:12] <hannesw> i'm just working on the initial implementation
[19:12] <hannesw> as soon as I have the demo app working I'll commit it to svn/git
[19:12] <liamMT> cool - will look forward to that, thanks
[19:18] <rsaccon> yeah, really cool, look forward to try that out
[20:30] <hannesw> ok, just committed the module and demo app.
[20:30] <hannesw> http://github.com/hns/helma-ng/blob/e102a1982e25069489c5efcd14fb829fb66fa0c9/modules/helma/googlestore.js
[20:30] <hannesw> http://github.com/hns/helma-ng/tree/e102a1982e25069489c5efcd14fb829fb66fa0c9/apps/googlestore
[20:31] <hannesw> far from finished, but the simple demo app is working:
[20:31] <hannesw> http://helma-storage.appspot.com/
[21:18] <rsaccon> wow, amazing !!!!!
[21:20] <rsaccon> oh, and I didn't know that helma ng template language has the 'extends' tag
[21:22] <rsaccon> feel really bad now, because I mentioned in a blog that helma ng does not have template inheritance, will correct that ASAP
[22:56] <gozala> hi
[22:57] <gozala> I wonder if Sessions shoulfd work now?
[22:59] <gozala> I
[22:59] <gozala> might use it in a wrong way as well
[23:00] <gozala> I just add properties to the req.session.data and expect tem to be stored

 

 

In the channel now:

Logs by date: