Re: [Pyobjc-dev] Need design input for method names
Brought to you by:
ronaldoussoren
From: Orestis M. <or...@or...> - 2009-03-30 12:28:11
|
It occurs to me (having started to do Obj-C development this past month full-time) that a major source of annoyance is not the verboseness of the bridge, but the lack of a Pythonic API to Cocoa, which can be very verbose itself. One approach taken from the Ruby guys is HotCocoa (http://www.macruby.org/trac/wiki/HotCocoa ) that aims to provide simplified wrappers for common Cocoa use-cases. For example, rather than doing: win = NSWindow.alloc.initWithContentRect [10,20,300,300], :styleMask => ( NSTitledWindowMask | NSClosableWindowMask | NSMiniaturizableWindowMask | NSResizableWindowMask) you do: win = window :frame => [10,20,300,300] However, I know that the PyObjC maintainers don't want to do this since it has to be manually maintained. Perhaps then this can be another project? Maybe the fact that as bbum said there hasn't been an acceptable solution for 15 years now is in an indicator of wrong scope. Even if an acceptable method name convention can be reached, the fact that to create a usual NSWindow you need to pass in 4 flags won't go away. Orestis -- or...@or... http://orestis.gr/ On 29 Mar 2009, at 19:21, Ronald Oussoren wrote: > > On 29 Mar, 2009, at 13:11, Bill Bumgarner wrote: >>> >> >> This again? :) >> >> Here is a good starting point for one of the more signal-oriented >> discussions on this subject (it has come up once every 6 to 24 months >> since PyObjC was created in '94): > > I know, but the current syntax really annoys me. > > Ronald > ------------------------------------------------------------------------------ > _______________________________________________ > Pyobjc-dev mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev |