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

2009-11-19:

[10:02] <emilis_info> what do you use for session storage?
[11:30] <hannesw> everybody: please have a look at the helma-ng jsdoc app:
[11:30] <hannesw> http://helma-ng.appspot.com/jsdoc/
[11:30] <hannesw> it's pretty much complete
[11:30] <hannesw> i'm interested in your feedback.
[11:32] <simono> functions docs look a lot better
[11:33] <emilis_info> some unit tests fail
[11:35] <simono> in the function headline i would prefer String.pad(str, len, mode) over String.pad(String, Number, Number)
[11:36] <hannesw> simono: that's just a bug in the actual jsdoc comments
[11:36] <emilis_info> yep
[11:36] <emilis_info> other functions look fine
[11:36] <emilis_info> hmm
[11:36] <hannesw> emilis_info: the unit tests only fail on google app engine and windows, for various reasons
[11:36] <simono> okay.. hm.. consistent bug :)
[11:37] <hannesw> app engine is because of missing java file I/O, so that's non-fixable
[11:37] <emilis_info> http://helma-ng.appspot.com/jsdoc/file.js is totally missing documentation
[11:37] <emilis_info> overall the output of jsdoc looks nice
[11:37] <emilis_info> though there may be some readability improvements
[11:37] <emilis_info> :)
[11:38] <robi42> overall impression: very nice & definitely a step forward.
[11:39] <robi42> here & there some little bugs/errors.
[11:39] <hannesw> yep
[11:39] <hannesw> many of the bugs are actually in the jsdoc comments
[11:39] <robi42> guess so, e.g., links in http://helma-ng.appspot.com/jsdoc/helma/skin/filters.js
[11:40] <robi42> or link tag in http://helma-ng.appspot.com/jsdoc/binary.js description header
[11:40] <hannesw> hm, ok, that's a limitation in the app
[11:41] <hannesw> you can only have local anchors, or actual URLs in @link
[11:41] <hannesw> problem is the app doesn#t know which module contains something like String.prototype.foo
[11:42] <robi42> ah ok, i see. what about the failed @link tag?
[11:42] <hannesw> so you'd need a module name, like core/string#String.prototype.pad
[11:42] <robi42> ah
[11:43] <emilis_info> I think Overviews need some visual improvements
[11:43] <emilis_info> maybe a tree view or something similar
[11:43] <emilis_info> http://helma-ng.appspot.com/jsdoc/system.js
[11:44] <emilis_info> IMHO it should somehow separate between print() function and other variables in the overview
[11:44] <emilis_info> there's also a lot of white space wasted and a need to scroll a lot in some pages
[11:45] <emilis_info> and maybe fixing doc comments themselves should be a bigger priority
[11:45] <robi42> emilis_info: ack.
[11:46] <robi42> maybe also using frames could be useful in this context?
[11:46] <robi42> as, e.g., javadoc does
[11:46] <hannesw> yep, grouping functions and proeprties, and maybe folding objects would be logical next steps
[11:47] <emilis_info> frames would need a whole framework to support links like "frames", "no-frames", "index", etc.
[11:47] <robi42> right
[11:47] <emilis_info> maybe you could fold objects and modules by splitting by "." or "/" and checking name prefixes
[11:49] <emilis_info> also... comming from the PHP world, I miss comments :-) But I don't know how you could fit them into such a layout
[11:50] <robi42> some kind of "back to index" link could also be useful when coming to a sub page via link/google
[11:50] <emilis_info> yup
[11:50] <hannesw> well, the demo app is not the final destination of the api docs
[11:51] <hannesw> so it's getting its own app soon, with "dedicated" navigation
[11:51] <robi42> great
[11:51] <emilis_info> very good
[11:52] <robi42> there's also a convenient way to generate it locally (via shell)?
[11:52] <hannesw> so everybody feel free to fix and enhance jsdoc comments :)
[11:52] <robi42> :)
[11:52] <emilis_info> oh yeah! :-) one question though: how do i submit a patch?
[11:52] <hannesw> no statical rendering yet - but you can run the app with helma apps/jsdoc/main.js
[11:53] <robi42> ok
[11:53] <hannesw> emilis_info: just fork helma-ng on github
[11:53] <hannesw> that's the easiest way for me to review changes and merge
[11:53] <emilis_info> ah.. ok
[11:53] <emilis_info> :)
[12:15] <hannesw> *sigh* my appengine deploy routine is slightly cumbersome
[12:15] <hannesw> especially when the net is slow, as it currently is
[18:57] <botic> hi! has someone here ever used i18n libs for helma 1.x?
[19:17] <botic> okay i found some demo code for jala.I18n which solves the problem. it looks more useful than knallgrauLib.I18n for me
[19:37] <robi42> botic: didn't work w/ jala.i18n yet but the knallgrauLib one, naturally. actually, found the latter pretty decent.
[19:41] <botic> jep it looks nice, but jala.i18n uses po-templates which looks more "advanced" for the advanced software engineering lab at the university :)
[19:43] <botic> and it's bundled with helma, which makes it a little bit easier for our helma-beginners in the team.
[19:48] <robi42> ah ok, i see. personally, i prefer plain java properties files over .po, tho. :)

 

 

In the channel now:

Logs by date: