Re: Making things hard on me...

[Aaron Turner <aturner@linuxkb.org>]

Hmmm.  Seems that we've been down this road before.  The problem seems to
me that this breaks the concept of drilling down.  How will you deal with
a parent with 5 children, and only two should have the article?  Will an
article be inherited from great-grandfather, to grandfather, to parent?

On Thu, 26 Aug 1999, Jason Pincin wrote:

> OK - 
> 
> Here is the current PAIN in my arse.
> 
> EVERY object EXCEPT Articles & External documentation can only have one
> parent.  I don't like that.  I hate it.  I've been coding circles around
> that issue - but my life would be easier if I could say:  ALL objects have
> ONE parent.
> 
> Does that make me a bad person?
> 
> Does anyone have any other ideas?  I'm getting a headache racking my brain
> against this issue.  
> 
> Am I out of line when I say:  If an article affects two differnet
> categories or applications, it should be linked above those categories or
> applications?  Not in each one seperatly?
> 
> Someone please help the thought process here - so that I know it's worth
> all the extra time to figure out ways around it if what I'm saying doesn't
> make sense.
> 
> But I feel that if we adhere to that rule, and place articles where they
> make sense... as well as design interfaces that allow very accurate
> tracking... such as using "Related Areas" and such things... that single
> parents for everything may make sense.  
> 
> Again - I need everyone's input on this.  
> 
> Jason
> 

--
Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
Linux Knowledge Base Organization  http://linuxkb.org/
Because world domination requires quality open documentation.