December 2012 - MacRuby-devel - lists.macosforge.org

Re: [MacRuby-devel] Problem with a window controller
by Jean-Denis MUYS 07 Mar '13

07 Mar '13

On 7 déc. 2012, at 19:48:39, david kramf <dakr.012(a)gmail.com> wrote: > > Message: 1 > Date: Fri, 7 Dec 2012 19:48:39 +0200 > From: david kramf <dakr.012(a)gmail.com> > To: "MacRuby development discussions." > <macruby-devel(a)lists.macosforge.org> > Subject: Re: [MacRuby-devel] Problem with a window controller > Message-ID: <1F1681C7-9DE6-4971-8D17-722F5EC630CA(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hi Bob, > "As you become more familiar with IB, you will probably do more initialization of objects in IB and less in MacRuby. Nib file expansion instantiates objects and then makes calls to initialize the objects using the same methods that you are using to initialize objects in MacRuby. Actually, in a large application, it would difficult to hook up all of the outlets without using IB." > > From my modest acquaintance with MacRuby that is not exactly the case since when the NIB instantiates an NSWindowController object , it does not call "initialize" Cocoa, whether accessed from Ruby, Python, Objective-C or any language, uses the Cocoa initialization patterns. It's unrealistic to assume the framework patterns to change when you change the client language. > ,as defined in Ruby , but calls "awakeFromNib". It does, but caveat: awakeFromNib is *not* an initialization method, even though it is often used as such. I was bitten before. The correct initialization method to use for Nib files is initWithCoder:. What's the difference, says you (and me)? Behold: awakeFromNib can be called several times in the lifetime of an object. This is no big deals for most initializations, but becomes a major issue in others. In my case, I was registering for notifications in awakeFromNib. Since I was registered several times, I got the notifications multiple times, and since I only unsubscribed once in dealloc, my app would crash. Many cases when awakeFromNib is called more than once are programming errors, but not all. And since there *is* a real initializer, I recommend using it. So in that case why is there an awakeFromNib method at all? It is because at initWithCoder: time, IB outlets are not yet loaded and are all nil. So awakeFromNib is meant to for initialization code that configures outlet. So here is a recipe: 1- Does you initialization code requires IB outlets to be alive? If not, override initWithCoder: 2- If so, put it in awakeFromNib 3- Does that awakeFromNib initialization code need to be called once only? if so, make it conditional on it having been already be called. 4- Optional: assert that awakeFromNib was not called before, and if that assert fires, investigate whether the case is legitimate or due to a bug in your code. > Only when you instantiate your controller from the code itself , you get your "initialize"method called. That is a bonus you just can be happy to have due to the deep integration of MacRuby in the Objective-C runtime system. There is no reason to assume that bonus to expand to objects created by the framework. > I know I still have a lot of practicing on IB. What I find disturbing ,is that when I do something with IB I cannot see the code created to accommodate my actions ( maybe because I only work in MacRuby and not Objective-C?). No. This is simply because there **no code created**. At all. IB does't generate code. And lest I forget: Interface Builder is not a code generation tool. IB instantiates and populates objects, and then serializes them to disk. Those objects are then simply deserialized from disk in your app. At no point ever is any code generated. Therefore, there is no "code created to accommodate your actions" for you to see. Even in Objective-C. Best regards, Jean-Denis

3 2

A neat little discovery: MacRuby + ImageMagick
by John Labovitz 17 Dec '12

17 Dec '12

I've been writing some personal tools for processing photographic images (film scans, if you must know). For most of it, I've been using Ruby 1.9 and the ImageMagick library, which has a very rich toolset of image-manipulation functions that are fairly easy to program using the RMagick gem that hooks up to the ImageMagick core engine. (Note: *not* running ImageMagick via sub-shells.) However, these are all batch tools (run from the command line). When I needed a tool with a GUI, I used MacRuby, and then got very frustrated trying to get Cocoa to be as functional as ImageMagick. To start with, there's the confusing mess of NSImage vs. CGImage vs. CIImage, etc. I found that Cocoa's great for doing things it's good at, but once you start driving off the road, you run into boulders. Anyway, this morning I realized I could glue the two together, simply by installing the RMagick gem in MacRuby! I always assumed that would break. But nope, it works fine. (I've installed ImageMagick using Homebrew, BTW.) For example, here's my Cocoa-only code for loading an image from a file into a CIImage: ci_image = CIImage.imageWithContentsOfURL(NSURL.fileURLWithPath(path)) and here's the new code with ImageMagick/RMagick: im_image_list = Magick::Image.read(path) # do some ImageMagick magic here! im_image = im_image_list.first data = im_image.to_blob.to_data ci_image = CIImage.imageWithData(data) Obviously, that's more code (though I've separated it to be a bit more readable). And it probably involves one or two copies of the image data, more than is needed. And doesn't lend itself to CIFilter-like realtime processing. But the point is that now I can process an image using ImageMagick, and display it using Cocoa, all in the same Ruby process! --John PS: This doesn't address packaging. These are my own tools, and so I'm just writing them as simple executables -- I'm not even building application bundles. Obviously if one was to ship an app using ImageMagick internally, there'd be some work to package it into the bundle.

1 0

Another Cocoa issue
by david kramf 14 Dec '12

14 Dec '12

Hello, In the following code I analyze a textView , split it to lines , try to build a Model object from each line , and if build failed I want to color that line in red. I use setColor:range , but once called this method colors my entire view ( also previous lines ) in red. Can someone tell me what I do wrong? Thanks, David Kramf def textView(textView,doCommandBySelector:sel) puts "#{sel.to_s}" return false if sel.to_s != "insertNewline:" puts " in doCommandBySelector selector is #{sel}" @newline = true enum = @textView.string.lines(seperaotr=$/) @location = 0 enum.each_with_index do |l,i| puts "location is #{@location}" words = l.split line = Line.new(words[0],words[1]) @lines[i] = line if @lines[i] != line red = NSColor.redColor range = NSMakeRange((a)location,l.length) puts "#{range.location}-#{range.length}" @textView.setTextColor(red,range) if line.rule == nil @location = @location + l.length end false end

1 0

NSPoint and CGPoint issue
by david kramf 13 Dec '12

13 Dec '12

Hello, I am trying to create an NSPoint object so I can call setFrameOrigin but I get in response a CGPoint object . When I pass the CGPoint to setFrameOrigin , it crashes. How do I make NSMakePoint making an NSPoint object and not a CGPoint object. Thank you for your help, David Kramf def initLabel(h) @label = NSTextField.alloc.initWithFrame(CGRectMake(0,0,250, 45)) @label.setStringValue(h) @label.drawsBackground = false @label.bezeled = false @label.font = NSFont.fontWithName("Arial", size:45.0) @label.editable = false puts "class of label is #{(a)label.class}" width = (@window.contentView.frameSize.width/2.0)-(@label.frameSize.width/2.0) height = (@window.contentView.frameSize.height/2.0)-(@label.frameSize.height/2.0) puts "width is #{width} heght is #{height}" origin = NSMakePoint(width,height) puts "class of origin is #{origin.class}" @label.setFrameOrigin(origin) end class of label is NSTextField width is 75.0 heght is 77.5 class of origin is CGPoint 2012-12-09 18:33:13.525 two[3836:503] /Users/davidkramf/Library/Developer/Xcode/DerivedData/two-gdovgltwrnzjfbfpizcbgrudvizf/Build/Products/Debug/two.app/Contents/Resources/MyController.rb:34:in `initLabel': undefined method `ÔøØÔæøÔæºÔøØÔæøÔæº' for #<MyController:0x4011a6080> (NoMethodError) from /Users/davidkramf/Library/Developer/Xcode/DerivedData/two-gdovgltwrnzjfbfpizcbgrudvizf/Build/Products/Debug/two.app/Contents/Resources/MyController.rb:15:in `initialize' from /Users/davidkramf/Library/Developer

3 7

OpenGL framework: gl.h versus gl3.h
by Jim Getzen 12 Dec '12

12 Dec '12

I am developing a basic MacRuby OpenGL library and I am avoiding the deprecated fixed-function pipeline in favor of OpenGL 3.2+ core functionality. The problem is Apple's OpenGL framework has two primary header files: gl.h and gl3.h. In Objective-C, I can just do: #import <OpenGL/gl3.h> to access OpenGL 3.2 functions. In MacRuby, I seem to be limited to: framework 'OpenGL', which loads the older gl.h header. To a large extent it doesn't matter since much of the 3.2 core functions already existed in OpenGL 2.1. However, there are some functions I need that only exist in 3.2: glBindVertexArray glGenVertexArrays glDeleteVertexArrays Versions of those functions do exist in OpenGL 2.1 (gl.h) with the APPLE suffix (e.g. glBindVertexArrayAPPLE), but they do not work when using a 3.2 core context. I have worked around the issue with an Obj-C wrapper that imports gl3.h and wraps those specific functions, but it results in a warning: "gl.h and gl3.h are both included. Compiler will not invoke errors if using removed OpenGL functionality." At first glance, the clouds would part and the sun would shine if I could just load the gl3.h header from MacRuby instead of gl.h. However, I suspect that I would then be faced with a bridgesupport file that doesn't reflect gl3.h. Having a bit of Obj-C code in my library isn't the end of the world, but I'd like to avoid the multiple-header warning, plus possible problems that might result from using OpenGL 2.1 functions with a 3.2 context (although I haven't seen any yet). Any suggestions? Just port the whole kit to Obj-C and be done? Ugh. On a related note, these constants are supposed to be defined in AppKit.framework bridgesupport, but aren't: NSOpenGLPFAOpenGLProfile = 99 NSOpenGLProfileVersion3_2Core = 0x3200 Jim

1 0

Problem with a window controller
by david kramf 09 Dec '12

09 Dec '12

Hi, In the copied below code only the awakeFromNib is executed . Can someone explain me what do I do wrong ? Window is displayed and I expected all other methods to be called. Thanks, David class MyController < NSWindowController attr_accessor :window def awakeFromNib @window.delegate = self puts " at end of awake from nib. title is #{(a)window.title}" end def windowWillLoad puts "window will be soon loaded" end def windowDidLoad puts "window loaded" end def windowTitleForDocumentDisplayName(displayName) "Hello World" end

5 15

MacBacon problem
by stephen horne 03 Dec '12

03 Dec '12

I'm trying to get started with tdd and MacRuby, but I've hit a stumbling block immediately with macbacon. I suspect it's something to do with rvm, but I'm not sure. When I run macbacon like this: $macbacon my_class_test.rb I get the following error backtrace: /Users/fatboy/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': /Users/fatboy/.rvm/gems/ruby-1.9.3-p125/gems/mac_bacon-1.3/lib/mac_bacon.rb:212: syntax error, unexpected tLABEL (SyntaxError) ...eForKeyPath(key_path, ofObject:object, change:_, context:__) ... ^ /Users/fatboy/.rvm/gems/ruby-1.9.3-p125/gems/mac_bacon-1.3/lib/mac_bacon.rb:337: class definition in method body /Users/fatboy/.rvm/gems/ruby-1.9.3-p125/gems/mac_bacon-1.3/lib/mac_bacon.rb:429: syntax error, unexpected keyword_end, expecting $end from /Users/fatboy/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /Users/fatboy/.rvm/gems/ruby-1.9.3-p125/gems/mac_bacon-1.3/bin/macbacon:110:in `<top (required)>' from /Users/fatboy/.rvm/gems/ruby-1.9.3-p125/bin/macbacon:19:in `load' from /Users/fatboy/.rvm/gems/ruby-1.9.3-p125/bin/macbacon:19:in `<main>' Can anyone see what's wrong with my setup? Thanks. -- Stephen Horne

4 10