Helma Logo
main list history

Version 3 by zumbrunn on 22. January 2008, 17:51

1Over the past days, I did some experimenting *experimenting with the JOMP patch for Rhino Rhino|e4xd and jhino - experimental soft-coding scaffold using JOMP* and the mapping of additional filename extensions to HopObject properties. I probably took it a bit to far and made the list of supported file suffixes to long, even introducing duplicates, but I would like to propose supporting additional filename based conventions for Helma 1.7.

Version 2 by zumbrunn on 21. January 2008, 16:44

Version 1 by zumbrunn on 21. January 2008, 16:44

1Over the past days, I did some experimenting with the JOMP patch for Rhino and the mapping of additional filename extensions to HopObject properties. I probably took it a bit to far and made the list of supported file suffixes to long, even introducing duplicates, but I would like to propose supporting additional filename based conventions for Helma 1.7.
3Here is what I added for my experiments:
4
5foo.macro --> becomes a hobj.foo_macro function with "params" as first argument
6foo.get --> becomes a hobj.foo_action_get function
7foo.post --> becomes a hobj.foo_action_post function
8foo.put --> becomes a hobj.foo_action_put function
9foo.delete --> becomes a hobj.foo_action_delete function
10foo.e4x --> becomes a hobj.foo_e4x xml object
11foo.json --> becomes a hobj.foo_json js object
12
13Then I also needed a mapping that would not be generally useful, but only interesting in the context of my experiments:
14
15foo.control --> becomes a hobj.foo_control function with "view" as first argument
16
17And on top of all that, I added some duplicates:
18
19foo.view --> the same as foo.skin
20foo.action --> the same as foo.hac
21
22The helma patch that resulted in:
23
24<% this.attachments %>
25
26Maybe instead of adding direct built-in support for additional filename conventions to Helma, we could instead add functionality that would make it easy to script/configure such additional conventions as needed.