[8:16]<hannesw> has anybody looked at the new skin/macro features in helma ng? [8:16]<hannesw> if anybody is interested, I could give a quick summary. [8:24]<hannesw> looking at sinatra url routing: http://www.sinatrarb.com/book.html#routes [8:24]<hannesw> some nice things in there [8:24]<hannesw> for one thing, i wonder if we should do routing by HTTP method. [8:51]<simono> i'll checkout new skin/macro features after noon [9:28]<simono> aha! further proof that merging post/get into data is evil http://dev.helma.org/trac/helma/changeset/9671 [13:09]<hannesw> simono: in the case of a rhino continuation, handling get and post requests in the same action is actually a requirement... [13:10]<hannesw> but it's a corner case. [13:11]<hannesw> Recently, I'm wondering if jetty continuations aka asynchronous request handling isn't going to be the more important technique. [13:11]<hannesw> (it doesn't really solve the same problem as rhino continuations...) [13:12]<simono> i see. i thought that in the continuation example all the params are GET [13:13]<simono> i posted my don't-merge-POST/GET on the wikipage anyways [13:14]<simono> "handling get and post request in the same action" .. thats not what i meant. i just don't like that they are merged into res.data [13:16]<simono> i would force people to think about wether POST or GET is appropriate [13:42]<hannesw> simono: I agree! [13:43]<simono> it's a minor issue, i just saw lots of res.data in this commit [14:01]<simono> skin extending works the same for helma1 & ng? i want to try it, found only the changeset-docu [14:39]<hannesw> simono: what commit contains res.data? [14:39]<hannesw> skin extending is different in helma 1 and ng [14:40]<hannesw> helma 1 uses <% .extends foo %>, helma ng without the dot. [14:40]<simono> i see [15:21]<fresco> are there any examples around of fetching remote html pages from within a Helma NG app? adding env.js and jquery would be a bonus...