[MacRuby-devel] [MacRuby] #274: [HotCocoa] Button images

[MacRuby]

#274: [HotCocoa] Button images
---------------------------------+------------------------------------------
 Reporter:  dj2@…                |       Owner:  lsansonetti@…        
     Type:  enhancement          |      Status:  new                  
 Priority:  minor                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by eloy.de.enige@…):

 Hi,

 I just closed #273 which does the same thing as this patch does for
 #image=. That is, the setImage method is already available as #image=.

 About the other two I have my reservations. My question with changes like
 these is: where lies the limit of what will be mapped. As I have
 understood from Rich, the point is to make the “harder” to use Cocoa APIs
 more accessible, in a more Ruby-ish way.

 But is writing “alternate_image=” vs “alternateImage=” really necessary
 and helpful? I'd be inclined to say no. Sooner or later people will have
 to deal with the existing API, so there's not much point in trying to
 completely mask the fact that the dev is using Cocoa.

 However, where the limits should lie is not written in stone somewhere
 afaik, so maybe that's a good idea to discuss?

 My 2$

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/274#comment:1>
MacRuby <http://macruby.org/>