Okay - a rough outline:
A question has many potential answers. Each answer can lead to a number of
questions. An example would be:
+Would you like Coffee or Tea? [Question]
- Coffee [Answer]
+De-Caff or Regular? [Question]
-De-Caff [Answer]
-Regular [Answer]
+Moccona or Nescafe [Question]
-Tea [Answer]
I can't see that recursive nesting of two trees should be a problem given
that we can pass in the "parentid" (which incidentally I need to figure out
how to specify differently), the problem at the moment is that I can't see a
way to pass the current "id" to the alternate model's tree as a "parentid".
I'd eventually like to include links to add "children", or edit/remove the
current node. That functionality further complicates things in that it will
involve manipulating records in the intermediary tables as well as the leaf
level. Nesting sure messes with your frame of reference!
First things first though, I need to get a tree out somehow..
On Sat, Jul 31, 2010 at 12:43 PM, Chuck Benedict
<[email protected]>wrote:
> Give me a use case and I'll be glad to add my $0.02
>
> Sent from my iPhone
>
> On Jul 30, 2010, at 5:02 AM, Simeon <[email protected]> wrote:
>
> The learning curve gets steep in a hurry around these parts!
>
> The "Hierarchies - Using acts_as_tree" recipe deals nicely with a self
> referencing model (category belongs to category) but it takes on the
> context of the model containing the call. I have yet to find reference
> to a similar solution involving multiple (nested) models.
>
> Is it possible, and how would I go about starting to figure it out?
>
> Thanks for your thoughts!
>
>
--
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.
