helma.org/wiki/Basic Scaffolding

Version 7

maks — Fri, 25 Jan 2008 05:49:34 +0100

40	Then copy the provided hop action files (.hac file attachment attachments at the bottom of this page), actions actions, HopObject.js and skins into your apps HopObject prototype folder.
41	Copy the attached htmlpage.skin into your apps Global folder.
46	etc.
48	While I have generic create.skin, edit.skin, etc. in HopObject, if you put a more customised one in any of your prototypes it will "override" my generic ones in the HopObject prototype. Likewise you can create your own edit function that will be called instead of the generic one in HopObject.

maks — Fri, 25 Jan 2008 05:41:48 +0100

5	==== <strong>Ensure each Prototype defines a _children collection of its own type===<=/strong>
11	==== <strong>Create mountpoints for each Prototype you want to access directly ===directly<=/strong>
17	====<strong> copy Ensure there is a skin named itemList available for each prototype in order to render each HopObject item in the provided hop action files (list skin.hac file attachement at the bottom of this page), actions and skins into your HopObject prototype folder</strong>
18	eg.
19	User/listItem.skin
20
21	<tr>
22	<td>
23	<% this.id %>
24	</td>
25	<td>
26	<% this.username %>
27	</td>
28	<% this.href name="editDelete" %>
29	</tr>
30
31
32	and HopObject/skins/editDelete.skin has something like:
33	<td>
34	<a href="<% this.href %>edit" >EDIT</a>
35	</td>
36	<td>
37	<a href="<% this.href %>delete" >DELETE</a>
38	</td>
19	You can now use Then copy the default create, listprovided hop action files (.hac file attachment at the bottom of this page), etc actions with urls like:and skins into your HopObject prototype folder
21	You can now use the default create, list, etc. actions with urls like:
22
27	Note: I expect that there is a skin named itemList available for each prototype in order to render each HopObject item in the list skin.
28

maks — Fri, 25 Jan 2008 05:32:22 +0100

1	While I prefer Helma over RubyOnRailRubyOnRails, I have been influenced by reading up about Rails and the convenience of their scaffolding system.
5	*==== Ensure each Prototype defines a _children collection of its own type:====
9	_children = collection(User)
11	*==== Create mountpoints for each Prototype you want to access directly: directly ====
15	users = mountPoint(User)
17	*==== copy the provided hop action files (.hac file attachement at the bottom of this page), actions and skins into your HopObject prototype folder
19	You can now use the default create, list list, etc actions with urls like:
24	While I have generic create.skin, edit.skin, etc etc. in HopObject, if you can just put a more customised one in any of your prototypesprototypes it will "override" my generic ones in the HopObject prototype.
25
26	Note: I expect that there is a skin named itemList available for each prototype in order to render each HopObject item in the list skin.
27
27	Note: make sure you add the jala.ListRender.js as one of your applications repositories, eg:
28
29	myapp.repository.2 = modules/jala/code/ListRenderer.js
30

maks — Fri, 25 Jan 2008 00:34:12 +0100

17	* copy the provided js fileshop action files (.hac file attachement at the bottom of this page), actions and skins into your HopObject prototype folder

zumbrunn — Tue, 24 Jul 2007 12:45:35 +0200

27	<% this.attachments %>

maks — Tue, 24 Jul 2007 04:00:40 +0200

19	You can now use the default listcreate, list actions with urls like:
20
21	http://localhost:8080/myapp/users/create
22	http://localhost:8080/myapp/users/list
23
24	While I have generic create.skin, edit.skin, etc in HopObject, you can just put a more customised one in any of your prototypes.
25	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.
26
27

maks — Fri, 13 Jul 2007 04:19:07 +0200

1	While I prefer Helma over RubyOnRail, I have been influenced by reading up about Rails and the convenience of their scaffolding system.
2	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.
3	The conventions are:
4	* Ensure each Prototype defines a _children collection of its own type:
5	eg.
6	Root/User/type.properties
7
8	_children = collection(User)
9
10	* Create mountpoints for each Prototype you want to access directly:
11	eg.
12	Root/type.properties
13
14	users = mountPoint(User)
15
16	* copy the provided js files, actions and skins into your HopObject prototype folder
17
18	You can now use the default list,