[3:21]<flinja> Can you map more then one HopObject to a "view"? For example, in http://helma.org/docs/tutorial/collections/, _children is mapped to Person prototype, when these subnodes are processed in /addressbook/Root/main.hac. What if you wanted to also map other hopobjects to the root? [21:30]<flinja> Can you map more then one HopObject to a "view"? For example, in http://helma.org/docs/tutorial/collections/, _children is mapped to Person prototype, when these subnodes are processed in /addressbook/Root/main.hac. What if you wanted to also map other hopobjects to the root? [22:09]<zumbrunn> flinja, a prototype can have several collections [22:10]<flinja> collections of attributes? [22:10]<zumbrunn> in addition to the default one (defined as _children) [22:11]<zumbrunn> do you want objects of different prototypes in a default collection that is mapped against a relational db? [22:12]<zumbrunn> I've never seen that done, I don't think [22:12]<zumbrunn> but maybe I'm wrong and it is possible [22:13]<zumbrunn> you could ask on the helma-user mailing list and see if someone can explain this in more details [22:13]<zumbrunn> http://helma.org/docs/guide/mapping/collections/ [22:13]<flinja> Yes, so in the tutorial, we map the address name the the default view. What if I had other objects/prototypes I wanted on that page? For example, for a blog I would route blog entries prototype, and maybe a another prototype for links, for example. [22:14]<flinja> I think I'll do that, ask in the mailing list. [22:14]<zumbrunn> in the first example on that page you see how you can define additional collections [22:15]<zumbrunn> (prop4 in this case) [22:15]<flinja> I'll take a look. Thank you! [22:15]<zumbrunn> but then they are not part of the list you get using myhopj.list() [22:16]<zumbrunn> they would be at myhopj.prop4.list() [22:16]<flinja> ok [22:16]<zumbrunn> usually, that's what you'd want , though