Should all object managers have active groups?

[GoogleCodeExporter]

As of r394, dotsTheDrawablesManager uses an active group to do drawing in 
batches.  The upcoming dotsTheComputablesManager will also use an active group 
with a lot of similar code.  I'd like to factor this out to 
dotsAllObjectManagers.

This would mean a small API change, like activeDrawavles->activeObjects.

This would also mean that dotsThePlayablesManager and dotsTheQueryablesManager 
would also have active groups, which they might never use.  But the might!  For 
example, dotsTheQueryablesManager might want to do some updating of data in 
batches, as opposed to requiring individual queryables to do their own updating.

Original issue reported on code.google.com by Benjamin.Heasly on 27 Sep 2010 at 10:10

[GoogleCodeExporter]

This relates to issue 30, about whether dotsTheQueryablesManager should 
implement topsConcurrent.  The concurrent behavior could act on the active 
group.

I'm leaning towards implementing this after November2010.

Original comment by Benjamin.Heasly on 27 Sep 2010 at 10:15

• Changed state: Accepted

[GoogleCodeExporter]

As of version 1.0, there will be no object managers, so this is not a useful 
issue.

Original comment by Benjamin.Heasly on 8 Jan 2012 at 9:59

• Changed state: WontFix