• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa et al as HCI usability problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa et al as HCI usability problem


  • Subject: Re: Cocoa et al as HCI usability problem
  • From: Peter Duniho <email@hidden>
  • Date: Mon, 19 May 2008 13:36:17 -0700

Date: Mon, 19 May 2008 20:31:02 +0200
From: Andreas Mayer <email@hidden>

This is (part of) a method that handles an AppleScript command send to
the application.
One possible argument is the color to be used for display:

- (id)handleDisplayCommand:(NSScriptCommand *)command
{
	NSDictionary *args = [command evaluatedArguments];
	NSString *colorName = [args objectForKey:@"color"];
	NSColor *color;

	...

	if (colorName) {
		SEL colorSelector = NSSelectorFromString([colorName
stringByAppendingString:@"Color"]);
		if ([[NSColor class] respondsToSelector:colorSelector]) {
			color = objc_msgSend([NSColor class], colorSelector);
		}
	}

	...
}

This way you may use any color name that NSColor supports.

In .NET, you'd just call Color.FromName().

More generally, as before, any code that is simply checking "respondsToSelector" and then calling the specific selector, that can easily be implemented in C# or Java using reflection (assuming there's not a better, more idiomatic approach in those languages, as often there would be). And situations when one would need this are generally far and few between (i.e. not common enough to dictate an entire language paradigm), especially when a class has the foresight to implement that kind of functionality already.

I appreciate the example. It's certainly reasonably elegant and to the point, and it's more "real world" than some of the other ones (bridging Cocoa to another language? yeah, right...a) it's not like you can't interface between languages with other languages, and b) this is not the kind of thing one is going to see in general application code). But not the sort of compelling "we really need the language to be this way otherwise it just doesn't work" example I was hoping for.

Thanks,
Pete
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Cocoa et al as HCI usability problem
      • From: Andreas Mayer <email@hidden>
    • Re: Cocoa et al as HCI usability problem
      • From: Andy Lee <email@hidden>
    • Re: Cocoa et al as HCI usability problem
      • From: Jean-Daniel Dupas <email@hidden>
    • Re: Cocoa et al as HCI usability problem
      • From: ben syverson <email@hidden>
    • Re: Cocoa et al as HCI usability problem
      • From: Jean-Daniel Dupas <email@hidden>
  • Prev by Date: Re: Cocoa et al as HCI usability problem
  • Next by Date: Re: Cocoa et al as HCI usability problem
  • Previous by thread: Re: Cocoa et al as HCI usability problem
  • Next by thread: Re: Cocoa et al as HCI usability problem
  • Index(es):
    • Date
    • Thread