search

uludaggonul / snow-dots

Automatically exported from code.google.com/p/snow-dots
0 stars 0 forks source link

"current group" object mode? #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It seems like a lot of classes are going to use the concept of a current
group.  This could be anything, but it's likely to be the name of a
topsBlockTree (e.g. trial, intertrial, etc.).

Maybe the way to go would be to let objects join a currentGroup object mode
that they could respond to.  They could define a set.currentGroup to do any
necessary preparation/changeover operations.

This could be an answer to tower of psych issue 6
"http://code.google.com/p/tower-of-psych/issues/detail?id=6", about
topsFunctionLoop inheriting a run mode from a topsBlockTree.  It would be
more general--the tun mode would correspond to the "currentGroup", which
other objects would respond to as well.

Original issue reported on code.google.com by Benjamin.Heasly on 11 Dec 2009 at 6:38

GoogleCodeExporter commented 8 years ago 
This should come up more when Josh and I get to developing a task.  There are 
hardware concerns to be solved before then...

Original comment by Benjamin.Heasly on 16 Feb 2010 at 11:01

GoogleCodeExporter commented 8 years ago 
The topsRunnable family solves this to some extent, since it gives explicit 
structure to the running of a program.  The current group is more of a current 
location in the graph of runnables.

Since each location in the graph has a start- and finishFevalable, setting a 
currentGroup is possible.  But I'm going to leave this as a user's choice as 
opposed to part of the kool-aid of Snow Dots.

Original comment by Benjamin.Heasly on 3 Aug 2010 at 6:00