Multimodel still will (usually) have a central model, so I'd put those there.
The non-model ones are a bit more complicated, is it more of a query (like an advanced search) that doesn't write info to the db? or more like a complicated multimodel or multiple models but only a handful of fields for each? I'd probably go with making a tools model and using lifecycles/web_methods as appropriate for the actions/forms. Depending on the tools, might even be possible to make a web editable form. I did something similar where I wanted to be able to render a tag with a given attribute set. The table had a name, tag, and serialized tag attributes. So, to be able to render a static tag (for a server side include elsewhere), all I had to do was create a new instance with the right values. -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
