[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Making things hard on me...
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