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

2008-11-12:

[8:57] <zumbrunn> good morning hannesw
[8:58] <zumbrunn> how are we standing for rc3?
[8:58] <zumbrunn> is there some fix still pending?
[8:58] <hannesw> hi chris
[8:58] <hannesw> from my part I think we're ready
[8:58] <hannesw> there were two commits i think
[8:59] <zumbrunn> ok
[8:59] <hannesw> one against dos attacks
[8:59] <zumbrunn> I'll do an rc3 then today or tomorrow
[9:00] <hannesw> (the other for removing jetty dependencies from StandaloneServletClient
[9:00] <hannesw> yes, i'll do some more testing today
[12:42] <simono> test
[22:22] <Helma0> hey guys, simple question: what is helma? a framework, but what is implemented already?
[22:24] * zumbrunn waits to see if Helma0 comes back
[22:26] <jirkap> anyone here?
[22:26] <zumbrunn> define "here"
[22:27] <jirkap> huh
[22:27] <jirkap> :)
[22:27] <zumbrunn> ;-)
[22:30] <jirkap> I would like to do a simple thing: I have a link in a skin, and when I click it, I want another skin to be the part of the original page.. I tried actions, macros, everything (not really intentionally at the end), and I'm lost now. Would you give me a clue?
[22:31] <zumbrunn> what do you mean by "the part of the original page"?
[22:33] <jirkap> well, let's say I have some page with a link only. When I click it, I want the page to be reloaded and the result contains the link (the original 'main_action' + some text which is embed in another skin).
[22:35] <zumbrunn> one way would be to make the link point to a different action
[22:35] <zumbrunn> like "/something" instead of "/main"
[22:36] <zumbrunn> or make the link include a get parameter in the request
[22:37] <zumbrunn> and check for that to determine if you include that other skin in the output or not
[22:37] <zumbrunn> there are really many ways to go about it
[22:37] <jirkap> like action="GET" as an <a> attribute?
[22:38] <zumbrunn> like "/main?foo=true"
[22:39] <zumbrunn> or "./?foo=true" or whatever
[22:40] <jirkap> so 'foo' would be an action?
[22:40] <zumbrunn> no, this would be in the case of using get params
[22:41] <zumbrunn> "./foo" would be an action
[22:42] <jirkap> sorry, i don't get it.. where the 'foo' would be defined then?
[22:43] <zumbrunn> in the case of "./?foo=true" you would check for it using like this: if (req.data.foo){this.renderSkin('some.skin')}
[22:44] <zumbrunn> ...inside the main action, in this case
[22:44] <jirkap> great thanks!
[22:45] <zumbrunn> but normally, if you want to output a different skin based on a link like that, you would point the link to a different action
[22:45] <zumbrunn> so, like "./foo"
[22:46] <zumbrunn> and in that case "foo" would be an action, yes
[22:47] <jirkap> but then I have to make the same action like main_action again (just named foo_action) and just add another line, right?
[22:47] <zumbrunn> could be, yes
[22:47] <jirkap> hmm
[22:47] <zumbrunn> depends on what exactly it is you are doing
[22:48] <zumbrunn> of course, "./foo" is prettier than "./?foo=true"
[22:49] <zumbrunn> and you could move the code you would otherwise have to duplicate to a separate function
[22:49] <zumbrunn> which you then call from both actions
[22:50] <zumbrunn> that way you could still avoid having the same code twice
[22:52] <hannesw> chris: another commit on helma_1_6 branch
[22:52] <hannesw> hope this is it now
[22:52] <jirkap> hm, and one more qustion, not really different. When I have a HopObject, its main_action is accessible only from itself. But when I define another_action() it is accessible even for root. I understand I have to make a method of HopObject out of it but somehow it does not work..
[22:55] <zumbrunn> hannesw: ok, I'll probably do rc3 tomorrow afternoon/night then
[22:55] <zumbrunn> jirkap, not sure what you mean
[22:56] <zumbrunn> that doesn't really make sense
[22:56] <zumbrunn> where do you define the main_action and the another_action in this case?
[22:56] <zumbrunn> inside the same prototype folder?
[22:57] <zumbrunn> which one? HopObject? Root? something else?
[22:59] <jirkap> I have functions.js in Sample prototype folder. Its instance is named 'sample' and is child of root. Now when I make a main_action for 'sample', it is accessible at root/sample/main only. But when I create another_action() in the same file it is accessible even at root/another
[23:00] <jirkap> I probably have some mess here..
[23:00] <zumbrunn> probably :-)
[23:01] <jirkap> :) so there shouldn't be a problem with such a behavior if everything is set properly?
[23:01] <zumbrunn> you could set Root to extend Sample, which would explain why root inherits another_action from sample
[23:02] <zumbrunn> plus if you have a main action defined inside of Root, that would explain what you are describing
[23:02] <jirkap> That might be it! That IS it.
[23:02] <zumbrunn> :-)
[23:03] <jirkap> :) great, thank you very much. good night

 

 

In the channel now:

Logs by date: