[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [kidsgames] Generic adventure game engine



On Tue, 18 Jul 2000, Steve Baker wrote:
> Into which of those catagories would you put:
> 
>    The GIMP.

CleverSource.

>    Ghostscript

Extendable by hard-core geeks.

>    Tcsh
does it really matter ?

>    TuxRacer

I don't know.

>    KDE
A visual tool for making Menus doesn't mean extendable.

>    NQC
what's this ?

>    LeoCAD
I don't know.

> 
> ...heck - we'll toss in one of mine too:
> 
>    TuxKart.

I don't know.

> 
> Woah! Gnome and Emacs are both OpenSource. If you are going to remove
> from the catagory of 'OpenSource' everything that you find to be
> 'CleverSource' then of course what's left is junk.

That's part of my point. There's a lot of junk, only the "recent"
superb libs like Mesa, SDL and others make a junk look like 
art work.

> 
> Nobody said you have to make things re-usable at the microscopic
> level within a program. 

Simply reusable.

> If you do, it's generally a waste of
> effort.  If I want (say) a routine to draw a dodecahedron - it's
> much easier to write a new one than it is to trawl through the
> entire web looking for one - only to find that it doesn't work
> *exactly* how I want it to.

You're saying that reinventing the wheel is better that get some
ways of organizing libraries of algorithms and libraries. Very
clever! Very geek-ly!

> 
> Code re-use in the context of such a wide-spread community is
> at the level of entire code libraries.  Hence, GIMP gave us
> GTK, TuxAQFH/TuxKart gave us PLIB.

OOP --> reusable objects, otherwise we're not programming in OO.

> 
> I'll talk about my software as an example - only because I
> happen to know it well:
> 
>   However, of those 44,000 lines of code, 40,000 are in the
>   PLIB library suite - which is written in classical OOP
>   style (albeit in C++) and which is now in use in over 100
>   OpenSource projects.

Very good for PLIB library!

>   giving a total code-reuse of better than 99% for the entire
>   TuxKart package.  That's good by ANYONE'S standards.

I've never said anything about TuxKart, in fact, I didn't know
it existed.

> FlightGear - for example - re-uses PLIB and exports SimGear
> and TerraGear which are the parts of FlightGear that might
> well be useful to (respectively) other simulation projects
> and other terrain/geographic-information-systems.

Good

> 
> PrettyPoly - re-uses PLIB, FLTK, Python and will export
> an editing core (PEC) that can be incorporated into games
> as the basis an in-game level design tool.
> 
Good

> Code re-use is alive and well - it just doesn't operate
> at the microscopic level because it simply isn't all that
> USEFUL at that level. 

Good
> I want to re-use modules of tens
> of thousands of lines of code - not silly little 20 line
> classes from some tiny Java program.

You're wrong about this. 
 

Regards/Saludos
Manolo
www.ctv.es/USERS/irmina    /TeEncontreX.html   /texpython.htm
/pyttex.htm /cruo/cruolinux.htm ICQ:77697936 (sirve el ICQ para algo?)

  Fried's 1st Rule: Increased automation of clerical function invariably results in increased operational costs.


-
kidsgames@smluc.org  -- To get off this list send "unsubscribe kidsgames"
in the body of a message to majordomo@smluc.org