[Pharo-project] drawString: aString from: firstIndex to: lastIndex at: aPoint font: fontOrNil color: c
bschwab at anest.ufl.edu
Thu Feb 10 17:24:19 CET 2011
I knew I had read that somewhere: thanks for the link. Still, the question of performance lurks. Passing all of those parameters and setting all of the colors/pens/etc. for EVERY operation might be inefficient. Just asking...
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Henrik Johansen [henrik.s.johansen at veloxit.no]
Sent: Thursday, February 10, 2011 7:52 AM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] drawString: aString from: firstIndex to: lastIndex at: aPoint font: fontOrNil color: c
On Feb 10, 2011, at 1:24 55PM, Schwab,Wilhelm K wrote:
This reminds me of something: I have long been concerned about possible speed penalties that might result from Morphic's accepting colors and other drawing tools as arguments rather than having a canvas hold them as state that can be set once and used many times.
It's probably nothing, but it always struck me as very different from the way Dolphin does things. Of course, Object Arts' focus on Windows could have simply have led them to follow along with the platform's design; there is nothing to say they would have created a context if none had existed.
Just something to think about.
The rationale is explained in http://stephane.ducasse.free.fr/FreeBooks/CollectiveNBlueBook/morphic.final.pdf
in the section "Adding appearance" on page 6 - 7.
Personally, this is one of the things I don't dislike about Morphic compared to other canvas-based systems :)
More information about the Pharo-project