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

2007-12-06:

[11:23] <zumbrunn> hypersmil, in case you're around...
[11:23] <zumbrunn> as description for schedulerInterval you suggested...
[11:23] <zumbrunn> "Defines the time in seconds after which the cronjobs are executed again, the cronjob can be called several times a minute"
[11:23] <zumbrunn> why is the second part helpful?
[11:24] <zumbrunn> isn't it clear that it can be "several times per minute" if the interval can be defined in seconds?
[11:28] <zumbrunn> oh, I see
[11:29] <zumbrunn> because the minimal interval using the cron property syntax is a minute, right?
[11:32] <hypersmil> no, i was thining about something else, but i have to test it, wait a moment
[11:34] <hypersmil> if you choose a number greater than 30 it won't be called more than one time a minute, if you choose a number greater than 60 no cronjob will be executed
[11:39] <zumbrunn> aha, ok!
[11:48] <hypersmil> meaning you can use the schedulerinterval as offset, but thats probably an bug not a feature?
[11:52] <zumbrunn> I'll need to look through the mailing list messages from back when this was implemented/changed
[11:53] <zumbrunn> maybe that will reveal what the intended behavior is
[11:53] <zumbrunn> but first...
[11:53] * zumbrunn goes walking his dogs
[15:54] <zumbrunn> the wording I ended up with turned out to be a bit more verbose:
[15:54] <zumbrunn> "The time in seconds after which scheduled cron jobs are executed again. Makes it possible to cause cron jobs to be run several times per minute. Note that this will have the side effect to invoke *all* cronjobs at the specified seconds interval within the minute that they are scheduled to run. For example, with this setting set to 5, a cron job that is scheduled to run once a week, will run every five seconds during one minute once a week
[15:54] <zumbrunn> http://helma.org/docs/guide/properties/listall/
[16:03] <zumbrunn> and on the page explaining the cron config syntax, I added the following...
[16:03] <zumbrunn> "Seconds and milliseconds are ignored, so the smallest interval is a minute. For cases where you need to run cron jobs every few seconds, a schedulerInterval property in app.properties can serve as a workaround."
[16:03] <zumbrunn> http://helma.org/development/rfc/cronjobs/
[16:28] <hypersmil> i found a typo in the cronjob rfc "An asterix (*)"
[16:30] <hypersmil> the api docs are very nice, do you use the js-toolkit already?
[16:34] <zumbrunn> yes, the ones at http://helma.zumbrunn.net/reference/ are jsdoc-toolkit generated
[16:34] <zumbrunn> I'm still fixing some bugs though
[16:38] <zumbrunn> ok, fixed the asterisk and also added the whole schedulerInterval explanation rigmarole instead of just referring to the app.properties docs
[17:46] <d2m> hi, all -- i wonder if there are any macros in use that support conditional logic, variable definition etc.
[17:47] <zumbrunn> within the macros you can have any logic you like, of course
[17:47] <zumbrunn> I assume what you are asking is having the logic in the skins themselves?
[17:47] <d2m> correct
[17:48] <d2m> don't you need template logic ?
[17:48] <zumbrunn> that's almost a religious question ;-)
[17:48] <d2m> sure, i'm doing ZPT most of the time, developing Zope apps
[17:48] <zumbrunn> I'm trying to find a link to something that could be what you are looking for...
[17:49] <zumbrunn> not sure if I'll find it, though
[17:49] <zumbrunn> not even sure where to search or what keywords to search for yet
[17:50] <d2m> i'm curious if e.g. the ORFon sites need such features
[17:50] <d2m> antville works very nice with plain helma macros
[17:50] <zumbrunn> the orf folks generally are on the other side of that religious war
[17:51] <zumbrunn> but it was tobi from the orf that wrote a macro that basically provides conditional functionality
[17:51] <zumbrunn> made possible by the new macro features in helma 1.6
[17:51] <zumbrunn> just trying tom think where and when he mentioned/posted that
[17:52] <zumbrunn> trying *to* think
[17:52] <d2m> heh, ok
[17:55] <zumbrunn> found it...
[17:55] <zumbrunn> http://helma.org/pipermail/helma-user/2007-May/006997.html
[17:55] <d2m> ah, great
[17:57] <d2m> so, question remains - it it necessary for a current webframework to support conditional logic ?
[17:57] <zumbrunn> no
[17:57] <zumbrunn> :-)
[18:04] <d2m> is "Helma 2 Template Framework" something to come (http://dev.helma.org/wiki/Helma+2+Templates) or just a discussion?
[18:05] <zumbrunn> just a discussion...
[18:05] <d2m> ok, thanks
[18:05] <zumbrunn> for a short while it looked like we'll be heading in the direction of using Jürg's javascript template engine
[18:06] <zumbrunn> but with the new features added to the java based skin implementation in helma 1.6 we moved away from that again
[18:06] <d2m> i see
[18:07] <zumbrunn> personally, I think many ways lead to Rome
[18:08] <zumbrunn> in some situations using e4x as a skin replacement is an attractive option

 

 

In the channel now:

Logs by date: