yes, we know, we are preparing a documentation. 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.
Weâve implemented a lot of examples. please have a look. 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.
----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Roadmap-tp4816171p4816769.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
yes, we know, we are preparing a documentation. 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. We did them twice :) And some of them should be improved.
To doc in on github pharo progress. Now I started to document the classes so that after I can generate part of the doc :)
Weâve implemented a lot of examples. please have a look. 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.
Good question alain will answer. Continue to ask so that we can extract the information from his mind.
Cheers, Sean
------------------------------------------------------------------------ View this message in context: Re: Bloc Roadmap <http://forum.world.st/Bloc-Roadmap-tp4816171p4816769.html> Sent from the Pharo Smalltalk Developers mailing list archive <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at Nabble.com.
yes, we know, we are preparing a documentation. 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. We did them twice :) I'm probably looking in the wrong place. Do you have links?
To doc in on github pharo progress. This? https://github.com/SquareBracketAssociates/PharoInProgress/blob/master/Bloc/...
Continue to ask so that we can extract the information from his mind. Okay! :)
----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Roadmap-tp4816171p4816788.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
sean if you can collect the answers to your question and put them into the pillar doc :), this can help. Stef Le 1/4/15 23:29, Sean P. DeNigris a écrit :
yes, we know, we are preparing a documentation. 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. We did them twice :) I'm probably looking in the wrong place. Do you have links?
To doc in on github pharo progress. This? https://github.com/SquareBracketAssociates/PharoInProgress/blob/master/Bloc/...
Continue to ask so that we can extract the information from his mind. Okay! :) Cheers, Sean
------------------------------------------------------------------------ View this message in context: Re: Bloc Roadmap <http://forum.world.st/Bloc-Roadmap-tp4816171p4816788.html> Sent from the Pharo Smalltalk Developers mailing list archive <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at Nabble.com.
if you can collect the answers to your question and put them into the pillar doc :), this can help. Aww⦠you guessed my plan ;)
----- Cheers, Sean -- View this message in context: http://forum.world.st/Bloc-Roadmap-tp4816171p4817050.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 01 Apr 2015, at 22:15, Sean P. DeNigris <sean@clipperadams.com> wrote:
yes, we know, we are preparing a documentation. 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.
https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bloc <https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Bloc> see blocCore.pillar work in progress...
Weâve implemented a lot of examples. please have a look. 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.
Bloc use Alarms, Stepping will be removed. Each space has its own queue of alarms but nothing prevent a morph to have its own queue. Now, steps and alarms are not limited to use blocks, one can use message send also. Cheers Alain
Cheers, Sean
View this message in context: Re: Bloc Roadmap <http://forum.world.st/Bloc-Roadmap-tp4816171p4816769.html> Sent from the Pharo Smalltalk Developers mailing list archive <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at Nabble.com.
Weâve implemented a lot of examples. please have a look. 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.
Morphic uses two global queues (hold by the world state) one for stepping and the other for the alarms. bloc have only one global queue for stepping and alarms. basically the same kind of implementation as in morph. and again, any class can declare and manage its own AlarmQueues. :) Alain
participants (3)
-
Alain Plantec -
Sean P. DeNigris -
stepharo