Helma Logo
main list history
previous version  overview  next version

Version 3 by zumbrunn on 24. July 2007, 12:45

While I prefer Helma over RubyOnRail, I have been influenced by reading up about Rails and the convenience of their scaffolding system.
So I've created a basic work-alike system (but not a straight port!) using actions/skins for HopObject that depends on following some coding conventions.

The conventions are:
* Ensure each Prototype defines a _children collection of its own type:
eg.
Root/User/type.properties

_children = collection(User)

* Create mountpoints for each Prototype you want to access directly:
eg.
Root/type.properties

users = mountPoint(User)

* copy the provided js files, actions and skins into your HopObject prototype folder

You can now use the default create, list actions with urls like:

http://localhost:8080/myapp/users/create 
http://localhost:8080/myapp/users/list

While I have generic create.skin, edit.skin, etc in HopObject, you can just put a more customised one in any of your prototypes.
Likewise the generic processForm() in HopObject that is called by create.hac and edit.hac can be over-ridden by a custom one if you need to do special processing on form data for any particular prototype and finally you can of course create custom create,edit,list, delete actions in each prototype to completely change this default processing.

<% this.attachments %>

     removed
     added