[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

6866: [MUD-Dev] Re: DBMS in MU*'s

[Full Header] [Plain Text]
From: quzah@geocities.com
Newsgroups: nu.kanga.list.mud-dev
Date: Wed, 12 Aug 1998 03:59:16 -0700
References: [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] <-newest
Organization: Kanga.Nu
To:             	mud-dev@kanga.nu
Subject:        	[MUD-Dev] Re: DBMS in MU*'s 
Date sent:      	Tue, 11 Aug 1998 16:14:22 -0700
From:           	J C Lawrence <claw@under.engr.sgi.com>
Send reply to:  	mud-dev@kanga.nu

> On Sun, 19 Jul 1998 20:46:15 +0200 
> Asmodai <Jeroen> wrote:
> 
> > At 19:37 19-07-98 , you wrote:
> 
> Please use full attributions that identify the original poster.
> Attributing to "you" is not good enough.  See:
> 
>   http://www.kanga.nu/~petidomo/lists/mud-dev/index.html#rules
> 
> and rule #5 in particular.
> 
> 
> > rock, glass, velvet, wood and paper and assign values about the
> > subject being able to break, torn apart etc...
> 
> I'd suggest an analogue of Java interfaces would be a much more native
> approach.  There's a fairly decent article in this month's C++ Report
> (might have been CUJ, but I don't think so and the mags are at home)
> on implementing interfaces under C++ which is worth reading.
> 
> > This would eliminate multiple tables and generally provide a good
> > addition to the MU*.
> 
> I see horrors when you start to get:
> 
>   volcanic_glass, silicate_glass, pyrex, lead_crytal, etc.

I was thinking of making a structure/class for the element type;
something along the lines of this:

element name,
element number,
element wpcc //weight per cubic centimeter, or rather, density.
element fragility_bits, // bit_0 may be flamability, bit_1 ...
element color,

Naturally, I haven't fully developed this idea. Most of my ideas
end up like this [I have a notebook or two full of them, and by
god, some day I'm going to implement them all!] I get ideas faster
than I can produce results. It's very sad... (Sad that I'm not a
brilliant speed demon who never needs sleep, even sadder that I'm
not getting payed to play around with all of my ideas... ;)

Anyway,I guess in the above example, the current object in question
would get a 'glass' element attached, which would then be modified
by the creator to suit their needs. (Change the color to blue, or
something.) This way, when created, you just drop in a similar type
of element, and modify the parts that you don't like. Oh well, it's
just a thought.

-Q-
(If this formatting is botched, I was trying out a different mail
reader, and so I'm not sure how this outputs. I am switching back
to my old one, so if this is screwed, don't worry, the rest won't
be. Sorry if it is.)


> 
> -- 
> J C Lawrence                               Internet: claw@null.net
> (Contractor)                               Internet: coder@ibm.net
> ---------(*)                     Internet: claw@under.engr.sgi.com
> ...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...
> 
> -- 
> MUD-Dev: Advancing an unrealised future.