On 14 November 2013 19:47, Stéphane Ducasse <stephane.ducasse@inria.fr>wrote:
Hi jeff
We should rewrite the drawnOn: method as drawAthensOn: and we should simplify the logic because often it is well⦠terrible. Now have a look at the way the tutorial Morph is done SceneView something because it shows the logic. I know that there is a morph to render morph in athens.
Yes, there is AthensSceneView (read its class comment, its really easy to use)
for transition , i implemented a special morph, AthensWrapMorph which wraps (as its name says) its children morphs and forces them to be rendered by athens (the child morphs will never receive #drawOn: but #drawOnAthensCanvas: instead ). Like that you can start using athens for current state of morphic and later, when whole World will be rendered by athens, you will no longer will need to use wrapper, so you will just throw it out from hierarchy without changing your existing code.
Stef
On Thu, Nov 14, 2013 at 5:56 PM, kilon alios <kilon.alios@gmail.com>wrote:
Athens is a vector graphics library, its not a GUI API. Athens will not give you buttons, menus, drop down lists and GUI elements. It will give you however the means to draw all those things and much more.
As far as I understand it, Athens is a vector graphics library that will eventually replace BitBlt for rendering Morphs in Pharo. For a time, there will be some things rendered with Athens and some things rendered with BitBlt. How do I make the transition from BitBlt rendering to Athens rendering?
Cheers,
Jeff
-- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick
-- Best regards, Igor Stasenko.