Ringobot log - RingoJS IRC channel: #ringojs on irc.freenode.net
2010-08-10:
[7:06] <hannesw> good morning[7:07] <hannesw> ready for irc meeting... soon
[7:07] * earl whistles
[7:07] <hannesw> :)
[7:08] <hannesw> back in ~5 minutes
[7:16] <hannesw> ok
[7:17] <hannesw> just adding "oberhamsi jsdoc merge" to the agenda
[7:17] <hannesw> http://ringojs.org/wiki/IRC_Meeting/
[7:18] <hannesw> ping earl emilis_info rist robertgg waddler
[7:18] * earl nods
[7:18] <hannesw> so first item: website improvements
[7:18] <emilis_info> wat
[7:19] <hannesw> irc meeting starting now
[7:19] <emilis_info> uh
[7:19] <emilis_info> never been to those
[7:19] <emilis_info> ok, I'll stop pretending I'm stupid
[7:19] <emilis_info> ;)
[7:19] <hannesw> i know
[7:19] <emilis_info> is there an agenda for this meeting? :)
[7:19] <hannesw> fully voluntary of course
[7:19] <hannesw> yes, http://ringojs.org/wiki/IRC_Meeting/
[7:20] <hannesw> so my ping was just a reminder, no expectations :)
[7:20] <emilis_info> where can I find out about oberhamsi jsdoc merge?
[7:20] <hannesw> hi zumbrunn
[7:20] <zumbrunn> hello :-)
[7:20] <hannesw> yesterday's merge is here: http://github.com/ringo/ringojs/commit/7011b38640a921d24b907ccd9bf0c202cda7a14e
[7:21] <hannesw> it's big
[7:21] <hannesw> bottom line is there's now a ringo-doc command line tool
[7:21] <hannesw> for statically generating jsdoc
[7:21] <hannesw> and jsdoc live app is ... somewhat changed
[7:22] <hannesw> there's now a live module name filter on the right
[7:23] <hannesw> personally i have a few issues with the new design
[7:23] <hannesw> so we could talk about that, too
[7:24] <hannesw> and multi-repository view has gone, which poses a problem for ringojs.org, where we used this feature.
[7:24] <hannesw> unfortunately oberhamsi is on holiday this week...
[7:25] <earl> well, multi-repos view should be not too hard to get back, i guess
[7:26] <hannesw> I'm not sure
[7:26] <hannesw> it affects the whole url routing etc
[7:27] <hannesw> what about the scroll animation and highlighting effects in the old version?
[7:27] <hannesw> should we get those back?
[7:27] <earl> possibly, yes
[7:28] <hannesw> e.g. when you click on any function name here: http://ringojs.org/api/master/ringo/httpserver
[7:28] <earl> but i don't think it's of much importance, for the moment
[7:29] <hannesw> well the most important thing is we find a way to deploy this on ringojs.org
[7:29] <emilis_info> scrolling effect is nice, but not vital, highlighting the target section is more important IMHO
[7:29] <hannesw> ok
[7:31] <hannesw> one issue i have is that the right side filter box is not on the main module overview page
[7:31] <hannesw> it would be a bit redundant, but the bit list and the filter box serve different purposes.
[7:31] <earl> for me there's no right side filter box on the module page as well :)
[7:31] <hannesw> also, i think filter input field should have focus on page load
[7:32] <earl> ah! there it is
[7:32] <hannesw> if you click on a module it's there
[7:32] <earl> css caching issue, i guess
[7:32] <earl> why do we need all those index.html's in the urls?
[7:32] <hannesw> oh yeah: ugly!
[7:33] <hannesw> but it's there to have the same links between static and dynamic version
[7:33] <hannesw> still...
[7:34] <earl> don't think that's needed
[7:34] <hannesw> i think the reason simon wanted the same link is to simplify html/link generation
[7:34] <earl> abstract the linking away in a macro, and do index.html only for the static version
[7:34] <hannesw> if we can do this, that would be a big plus IMO
[7:39] <ringostarr> 8e63a5d Andreas Bolka: Whitespace police
[7:39] <hannesw> wow, lots of police work :)
[7:39] <ringostarr> d8afd72 Andreas Bolka: Whitespace police
[7:40] <hannesw> was that all in yesterday's merge?
[7:40] <earl> yes
[7:40] <earl> whoop whoop!
[7:40] <earl> (that's the sound of ...)
[7:40] <hannesw> luckily intellij fixes this for me.
[7:40] <hannesw> do you have a tool for fixing this?
[7:40] <earl> vim macros, yes
[7:41] <hannesw> nice.
[7:41] <hannesw> but so you have to open files in vim to do this, or will vim scan through directories?
[7:42] <earl> in this case i manually fixed it while looking thru the code
[7:44] <earl> multi-repo support and url fixing should not be too hard
[7:45] <earl> looks like the necessary changes would be quite localised
[7:45] <hannesw> wanna go for it?
[7:47] <earl> but in general, git diff --check will show all whitespace errors
[7:48] <earl> i'll look at it for a bit, but i don't have too much time at the moment
[7:49] <hannesw> I'll look at the formatting side
[7:50] <hannesw> i just added another item to the agenda:
[7:50] <hannesw> "making parts of ringojs.org site static"
[7:50] <hannesw> http://ringojs.org/wiki/IRC_Meeting/
[7:51] <hannesw> this is about keeping stuff in git/github
[7:51] <hannesw> and then serving it with http://github.com/davidbierbauer/simplesite
[7:51] <earl> i think the main question for that is where we want to keep the static stuff
[7:51] <hannesw> in git/github?
[7:52] <earl> a few options that come to my mind:
[7:52] <earl> - mainline ringo repo, in a docs/ directory
[7:52] <earl> - ringojs.org repo
[7:52] <earl> - a wholly separate repo
[7:52] <hannesw> true
[7:52] <earl> i'd personally go for the first option
[7:53] <hannesw> it depends on how much stuff and what exactly we want to keep there
[7:53] <hannesw> if it's only the home page and a few other things, first option does not make that much sense imo
[7:54] <hannesw> tutorial and similar stuff would be nice to have bundled with ringojs
[7:54] <hannesw> but it'll be mostly in markdown format
[7:54] <earl> yeah, but markdown is quite fine to read in an editor as well
[7:55] <emilis_info> tutorial would be nice, but framework packages that include whole documentation with them seem a bit bloated to my taste
[7:56] <emilis_info> maybe I'm spoiled :)
[7:57] <earl> i tend to think that the closer the docs are to the code, the greater the chance that they are actually kept up-to-date as the code progresses
[7:58] <earl> which is obviously less of an issue once a system matures
[7:59] <hannesw> yes, except i would tend to keep in git what is more like "marketing copy"
[7:59] <hannesw> i.e. front page and surrounding documents
[7:59] <hannesw> and maybe keep more documentation like pages in wiki
[7:59] <hannesw> so that wouldn't work, would it?
[8:00] <earl> that'd probably make more sense in the ringojs.org repo
[8:00] <hannesw> or should we try to get everything in the git site, and leavve the wiki for whatever comes then?
[8:00] <earl> dunno
[8:00] <earl> how about adding a simple but restricted "render-document" macro to the wiki?
[8:01] <earl> a markdown extension, that is
[8:01] <hannesw> for rendering static pages as part of the wiki?
[8:01] <earl> yep
[8:01] <hannesw> i wanted to do that first
[8:02] <hannesw> but i think the simplesite approach is much better
[8:02] <hannesw> for one, it lets us use the root urlspace of ringojs.org, and keep the wiki in /wiki/
[8:02] <hannesw> i kind of liked this idea
[8:02] <earl> (which i consider to be a disadvantage, as it needlessly fragments things)
[8:02] <hannesw> it's just hard where to put the line between static and wiki content
[8:03] <hannesw> well, at some point we'll have to have a site that is not a wiki
[8:05] <hannesw> and i think it's good to have the wiki as a dedicated area, as we have now
[8:05] <earl> maybe
[8:06] <earl> as some kind of scratchpad and area for note-taking
[8:07] <hannesw> right
[8:12] <hannesw> ok, meeting is over
[8:12] <hannesw> some words about issue 1 and 2:
[8:12] <hannesw> website redesign - me and oberhamsi thought about that based on usage/flow graph
[8:12] <hannesw> http://stats.nekapuzer.at/static/clickgraphs//ringojs/201007.png
[8:13] <hannesw> oberhamsi already started reworking stuff, it's an ongoing thing
[8:13] <hannesw> in the mid-term, we'll have to do some redesign of the ringojs.org site
[8:13] <earl> agreed
[8:13] <hannesw> to fix some navigation issues
[8:14] <hannesw> anybody is welcome to contribute thoughts and design sketches to that
[8:14] <hannesw> and number 2 - 0.6 release
[8:15] <hannesw> that'll be when the jsdoc and utils changes are completed
[8:16] <hannesw> does that sound ok?
[8:16] <earl> yep
[8:16] <hannesw> (for example, we still have a "ringo/fileutils" modlue which should probably be "ringo/utils/files"
[10:44] <maks> hi, just working on my first proepr ringo app and have question - should I be able to access req.session from a middleware module?
[10:51] <maks> I should add I can access req.session just fien from within my apps actions, it just seems that req.session is undefined within my middleware
[13:04] <oravecz> when I write my own macros, is there a call I can make to expand embedded keys?
[13:04] <oravecz> i.e. <% link src='/path/to/<% something %> %>
[13:04] <oravecz> link is my macro, I would like 'something' to be expanded.
[13:41] <oravecz> hi
[14:24] <oravecz> when I write my own macros, is there a call I can make to expand embedded keys?
[14:24] <oravecz> i.e. <% link src='/path/to/<% something %> %>
[14:24] <oravecz> link is my macro, I would like 'something' to be expanded.
[14:54] <hannesw> oravecz I'm not sure, but I don't think it's exported right now in ringo/skin
[16:47] <oravecz> thx for the answer
[17:20] <ringostarr> 55bdb58 Hannes Walln?fer: Make parameter helpers protected.
