I’ve looked into doing this, because I think it would be useful for a lot of ASOC users. However, the problem is in the definition: + (id)stringWithFormat:(NSString *)format, …
That ellipsis means the method takes a variable number of arguments, and the way that works is complicated. It will take a much better objC programmer than me to tackle this.
ObjC categories are not accessible from ASOC.
That’s one of the reasons I always recommend to spend the time to learn Objective-C.
There are none of the silly restrictions and coercion problems you have in ASOC.
AppleScript is the perfect solution for inter-application communication but for an stand-alone app
you should use the “adult” language
Er… what about the Intel Xeon assembler ? THIS would be really adult !
Anyway, I’m maybe not a good example for ASOC programming, because I’m coding a stand-alone application, which pilots no other app – the Finder was the last one, and it’s gone – and has some very specific features which were originally developed in the native MacOS language (pascal).
But the aficionados at MacScripters (including you, Stefan) have always solved my problems so far, with 98% ASOC solutions. I have to admit that ASOC is a main entrance to Cocoa, not just a peephole. And for the coercion problem, well, you learn you live with it, the compiler gives us no “wrong type” warnings so far, but the debug panel helps.
I know there is nothing that the “real thing” but if I try ObjC it won’t be for this app, because I’m too far with it.