Honestly, that's not relevant :). If you want to be able to create a
CFStringRef from a Pascal string at runtime, use
CFStringCreateWithPascalString().
Indeed, thanks, following this I could apple I should be looking for
and I see that I can easely set utf-8 strings to my controls =)
But your framework should still
allow actual CFStringRef objects to be passed around directly, as
they are the premier string representation on Mac OS X.
CFStringRef isn't cross-platform. i.e. has no meaning on windows or on
linux, or on windows ce, and the framework is cross-platform.
Your framework should just as easily allow strings to come from
strings files or to load UI elements from a nib if you want to be
able to deal with localization in a sane way. In theory you could
reinvent the wheel by defining your own serialized UI format, but
then you have to create your own tools etc - why do that to yourself?
I don't follow. The tools are already created, I'm just improving the
carbon backend because we are porting a large Delphi software to
Macintosh which requires more features then the current implementation
provides.
--
Felipe Monteiro de Carvalho
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
