On Monday 01 December 2008 17:05:58 Fiona Burrows wrote:
> Thank you! I knew there would be a term for it. :)
> Those libraries seem interesting - especially Dramatis. But neither of
> them seem as well suited for games as mine as I have lots of
> game-specific things like collision detection going
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Knapp
> Sent: Monday, December 01, 2008 10:54 AM
> To: pygame-users@seul.org
> Subject: Re: [pygame] Pygame-Fenix - Using generators as game objects
>
> On Mon, Dec 1, 2008 at
On Mon, Dec 1, 2008 at 7:49 PM, Noah Kantrowitz <[EMAIL PROTECTED]> wrote:
> Panda is more of a hybrid of an actor system and a lot of interlinked state
> machines (each actor has an FSM, and there are others that are global). I do
> actually like this model a lot, just not the Panda API.
>
> --N
[EMAIL PROTECTED]
> On Behalf Of Knapp
> Sent: Monday, December 01, 2008 10:33 AM
> To: pygame-users@seul.org
> Subject: Re: [pygame] Pygame-Fenix - Using generators as game objects
>
> On Mon, Dec 1, 2008 at 6:05 PM, Fiona Burrows
> <[EMAIL PROTECTED]> wrote:
> >
> &
On Mon, Dec 1, 2008 at 6:05 PM, Fiona Burrows <[EMAIL PROTECTED]> wrote:
>
>
> Noah Kantrowitz wrote:
>
> If you want to look up information about this, the general term is
> "actor-based" programming. Existing libraries (neither of which ever seemed
> that great) include PARLEY and Dramatis. Stack
Noah Kantrowitz wrote:
If you want to look up information about this, the general term is
"actor-based" programming. Existing libraries (neither of which ever
seemed that great) include PARLEY and Dramatis. Stackless tasklets are
also a very nice way to handle this.
Thank you! I knew ther
If you want to look up information about this, the general term is
"actor-based" programming. Existing libraries (neither of which ever
seemed that great) include PARLEY and Dramatis. Stackless tasklets are
also a very nice way to handle this.
--Noah
On Dec 1, 2008, at 7:54 AM, Fiona Burro
Dan Krol wrote:
The way I would do it is this:
def begin(self):
while True:
for x in range(0,5):
#state 0 stuff
yield
for x in range(0,3):
#state 1 stuff
yield
for x in range(0,7):
#state 2 stuff
yie
This is something I've thought of as well, but slightly differently.
It started with me working on a game framework where your "guy" would
have an __init__ for loading the images, and a FrameAction that gets
called by the game loop. The game loop of the framework would handle
all of the callbacks.
