First let me request that you add "Re:" in front of your replies because if you put the subject as it is , it creates a new thread in forum.world.st which makes it hard for me to keep up with your replies. The water drop does not know about the sea , because it can become one with it. There is no separation. Here there is a clear separation, subtopics. Plus isn't this the essense of OOP to keep things in hierarchy ? I am not saying that a HelpTopic should not be independent from other HelpTopics. Some kind of documentation can stand on its own. But when subtopic message is used I would assume that it would respect the hierarchy. Afterall you have already a subtopics instance variable with a getter. It looks like I would have to subclass. I was just wondering if there is any specific reason why there should not be one. As always I am open to suggestions :) Torsten Bergmann wrote
The help tool uses a treeMorph to display all topics in a tree like fashing, and since each submorph in the tree is tied to a HelpTopic I could fetch the hierarchical structure of HelpTopic from there, but the question is , is this a good idea ?
The navigation is UI related anyway, so there is nothing that would speak against this.
I left out the "parent" or "owner" explicitly in my design, why should the water drop know the sea ;)
It is IMHO more flexible and makes it easier (as you have seen with the wiki pragma).
Thx T.
-- View this message in context: http://forum.world.st/Lets-Talk-about-Pharo-Help-tool-tp4708926p4708948.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.