Comments for developer.casgrain.com

Comment on Display std::wstring in Xcode using a Data Formatter by slh

slh — Tue, 20 Jul 2010 01:46:36 +0000

Has anyone ever gotten this to work in an iphone project? Works fine for me within wcharTest in the wchardataformatter project, but in my iphone projects, I see only blank summary fields where I should see the formatted wchar_t data. Any ideas appreciated.

Comment on About Box by Laurent Lecaille

Laurent Lecaille — Wed, 23 Jun 2010 09:53:48 +0000

Bonjour,

Je vous envoie ce mail pour en quelques sorte vous remerciez.
A partager votre passion et votre enthousiasme pour le monde Cocoa, vous m’avez donner l’envie et le courage de faire ma propre application iPhone qui est sorti depuis hier.

Elle s’appelle iPrelude, j’espère qu’elle vous plaira.
Merci de transmettre se message a Philippe Guitard.

Et surtout continuez comme ça !!!

Amicalement
Laurent Lecaille

Comment on Automatically localize your nibs when building by Philippe

Philippe — Sat, 22 May 2010 00:23:16 +0000

@Ferris Gabriel Sure, you could only have one nib and translate everything in strings. That's kind of what Wil Shipley does. Or you could have no nib too. It's really up to you to weigh the pros and the cons. I like nibs, other people, not so much.

Comment on Automatically localize your nibs when building by Ferris Gabriel

Ferris Gabriel — Tue, 18 May 2010 15:46:37 +0000

@Philippe
Oh perfect, I see what you’re saying.
Now, with that, and if all UI texts are set programmatically, then we should be OK just using genstrings (and not have to use IBTOOL), is this correct? For a small app, do you know if there’ll be any noticeable runtime performance degradation for the app always having to translate from string files, as oppose to pre-localizing the XIBs with IBTOOL). I’m trying to weigh the effort with IBTOOL and increase in bundle size incurred with additional XIBs (one for each language), against using genstrings alone? (sorry if this is too simple, this is our first iPhone project and therefore our first localization.)

Comment on Automatically localize your nibs when building by Philippe

Philippe — Tue, 18 May 2010 03:32:45 +0000

Ferris Gabriel :
What do you mean by hard-coded keys? I am assuming you mean that all user-visible labels, should be programmatically set rather than with IB, correct?

What I mean is, don't depend on the return value of NSLocalizedString. It is common to see "NSLocalizedString(@"Some sentence that needs to be localized", nil)" where you should be using "NSLocalizedString(@"SentenceLabel", nil)" and in your strings file, you have the translation between "SentenceLabel" = "Some sentence that needs to be localized" for every supported language. That way, English is just a language, not a key.

Comment on Automatically localize your nibs when building by Ferris Gabriel

Ferris Gabriel — Tue, 18 May 2010 02:20:09 +0000

Can you expand on this statement: “This technique is important even if you have nib files, because most of your strings are probably in .strings files already. Don’t use hard-coded strings for anything that is user-visible. Only use hard-coded keys.”

I do have XIBs, but would like to only use Localizable.strings files using genstrings if possible, and more importantly, only one XIB for all languages (as apposed to one for each). What do you mean by hard-coded keys? I am assuming you mean that all user-visible labels, should be programmatically set rather than with IB, correct? If that’s do-able I’d like to use this approach and avoid using IBTOOL altogether. Am I missing anything? Are their drawbacks to this approach?

Comment on Eight guys, four weeks, one dream by Philippe

Philippe — Sun, 09 May 2010 19:04:29 +0000

@MJ Ray It's not officially a co-op, as in the legal entity. Right now we're a group of like-minded individuals that like Cocoa programming in the Ottawa, Canada region.

Comment on Eight guys, four weeks, one dream by MJ Ray

MJ Ray — Fri, 07 May 2010 15:47:33 +0000

Why is “co-op” in quote marks? Is Cocoaminded a co-op or not? I see it’s not using a dotCoop domain.

If it is a co-op, please let me know: I’d love to network with other software co-op members.

Comment on Display std::wstring in Xcode using a Data Formatter by Philippe

Philippe — Sat, 17 Apr 2010 04:34:20 +0000

@rpv For C++ you want ",cpp" files. Your files are ".ccpp", which Xcode doesn't know how to compile.

Comment on Display std::wstring in Xcode using a Data Formatter by rpv

rpv — Fri, 16 Apr 2010 14:25:10 +0000

should i ignore those warnings?

[WARN]warning: no rule to process file ‘$(PROJECT_DIR)/myCustomFormatter.ccpp’ of type text for architecture x86_64
[WARN]warning: no rule to process file ‘$(PROJECT_DIR)/myCustomFormatter.ccpp’ of type text for architecture i386
[WARN]warning: no rule to process file ‘$(PROJECT_DIR)/myCustomFormatter.ccpp’ of type text for architecture ppc