--- Begin Message ---
> 
> But how to drive it? e.g. simulate events

ok, so we agree here. Bloc is done in that perspective.
For now, you have to implement your own BlocSpace with an adequate 
#processEvents method, 
your can also implement your own main loop manager (polymorphic with 
BlMainLoopManager).

> 
> 
> Pharo Smalltalk Users mailing list wrote
>> but your code does not make sense regarding how Bloc is designed
>> you can have one and only one **active** BlocSpace at a time.
> 
> I understand from a Pharo perspective that one is only expected to have one
> *real* space at a time which is receiving hardware events and such, but what
> prevents us from simulating Spaces?! If there is a SpaceElement, and
> Elements can be placed in the World, the principle of uniformity encourages
> that a SpaceElement can be placed there like any other.

yes, your right. I had that idea in mind. The only problem we have today 
is that the current implementation of damages repairing makes the assumption 
that a SpaceElement is at 0@0. (need to review BlSimpleRedrawer for that).

> 
> 
> Pharo Smalltalk Users mailing list wrote
>> imagine that a BlocSpace is a Pharo image.
>> Making your code working would mean that we would be 
>> able to run a Pharo image within a Pharo image.
> 
> Exactly, like the VM simulator! Sign me up! This was the level of uniformity
> and explorability that I always wished in Morphic.

:)
ok, so not infeasible but we are not there today.
Do not forget that Bloc is currently implemented by a very small team.
lets do it step by step.

Cheers
Alain

> 
> 
> 
> -----
> Cheers,
> Sean
> --
> View this message in context: 
> http://forum.world.st/Bloc-Space-within-a-Space-tp4877474p4877733.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
> 



--- End Message ---

Reply via email to