I'm an iOS developer, and I haven't tried MacRuby yet, but it appears to be a good alternative to Objective-C. Assuming that MacRuby will be used on iOS devices in the future, perhaps the framework (and project) should be renamed before the v1.0 release. Some alternatives are: * AppleRuby.framework * CoreRuby.framework * HotRuby.framework (if HotCocoa is popular) * Ruby.framework (in Versions/?? subfolder) * RubyBridge.framework * RubyCocoa.framework (in Versions/B subfolder) * RubyFoundation.framework * RubyKit.framework Since you've recently moved to GitHub, and your "MacRuby: The Definitive Guide" book is probably nearing completion, I don't think this is likely to happen. But I thought it was worth suggesting, because choosing to rename after v1.0 (e.g. "iPhone OS 3.x" to "iOS 4") is worse. Cheers. P.S. I had a quick look at the MacRuby source code (commit 17be4634582ac22c418b). Here's a modest patch for "MacRuby.m": -- (id)performRubySelector:(SEL)sel -{ - return [self performRubySelector:sel withArguments:NULL]; -} +- (id)performRubySelector:(SEL)sel +{ + return [self performRubySelector:sel withArguments:NULL count:0]; +}
What, no iRuby? On Apr 3, 2011, at 3:46 AM, Ben Rimmington wrote:
I'm an iOS developer, and I haven't tried MacRuby yet, but it appears to be a good alternative to Objective-C.
Assuming that MacRuby will be used on iOS devices in the future, perhaps the framework (and project) should be renamed before the v1.0 release. Some alternatives are:
* AppleRuby.framework * CoreRuby.framework * HotRuby.framework (if HotCocoa is popular) * Ruby.framework (in Versions/?? subfolder) * RubyBridge.framework * RubyCocoa.framework (in Versions/B subfolder) * RubyFoundation.framework * RubyKit.framework
Since you've recently moved to GitHub, and your "MacRuby: The Definitive Guide" book is probably nearing completion, I don't think this is likely to happen. But I thought it was worth suggesting, because choosing to rename after v1.0 (e.g. "iPhone OS 3.x" to "iOS 4") is worse.
Cheers.
hmm i double checked my calendar to be sure not getting trapped as april fool... :-) --- Bryan Harrison <bryan@bryanharrison.com> schrieb am So, 3.4.2011: Von: Bryan Harrison <bryan@bryanharrison.com> Betreff: Re: [MacRuby-devel] Renaming the MacRuby project An: "MacRuby development discussions." <macruby-devel@lists.macosforge.org> Datum: Sonntag, 3. April, 2011 18:52 Uhr What, no iRuby? On Apr 3, 2011, at 3:46 AM, Ben Rimmington wrote:
I'm an iOS developer, and I haven't tried MacRuby yet, but it appears to be a good alternative to Objective-C.
Assuming that MacRuby will be used on iOS devices in the future, perhaps the framework (and project) should be renamed before the v1.0 release. Some alternatives are:
* AppleRuby.framework * CoreRuby.framework * HotRuby.framework (if HotCocoa is popular) * Ruby.framework (in Versions/?? subfolder) * RubyBridge.framework * RubyCocoa.framework (in Versions/B subfolder) * RubyFoundation.framework * RubyKit.framework
Since you've recently moved to GitHub, and your "MacRuby: The Definitive Guide" book is probably nearing completion, I don't think this is likely to happen. But I thought it was worth suggesting, because choosing to rename after v1.0 (e.g. "iPhone OS 3.x" to "iOS 4") is worse.
Cheers.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
I like the name MacRuby :) NSObject is also still called NSObject although NeXTStep hasn't been around for a long time. - Johannes On Sun, Apr 3, 2011 at 6:52 PM, Bryan Harrison <bryan@bryanharrison.com> wrote:
What, no iRuby?
On Apr 3, 2011, at 3:46 AM, Ben Rimmington wrote:
I'm an iOS developer, and I haven't tried MacRuby yet, but it appears to be a good alternative to Objective-C.
Assuming that MacRuby will be used on iOS devices in the future, perhaps the framework (and project) should be renamed before the v1.0 release. Some alternatives are:
* AppleRuby.framework * CoreRuby.framework * HotRuby.framework (if HotCocoa is popular) * Ruby.framework (in Versions/?? subfolder) * RubyBridge.framework * RubyCocoa.framework (in Versions/B subfolder) * RubyFoundation.framework * RubyKit.framework
Since you've recently moved to GitHub, and your "MacRuby: The Definitive Guide" book is probably nearing completion, I don't think this is likely to happen. But I thought it was worth suggesting, because choosing to rename after v1.0 (e.g. "iPhone OS 3.x" to "iOS 4") is worse.
Cheers.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-- springenwerk.com | github.com/jfahrenkrug | twitter.com/jfahrenkrug Springenwerk Consulting Johannes Fahrenkrug Muehlenredder 21c, 24582 Bordesholm, Germany +49 (0)151 22 634 651
While there is nothing wrong with having this kind of discussion, I don't think we are currently looking into changing the project's name ;) - Matt On Sun, Apr 3, 2011 at 10:33 AM, Johannes Fahrenkrug <jfahrenkrug@gmail.com>wrote:
I like the name MacRuby :) NSObject is also still called NSObject although NeXTStep hasn't been around for a long time.
- Johannes
On Sun, Apr 3, 2011 at 6:52 PM, Bryan Harrison <bryan@bryanharrison.com> wrote:
What, no iRuby?
On Apr 3, 2011, at 3:46 AM, Ben Rimmington wrote:
I'm an iOS developer, and I haven't tried MacRuby yet, but it appears to be a good alternative to Objective-C.
Assuming that MacRuby will be used on iOS devices in the future, perhaps the framework (and project) should be renamed before the v1.0 release. Some alternatives are:
* AppleRuby.framework * CoreRuby.framework * HotRuby.framework (if HotCocoa is popular) * Ruby.framework (in Versions/?? subfolder) * RubyBridge.framework * RubyCocoa.framework (in Versions/B subfolder) * RubyFoundation.framework * RubyKit.framework
Since you've recently moved to GitHub, and your "MacRuby: The Definitive Guide" book is probably nearing completion, I don't think this is likely to happen. But I thought it was worth suggesting, because choosing to rename after v1.0 (e.g. "iPhone OS 3.x" to "iOS 4") is worse.
Cheers.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-- springenwerk.com | github.com/jfahrenkrug | twitter.com/jfahrenkrug
Springenwerk Consulting Johannes Fahrenkrug Muehlenredder 21c, 24582 Bordesholm, Germany +49 (0)151 22 634 651 _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On 3 Apr 2011, at 18:33, Johannes Fahrenkrug wrote:
I like the name MacRuby :) NSObject is also still called NSObject although NeXTStep hasn't been around for a long time.
I don't hate the name MacRuby, but I thought it might be confusing (if someday Ruby becomes the most popular language for writing iOS apps). However, your analogy to the NeXTSTEP frameworks was good. On 3 Apr 2011, at 19:07, Matt Aimonetti wrote:
While there is nothing wrong with having this kind of discussion, I don't think we are currently looking into changing the project's name ;)
Maybe it just takes a while to appreciate the project name (a bit like how the name "iPad" was unpopular at first). P.S. In chapter 5 of "MacRuby: The Definitive Guide", you might be able to use -addObserverForName:object:queue:usingBlock: to simplify your NSNotificationCenter examples. <http://ofps.oreilly.com/titles/9781449380373/ch05.html#_tasks_subprocesses> <http://ofps.oreilly.com/titles/9781449380373/ch05.html#_notifications> For the second example, instead of:
framework 'Foundation'
class NotificationHandler def tea_time(notification) puts "it's tea time!" end end
center = NSNotificationCenter.defaultCenter notification_handler = NotificationHandler.new
center.addObserver( notification_handler, selector: "tea_time:", name: 'tea_time_reminder', object: nil )
center.postNotificationName("tea_time_reminder", object:self)
You might be able to do:
framework 'Foundation'
center = NSNotificationCenter.defaultCenter
observer = center.addObserverForName( "tea_time_reminder", object: nil queue: nil usingBlock: Proc.new{|notification| puts "it's tea time!" } )
center.postNotificationName("tea_time_reminder", object:self)
Am 03.04.2011 um 22:00 schrieb Ben Rimmington:
On 3 Apr 2011, at 18:33, Johannes Fahrenkrug wrote:
I like the name MacRuby :) NSObject is also still called NSObject although NeXTStep hasn't been around for a long time.
I don't hate the name MacRuby, but I thought it might be confusing
you mean like the UI in UIApplication? anyways, nice trolling, though a few days late.
Thanks for the observer recommendations, back when I wrote these examples, we were not yet supporting blocks. I should probably show both examples now that blocks are properly supported. - Matt On Sun, Apr 3, 2011 at 1:00 PM, Ben Rimmington <benrimmington@me.com> wrote:
On 3 Apr 2011, at 18:33, Johannes Fahrenkrug wrote:
I like the name MacRuby :) NSObject is also still called NSObject although NeXTStep hasn't been around for a long time.
I don't hate the name MacRuby, but I thought it might be confusing (if someday Ruby becomes the most popular language for writing iOS apps). However, your analogy to the NeXTSTEP frameworks was good.
On 3 Apr 2011, at 19:07, Matt Aimonetti wrote:
While there is nothing wrong with having this kind of discussion, I don't think we are currently looking into changing the project's name ;)
Maybe it just takes a while to appreciate the project name (a bit like how the name "iPad" was unpopular at first).
P.S. In chapter 5 of "MacRuby: The Definitive Guide", you might be able to use -addObserverForName:object:queue:usingBlock: to simplify your NSNotificationCenter examples.
< http://ofps.oreilly.com/titles/9781449380373/ch05.html#_tasks_subprocesses
<http://ofps.oreilly.com/titles/9781449380373/ch05.html#_notifications>
For the second example, instead of:
framework 'Foundation'
class NotificationHandler def tea_time(notification) puts "it's tea time!" end end
center = NSNotificationCenter.defaultCenter notification_handler = NotificationHandler.new
center.addObserver( notification_handler, selector: "tea_time:", name: 'tea_time_reminder', object: nil )
center.postNotificationName("tea_time_reminder", object:self)
You might be able to do:
framework 'Foundation'
center = NSNotificationCenter.defaultCenter
observer = center.addObserverForName( "tea_time_reminder", object: nil queue: nil usingBlock: Proc.new{|notification| puts "it's tea time!" } )
center.postNotificationName("tea_time_reminder", object:self)
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (7)
-
Ben Rimmington
-
Bryan Harrison
-
denny trebbin
-
Henry Maddocks
-
Johannes Fahrenkrug
-
Matt Aimonetti
-
Thomas R. Koll