[Pharo4] Weekend Project 1: Cleanup Low-Level animation code
Hi, Now with holidays coming⦠maybe someone wants to do a small Pharo related Project with impact on the future? Here is suggestion 1. Context: cleanup graphics. (so e.g. one could replace the canvas later). Details ====== Morphic has some very arcane code for animating moving morphs around that bypasses layers. DisplayObject has these methods: follow:while: follow:while:bitsBehind:startingLoc: slideFrom:to:nSteps:delay: slideWithFirstFrom:to:nSteps:delay: displayOnPort:at:rule: They are used by morphic for some not really important animation that for sure can be directly done by moving the morphs as morphs around. Bypassing and directly using low level (not even Canvas level) functionality is for sure not needed. On the Morph level the users are: slideBackToFormerSituation: vanishAfterSlidingTo:event: animationForMoveSuccess: What to do? -> rewrite the morphic level code to just move the morphs around. -> delete all the code from DisplayObject -> review âGrafPortâ usage, as this might have been the last client. Marcus
Yes marcus may be we should add that description to pharo roadmaps on github. I like to document design problems that I encounter but cannot fix fast. Stef On 24/7/14 10:28, Marcus Denker wrote:
Hi,
Now with holidays coming⦠maybe someone wants to do a small Pharo related Project with impact on the future?
Here is suggestion 1.
Context: cleanup graphics. (so e.g. one could replace the canvas later).
Details ====== Morphic has some very arcane code for animating moving morphs around that bypasses layers.
DisplayObject has these methods:
follow:while: follow:while:bitsBehind:startingLoc: slideFrom:to:nSteps:delay: slideWithFirstFrom:to:nSteps:delay: displayOnPort:at:rule:
They are used by morphic for some not really important animation that for sure can be directly done by moving the morphs as morphs around. Bypassing and directly using low level (not even Canvas level) functionality is for sure not needed.
On the Morph level the users are:
slideBackToFormerSituation: vanishAfterSlidingTo:event: animationForMoveSuccess:
What to do?
-> rewrite the morphic level code to just move the morphs around. -> delete all the code from DisplayObject -> review âGrafPortâ usage, as this might have been the last client.
Marcus
Marcus I pushed it to the git pharo-workingRoadmaps Stef On 24/7/14 11:04, stepharo wrote:
Yes marcus may be we should add that description to pharo roadmaps on github. I like to document design problems that I encounter but cannot fix fast.
Stef
On 24/7/14 10:28, Marcus Denker wrote:
Hi,
Now with holidays coming⦠maybe someone wants to do a small Pharo related Project with impact on the future?
Here is suggestion 1.
Context: cleanup graphics. (so e.g. one could replace the canvas later).
Details ====== Morphic has some very arcane code for animating moving morphs around that bypasses layers.
DisplayObject has these methods:
follow:while: follow:while:bitsBehind:startingLoc: slideFrom:to:nSteps:delay: slideWithFirstFrom:to:nSteps:delay: displayOnPort:at:rule:
They are used by morphic for some not really important animation that for sure can be directly done by moving the morphs as morphs around. Bypassing and directly using low level (not even Canvas level) functionality is for sure not needed.
On the Morph level the users are:
slideBackToFormerSituation: vanishAfterSlidingTo:event: animationForMoveSuccess:
What to do?
-> rewrite the morphic level code to just move the morphs around. -> delete all the code from DisplayObject -> review âGrafPortâ usage, as this might have been the last client.
Marcus
participants (2)
-
Marcus Denker -
stepharo