Recent changes to bugs

#67 TemplateInfo.plist in File Templates not working

kimura wataru — Sun, 31 May 2015 04:36:08 -0000

Thanks! I've merged your file.

https://github.com/rubycocoa/rubycocoa/commit/0f149877576ed777a10fff032de83046c324262b

TemplateInfo.plist in File Templates not working

kmav — Fri, 17 Apr 2015 03:21:31 -0000

Hello,

when I was trying to open the ruby file template in Xcode using version 1.2.0, it was not found under OSX/Cocoa. After several checks I found that TemplateInfo.plist had a misplacement of <dict> tags. I fixed the error according to some default (objective-c) template.

Now, the file template showed up, but without an icon. So, I coppied the icon file from Project Templates and now all is fine.

So, I am uploading the file with the fix in order to include it in an update of your project.

regards,

Konstantinos

10.8 support

Anonymous — Sat, 28 Jul 2012 16:21:10 -0000

10.8 support ??

Seg Fault in RubyCocoa 1.0.1 on Mac OS X 10.6

Anonymous — Mon, 22 Mar 2010 17:02:27 -0000

Related to another open bug, where installation of 1.0.1 by DMG fails, I installed via source without any errors according to the steps outlined in Getting Started. Install appeared to work correctly, by result is a broken library, seen when I run my rake file here:

[wgray@Ryoan-ji]~/Documents/Sources/Cocoa/StripSync:master
$ rake -T
(in /Users/wgray/Documents/Sources/Cocoa/StripSync)
/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/objc/oc_import.rb:127: [BUG] Segmentation fault
ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin10]

Abort trap

Im using the Mac Ports version of Ruby at the moment.

Wrong creation of cflags from --target-archs

OBATA Akio — Fri, 04 Dec 2009 12:15:06 -0000

On Mac OS X 10.4.11 with ruby-1.8.7 patchlevel 174 from pkgsrc,
install.rb --target-archs="ppc" result in

---> framework
create /private/var/tmp/obj/pkgsrc/wip/RubyCocoa/work/RubyCocoa-1.0.1/framework/src/objc/osx_ruby.h ...
create /private/var/tmp/obj/pkgsrc/wip/RubyCocoa/work/RubyCocoa-1.0.1/framework/src/objc/osx_intern.h ...
BSROOT="/private/var/tmp/obj/pkgsrc/wip/RubyCocoa/work/RubyCocoa-1.0.1/framework/bridge-support" CFLAGS="ppc" /usr/pkg/bin/ruby18 build.rb

Yes, it will be failed to build, CFLAGS should be "-arch ppc".

It came from typo in framework/post-config.rb:

cflags << archs.gsub(/\a|\s+/, ' -arch ') if archs.size > 0

It should be as following:

cflags << archs.gsub(/\A|\s+/, ' -arch ') if archs.size > 0

1.0.1 doesn't work with versions < 10.5.7

Nava Carmon — Sun, 01 Nov 2009 11:02:09 -0000

1.0.1 doesn't work with versions of Leopard, prior to 10.5.7. The application crashes on the start with the request of unknown setter

1.0.1 release crashes on 10.6

Nava Carmon — Sun, 01 Nov 2009 10:59:58 -0000

1.0.1 release enters indefinite loop and crashes on 10.6. Seems a regression for some reason. rev. 2277 builds and works both with 10.5 & 10.6

1.0.1 release crashes on 10.6

Anonymous — Sun, 01 Nov 2009 10:58:38 -0000

1.0.1 release enters indefinite loop and crashes on 10.6. Seems a regression for some reason. rev. 2277 builds and works both with 10.5 & 10.6

Converting Ruby string to NSString results in NSNull

Axel Roest — Fri, 30 Oct 2009 11:51:58 -0000

I have a ruby string which is made by filling an RTF template. The template is read in from a file with seemingly a Mac OS Roman encoding (or so says BBEdit). The template is expanded using ruby string concatenation and replacement. At the end it is about 150kB in length, but length is not the issue here. When I convert it back to NSString, I oftentimes get an NSNull instead of an NSString, and subsequent code crashes.

I've traced it down to an incorrect NSString.guess_nsencoding in cocoa_macros.rb. It guesses the data has encoding '8', which is NSShiftJISStringEncoding, instead of NSMacOSRomanStringEncoding.

The subsequent result is that NSString.alloc.initWithData_encoding returns an NSNull instead of the string.
When I manually convert using
data = NSData.dataWithRubyString( ftext )
enc = NSMacOSRomanStringEncoding
nsstr = OSX::NSString.alloc.initWithData_encoding( data, enc )

it works fine.

I hope you are able to reproduce the error, it has baffled me for days.

Enclosed is a simple appcontroller which is able to reproduce the bug if put in a rubycocoa application.
Template.rtf : the original template, which can correctly be converted
data.rtf: the generated data, which crashes the conversion.
Both rtf files open fine in TextEdit

OS platforms: the bug existed in 10.5.x and still exists in 10.6.1

MeCab not working on Snow Leopard RubyCocoa App

Anonymous — Wed, 14 Oct 2009 07:19:27 -0000

Hi,
I've been trying to use MeCab from RubyCocoa application on Snow Leopard. I installed the latest MeCab-Ruby (0.98) and I can use it from Ruby scripts, but not from RubyCocoa application. The same application runs fine on Leopard.

A simple script (sample on MeCab site) like the following ends up crashing the application.

require 'MeCab'
m = MeCab::Tagger.new("-Ochasen")
print m.parse("今日もしないとね")

The error message is the following:

dyld: lazy symbol binding failed: Symbol not found: __ZN5MeCab12createTaggerEPKc
Referenced from: /Library/Ruby/Site/1.8/universal-darwin10.0/MeCab.bundle
Expected in: flat namespace

dyld: Symbol not found: __ZN5MeCab12createTaggerEPKc
Referenced from: /Library/Ruby/Site/1.8/universal-darwin10.0/MeCab.bundle
Expected in: flat namespace

Could this be a bug or is there anything wrong with MeCab-Ruby on Snow Leopard? Considering it works fine with Ruby 1.8.7, it could be a RubyCocoa bug, though. Or is this fixed on the latest build?. Or should I blame MeCab-Ruby? I'm using 0.13.2, which I believe comes with Snow Leopard

Thanks.