On 24/02/2009, at 9:51 PM, "[email protected]" <[email protected] > wrote:
> > Can I just see if I understand these responses? > > With a function stack, it seems like it would be up to the > experimenter to reconceptualize their experimental procedure into a > series of production rules. If thats right, then I think it sinks this > idea, since it's unlikely that this target group will grok this. But > please let me know if I'm misunderstanding. > > The cooperative threading sounds interesting, I found fibra, but > couldn't find examples of tasks/tasklets. Why not simply have a list of actions defined by the experimenter, which your program uses to drive the event/state model required by pyglet? You could even parse this list of actions from a text file, in effect creating a mini language for your program to interpret. Alex. > > Rob > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
