Re: Non-Drilldown pages & header.php3

[Jason Pincin <chardros@linuxkb.org>]

There should be a corresponding object for everything.

But the point is well taken... what if we don't want to display the drill
path?  I was tossing that idea around myself... the drill-down path
display at the top has caused a lot of complications for me.  I was
thinking about doing away with it completely and re-implimenting it a
different way at a later date.... when I had less concerns.

But - as it stands, I can't think of a situation that wouldn't have a
corresponding object in the tree.  Remember - most things should be
classified as ACTIONS to an object.

Example:

User tools, articcle submits, all that DOES have a position in the tree.
You people NEED to impliment these things AS ACTIONS.  Not stand-alone
pages.  They NEED to be called from render.php3.

So - Article submits could be called from op=1.3.9&as=7.5.SubmitArticle or
something.  Maybe OID 9 is "Apache" - so what your doing here is adding an
article to the Apache group... who's full path is 1.3.9.

UserTools - would work the same way... if I'm a user and I want to edit my
properties... and my ObjectID is 578, and I'm in the standard users group
who's OID is 10... then my full path is 1.10.578.  So I'm performing an
EDIT action on that Object.  So it may look like:
op=1.10.578&as=7.5.Edit

Understand?

I may not have made this clear in the last meeting... but we need to think
as EVERY page we develop as an ACTION that can occur to an Object.  

The only exception is the LBF.  Because it's not part of the object
tree... and it's completely seperate for the most part... 

On Sun, Oct 24, 1999 at 10:24:01AM -0700, Aaron Turner wrote:
> 
> Jason,
> 
> I know other people are interested in this too, so...
> 
> Everyone wants to use the standard header.php3 for the top of their pages
> (User-Tools, Article Submits, LBF, etc).  However, since there is no
> correlating object in KBObjects, when you include header.php3 you get a
> bunch of errors.  See:
> 
> http://dev.linuxkb.org:81/lbf/companylist
> 
> for an example of the errors.
> 
> So, what can we do about this?  Should we create static header.php3's for
> each section or create KBObjects?  Your call.
> 
> --
> Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
> Linux Knowledge Base Organization  http://linuxkb.org/
> Because world domination requires quality open documentation.

-- 
Jason
http://vodka.linuxkb.org/~chardros