Tree

GaryBartlett

Hi Folks,

I am in the process of building a replica of my editable HTML Help-like application, eGuide Creator. It looks, to ordinary users, like HTML Help (e.g the Aware IM Help System), but Editors are able to add, edit and relocate topics on the tree on the left of the page.

I have got the topic hierarchy working as I would like and am now trying to build the tree in the left-hand panel. I'm looking to create something like the tree in the Documents example, but comprising merely a set of topics with sets and generations of child topics, beneath them.

Is anyone able to offer me advice in the form of a set of steps I can take to do so?

I don't want a single root node, with all of the root topics under it. I want to see just the root topics (without the root node), with their children under them.
I want to be able to click on a tree node and have the panel alongside, containing HTML, updated accordingly (presenting the content of the topic clicked): in editable form for editors and in uneditable form for ordinary users.

Thanks very much - battling to find a starting point!

Gary

GaryBartlett

I should have said that I have watched the Tree Video on the Aware IM site and been able to create a tree on a tab within the Topic form.

Currently this tree:

Provides Edit and Delete options on it;s context menu.
Allows dragging and dropping (although the first drag creates two copies of the topic as children of the topic its dropped on.
The barren topics (no children) seem to carry a plus (expand) icon next to them although they don't have children - as with the Trees video. Does anyone have a solution to that problem?

Of course, this tree reflects only the children of the relevant topic - which, I suspect is where the need to create the equivalent of a DocumentsRoot Folder, from the Documents example, comes in. A this point it starts becoming confusing, which is why I'm looking for a set of steps to follow - or some advice...

Thanks very much!

Gary

kenlyle

Can I get a bump on this? I have similar questions...I don't really need a Root either, but want to start from a list of BOs and allow drill down and then open the selected item, similar to the Document Management sample app.

Like the OP, I have seen adding a tree to a form section in the video, but want to create one standalone in a tab, and use it for object selection in another panel.

aware_support

At the moment you have to have an object that stores all initial references of a tree in some reference attribute (Root). You display some form of this object with the Root being the only attribute shown. See Document Management sample app