Logs for the RingoJS IRC channel,
as logged by ringostarr.
2010-11-17
[09:40] <hannesw> FYI: I finalized the roadmap for the 0.7 release (kind of)
[09:40] <hannesw> http://ringojs.org/wiki/Release_0.7/
[09:41] <hannesw> plus issues labeled "0.7": https://github.com/ringo/ringojs/issues/labels/0.7
[09:56] <olegp> hannesw: looks good
[09:56] <olegp> would be nice if there was some way for apps to also specify which packages they depend on
[09:57] <olegp> in my current version of ringo-admin package I just bundle up all packages when building a war, which isnt ideal
[09:57] <hannesw> olegp: there will be
[09:57] <hannesw> i guess we'll just use package.json files
[09:57] <olegp> yea
[09:57] <hannesw> and a ringo-admin command to install all dependencies
[09:58] <hannesw> I'm not sure about how to resolve dependencies
[09:58] <hannesw> whether to have an online registry or some kind of bundled catalog
[09:59] <olegp> Id like something that relied more on github
[09:59] <hannesw> yes, it should be able to install from github
[09:59] <olegp> rather than having a separate online registry
[09:59] <hannesw> including support for git tags for versions
[10:00] <hannesw> well the registry might be a web app running somewhere IMO
[10:00] <olegp> why cant we just use the github api for a repository with that name?
[10:00] <olegp> and if theres more than one ask the user which one they want?
[10:01] <olegp> github api to search for a repository with that name, I mean
[10:01] <hannesw> so you want to use the username/package convention for dependencies?
[10:01] <olegp> no
[10:01] <olegp> just the package
[10:02] <olegp> but then run a search on github for all repositories
[10:02] <olegp> so you get a list of username/packages
[10:02] <olegp> and if theres one, default to that
[10:02] <olegp> if theres more, ask user which one they want to install
[10:02] <hannesw> ah no, i don't like that, sorry
[10:02] <hannesw> first, it excludes anything else than github
[10:03] <hannesw> second, it requires knowledge by the enduser. Imagine somebody just creates a package with the same name
[10:04] <hannesw> I'm convinced we need some kind of registry, either narwhal-style (as some json file kept on github) or npm style (as an open online registry)
[10:04] <hannesw> or somewhere in between
[10:04] <olegp> Im more in favour of an open one, hence the github lookup suggestion
[10:05] <olegp> it would be as simple as ...
[10:05] <olegp> curl http://github.com/api/v2/json/repos/search/ringo-hibernate
[10:05] <olegp> but I get your concerns
[10:09] <hannesw> afk, back in an hour or so...
[10:10] <olegp> maybe the thing to do would be to stick to just package names in dependencies
[10:10] <olegp> but allow for pluggable resolvers
[10:10] <olegp> one could do the github lookup I suggested
[10:10] <olegp> and others could do a lookup via an npm style registry
[20:41] <hannesw> tschaub what do you think about this so far:
[20:41] <hannesw> https://github.com/hns/stick/blob/master/demo.js
[20:41] <tschaub> hey hannesw
[20:41] <hannesw> hey
[20:41] <hannesw> i used the middleware name for all configuration methods so far (basicauth, static, etc)
[20:43] <tschaub> that looks really slick hannesw
[20:43] <tschaub> I like it
[20:43] <hannesw> cool :)
[20:44] <hannesw> definitely have to work more on documentation
[20:45] <tschaub> do you think stick middleware will be useful outside of stick?
[20:45] <hannesw> well i think stick module itself should be pretty portable
[20:45] <hannesw> do you mean outside of stick on ringo, or on other platforms?
[20:46] <tschaub> well, I was just thinking that things like basicauth would be very useful even if someone weren't using stick
[20:47] <tschaub> ringo/jsgi/middleware perhaps
[20:47] <tschaub> but maybe stick is the lowest common denominator
[20:50] <hannesw> well given that the type of middleware factory signature is specific to the way it's configured...
[20:50] <hannesw> but the current middleware will continue to exist in ringo-webapp or whatever it'll be called