Re: [Proposal] On-the-fly NIB localization
Re: [Proposal] On-the-fly NIB localization
- Subject: Re: [Proposal] On-the-fly NIB localization
- From: John Stiles <email@hidden>
- Date: Tue, 16 Nov 2004 10:45:46 -0800
On Nov 16, 2004, at 9:39 AM, mmalcolm crawford wrote:
Is any of this noticeable to the user? Probably not directly. I'd
argue, though, that in this case working with the frameworks and not
unnecessarily increasing resource usage are in general Good Things...
as are reducing the code maintenance burden and scope for error.
Well, if you're in my position and need to support two platforms, you
try to share as much code and data as possible. I can't "work within
the framework" if 95% of my customers don't have that framework! :)
Currently my strings are in an XML file, they work fine, there's no
perceptible overhead whatsoever, and I think there isn't any
lower-maintenance approach that maintains portability.
If you're going to write an OS X-only app, I'd use the nib approach for
localized strings. But I'm sure a very large number of developers
prefer solutions that work everywhere, because they need to minimize
the amount of OS-specific code and data that they have to deal with.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden