[futurebasic] Re: [FB] Cheap CoreGraphics text

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : March 2009 : Group Archive : Group : All Groups

From: Brian Stevens <bstevens33@...>
Date: Sun, 8 Mar 2009 10:46:57 -0700
On Mar 8, 2009, at 9:58 AM, Max Taylor wrote:

> If this is deprecated as of 10.4 is it wise to make use of it as a  
> quick fix that we know may break in the future?

Deprecation should always be considered but deprecated calls can still  
be used. It behooves the programmer to understand the consequences as  
they apply ( or not ) to their project. Each programmer will need to  
make their own decision based on the project. Listers with shorter- 
term goals and program life expectancies might not be as concerned as  

> Is CGText a possiblity in the near future for FB.
CG is possible today in an FB program by making the toolbox calls, so  
I assume this is a request for the FB statements like Text, Print etc  
to use CG instead of QuickDraw?  If that is so, I don't believe anyone  
has investigated how the CG calls map to FB statements yet. Clearly,  
much is possible ( to answer your question ), but everything is a  
matter of time, resources and motivation.

> It would be really nice to see the text in an FB edit window look as  
> nice as that in Xcode.
EUTCs are modern, anti-aliased text fields and are possible with  
Appearance Button commands or nibs. Clearly, EUTCs have limitations,  
but they do look good and don't use QuickDraw. Even though I might  
guess, please elaborate a *little* more about this "FB edit window"  
and what commands you have in mind to upgrade.

> Would also make FB look very professional and modern.
Ah, you're right, the FB Editor's  text rendering uses Text Services  
Manager ( TSM ) and not CG.

Brian S