[1089] in Coldmud discussion meeting
[COLD] Re: [ColdCore] Pruning the Object Heirarchy
daemon@ATHENA.MIT.EDU (Sat Sep 21 12:48:26 1996
)
Date: Sat, 21 Sep 1996 10:40:46 -0600 (MDT)
From: Brandon Gillespie <brandon@glacier.cold.org>
To: Miroslav Silovic <silovic@srce.hr>
cc: coldstuff@cold.org
In-Reply-To: <199609182355.BAA28467@regoc.srce.hr>
> > $help_index_driver -- urg, what to do? need to change driver help
> > $help_node_driver_... -- ^^^^ (Miro?)
>
> @edit <helpnode> to edit it. You can change node's index by calling
> node.[add|del]_index (or something, check the methods on $help_node.
We had a discussion a little while back as to where the authoritative
source is for the driver docs. The reason I dont like using what we have
in db right now is because it didnt all convert correctly. Because I
dont know what to treat as the source I havnt updated any of the docs
since about patch 8. What I think I'm going to do is take the stuff on
the web, strip the HTML and just do my own formatting that a perl script
can frob to HTML or CML. comments/concerns?
> > $tree --\ Jeff Artifacts, what do to with $tree, nix?
> > $tree_4 --/ still used? $help_node_* used to use it..
>
> @grep for these, I didn't like this code. :) Nothing seems to use it now.
I didnt like the idea of $tree's either, seemed redudnant. They are nixed.
> > $heart/$scheduler -- review, I would like to make $scheduler native
>
> $scheduler is outdated and buggy. My suggestion is to use dictionary instead
> of heap for event table.
I thought somebody rewrote $scheduler already? As for its future, we
should just make a $scheduler native module.
> > $read_parser -- rename/move in heirarchy, its not an official
> > 'parser', it parses from the connection not the
> > user's parser stack
>
> I'd move this to $login_connection ?
No, I think it can be used on many connection types.. (ponder)
Other than that, I'm going to start @dump'ing some stuff for a contrib
archive, It'll likely be non-functional but can be used for reference.
-Brandon