On Mar 8, 2009, at 10:46 AM, Brian Stevens wrote:

>
> 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 others.

Thanks.

>> 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.

Sorry for the confusion here as I already have a CG Demo that is  
freely available on request that makes full use of Core Graphics so I  
am aware that we can use it. Possibly though there may be some who  
have not tried it yet. The lucky ones are those of you just starting  
out with FB and FBtoC and not having to unlearn what most of use old  
timers went through.

>> 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.

My original thoughts here were to implement CG into the FB editor and  
all screen displays of FB so that the FB application itself if fully  
CG for that fully professional look as in Xcode.

>> 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.

Once again it is probably priorities and not at the top. In the long  
run it is about performance and final code that should come first. As  
many of us have found out trying to bring old code up to new spec's  
its something akin to trying to make steak out of hamburger. I look at  
code I wrote 20 years ago and just say "what was I thinking" but then  
again we didn't even have long functions back then or long if's, etc.  
It seems at time that it would just be easier to start from scratch  
knowing what we know now.

Thanks again for the reply.

Max Taylor
The MaxClass Guy