Re: [Alephmodular-devel] High Level Modules

[Br'fin <br...@ma...>]

On Sunday, December 29, 2002, at 09:40  PM, Chris Pickel wrote:

> On Sunday, December 29, 2002, at 07:39  PM, Br'fin wrote:
>> What sort of independent pieces would people like to see?
>
> The first target, in my opinion, should be the definitions. I've got a=20=

> list of them somewhere... got it. Bottom of the message, it's fairly=20=

> long. The most important ones to modularize are the ones in:
> - device.cpp
> - fades.cpp
> - game_window.cpp
> - item_definitions.cpp
> - media_definitions.cpp
> - scenery_definitions.cpp
> - sound_definitions.cpp
>
> Interestingly enough, the number comes out to 7. But more importantly,=20=

> modularizing these would mimic the functionality of MML in A1. These=20=

> are smaller things, and should be fairly easy to split off, while=20
> other, hairier things (rendering, networking) might take some more=20
> time and effort for less of an immediate return.

A very good list. I'm trying to think of what we should call this group=20=

of ... extended physics. Scenario? Personality? (Do you play a Map=20
Scenario ala E:MR within AM with the Personality of M2?) I agree that=20
they should have their own module. Something that might interface a bit=20=

more strongly with the other modules than any other module is allowed=20
to.

An extended example would include not just monster definitions, but=20
also provide the monster control functions. (Hah! *MY* Scenario=20
implements a segmented worm as a monster!)

I'd really like a decent name for this!

> Another thing that should be modularized quickly, and hopefully almost=20=

> as easily, would be the network game types. I'm not entirely sure how=20=

> to go about it myself =96 we'd need to split apart the switch-cases =
that=20
> are in most of the network_games.cpp functions in such a way that it=20=

> handled a variable number of game types.

I'm not sure about modularized quickly. Mainly because we don't have=20
working netplay yet. I don't want to break the netcode before someone=20
is actually in a position to neatly fix it back up :)

It's for this reason that I've not done any of the cleanup steps on any=20=

of the network* files.

-Jeremy Parsons