> yes, we know, we are preparing a documentation. 
<br/>Great! Is the WIP publicly available (e.g. in one of our Pillar/GitHub repos)? Btw. the class comments are reeeally great! I'm only talking about documenting design rationale.
<br/><br/>&gt; We���ve implemented a lot of examples. please have a look.
<br/>Thanks - I have and they are also great. But AFAICT it's impossible to tell from the examples /why/ e.g. we went from Morphs owning their step actions to block-based steps registered with a scheduler that is universal to all worlds. I have a doubt about that because one use case I've had in Morphic is to speed up time in a world to see what happens e.g. in 10 minutes from now, but #schedule hard-codes the reference to the BlUniverse singleton.

	
	
	<div class="signature" style="margin-top:1em;color:#666666;font-size:11px;">
				Cheers,
<br/>Sean
			</div>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://forum.world.st/Bloc-Roadmap-tp4816171p4816769.html">Re: Bloc Roadmap</a><br/>
Sent from the <a href="http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html">Pharo Smalltalk Developers mailing list archive</a> at Nabble.com.<br/>