Joseph Carter wrote:
<snip>
> 2. Create twilight/baselib. FIXME: better name?
> A place to put mathlib, strlib, console, cvar, cmd, bspfile, common,
> and all of the other things which were classically used by both the
> engine and the tools. The code here should be built into a static
> library for the engine to link, but we should not discount making it a
> dynamic library in the future.
I hate libs, you even ranted about how evil QF's libs were, so why do
you propose this?
> 3. Create twilight/renderer.
> Here we'll place all of the shared stuff necessary for the client's
> rendering. Starting with all of the gl_* files, more or less. They
> should lose their gl_ prefix probably when they move. I'm not sold yet
> on the idea that that vid_sdl belongs in here, but I'm not really sure
> where to put it really.
If the renderer is to stay GL only, then vid_sdl has no reason to go
into renderer, the renderer would be implied to be GL.
> 4. Create twilight/sound.
> Currently, there is not much to Project Twilight in the form of sound.
> Only a handfull of files. But if we add support for more kinds of
> music such as mp3, Ogg Vorbis, etc, I believe it will make more sense
> to give these things a place of their own.
Hmm, seems excessive, but ok.
> These directories should be as free of outside dependencies as possible.
> Clearly most of them will depend on "baselib" and just about all of them
> will depend on SDL for certain. Headers for each module should move to
> that module. That'll mean more include paths in the engine, but it also
> means that the modules themselves will be more bite-sized. The exception
> to this is of course baselib, whose headers should live in the shared
> include directory we have now, possibly a subdirectory of that even
> waiting for the day that these headers will actually be installed on the
> system.
Make baselib depend on SDL? then you don't need to manually specify SDL
:)
I don't like having multiple include paths either, but I'd tolerate it.
> The result should look like this:
>
> twilight
> |-- baselib (or whatever)
> |-- debian
> |-- doc
> | `-- olddoc
> |-- gamecode
> | `-- progs
> |-- include
> | `-- Twilight
> |-- nq
> |-- qw
> |-- renderer
> |-- sound
> `-- tools
>
> The last thing I want to do, and probably not until after our second
> release, is move the twilight directory to twilight-classic so we can move
> on, break compatibility, and do cool things. Obviously that's way off in
> the distance, but I thought I'd mention it since I have already made the
> Debian package scripts work that way.
>
> Comments? Suggestions? Thwacks for really lame design choices?
The only way to break compatibility is to make a twilight mod (or more
likely TC), and then develop for that mod, changing it to fit the
changing engine.
> --
> Joseph Carter <[EMAIL PROTECTED]> Free software developer
>
> <elmo> unclean: err, the admin team do not control the archive, that's the
> ftp cabal
> <elmo> get your cabals right, damn it :-P
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
--
LordHavoc
Senior Editor for http://www.gamevisions.com
A member of the Brotherhood of The Axe game clan.
Author of DarkPlaces Quake1 engine and mod (
http://darkplaces.gamevisions.com/ )
"War does not prove who is right, it proves who is left." - Unknown
_______________________________________________
twilight-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/twilight-devel
