rubycocoa-talk — talking about RubyCocoa

Re: [Rubycocoa-talk] build problems

[FUJIMOTO H. <hi...@fo...>]

At Mon, 1 Dec 2003 23:30:17 -0600,
Dan Weinand wrote:
> I did indeed subclass it in interface builder, and I have read up on 
> cocoa.
(snip)

I am weak in reading a detailed text by English.  Candidly I may
not understand exactly your issue even if I read these
explanation.  I guess you can show a real code snippet which
described the issue as simply as possible. So I may understand it.

When I will have the time, I try to read and understanding your
e-mail ;-). Sorry.

Isn't there somebody of native speaker who answer this issue?

regards
--
FUJIMOTO Hisakuni

Re: [Rubycocoa-talk] build problems

[Dan W. <dwe...@ri...>]

I did indeed subclass it in interface builder, and I have read up on 
cocoa.

For what its worth, I still have been unable to discover the cause of 
the errors. I was able to duplicate the error in new projects (with a 
control or two and an AppController subclass), created from the 
rubycocoa templates in xcode and again in project builder.

At this point I was incredibly frustrated and completely baffled. I 
went over every single word of code and every aspect of my nib files. 
They were all solid. As a last resort I finally decided to try 
something i figured wouldn't work. I went into one of the example 
NSObject subclass files and copied the "< OSX::NSObject" part (even 
though it was the exact same in my document). I deleted that part from 
my file and pasted the section from the other. To my amazement, the 
error disappeared.

In it's place, were several more extremely odd errors. For instance it 
claimed that my "end" tags were void expressions. I checked and I had 
the right number of tags. I got so fed up with trying to get rid of the 
errors, that I decided to start over completely from scratch.

This time I used project builder (even though my earlier experiments 
had yielded the same errors). The first thing I did was to create my 
interface, and subclass NSObject. I wrote up the class definition with 
a few outlet initializations and an action that did nothing.

I was once again surprised when my application built and ran without 
error. I broke down my code in to very small chunks, and worked at an 
extremely slow place, doing one small step, then building and such. 
Even after copying in my code (the exact same code mind you) it 
continued to build. The only thing I did different was to use a regular 
ruby class instead of an NSObject subclass for my support class. I know 
that factor wasn't the cause of the initial error, though. Because it 
failed at my controller class too.

I am just as amazed, and confounded by these events as I imagine you 
may be after reading it. I'm not new to programming, I have worked with 
cocoa before, and I picked up ruby in a day. I'm used to dealing with 
bugs in my code, sometimes even hard to find ones. However, ruby has 
such a clean syntax, and rubycocoa is likewise fairly straightforward, 
and my application was pretty small as programs go, that I was able to 
analyze every character, every space, everything in my code. The one 
thing I hate more than most other things, is when a 
computer/application does something unexpected, defies logic.

I still don't know why my code didn't work before, or why it works now. 
I guess the moral of the story is that when all the solutions that 
should work don't, the only thing left to do is the stuff that 
shouldn't work at all.

-Dan Weinand

btw. I now have a fully operational pre-alpha executable that I'm 
testing on various other computers. Ruby and RubyCocoa are great...when 
they work.

On Dec 1, 2003, at 7:23 PM, FUJIMOTO Hisakuni wrote:

> At Sat, 29 Nov 2003 16:26:26 -0600,
> Dan Weinand wrote:
>> My rubycocoa application has two classes derived from NSObject. One is
>> a standard AppController, and the other is just a simple support 
>> class.
>>
>> When I build my application it comes up with "Unknown class
>> `AppController' in nib file, using `NSObject' instead." The same error
>> occurs with my other class.
>>
>> I checked and all of the examples build fine. I have gone through 
>> every
>> piece of code in the samples to try and find out what I'm missing, but
>> I can't find anything.
>>
>> My class files are named the exact class name in IB (including case).
>> They are in the same folder as the project file.
>> I have all my require and includes, and my class definitions are in 
>> the
>> exact same format as in the examples.
>
> You forgot to do subclassing AppController on "classes" tab of a
> nib window of Interface Builder. Didn't you?  If this guess is
> wrong, I'm sorry.
>
> Have you learned some simple tutorial of Cocoa like Currency
> Converter with Objective-C, Java or others? If you have done, you
> can do a same almost with RubyCocoa.
>
> regards
> -- 
> FUJIMOTO Hisakuni
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] build problems

[FUJIMOTO H. <hi...@im...>]

At Sat, 29 Nov 2003 16:26:26 -0600,
Dan Weinand wrote:
> My rubycocoa application has two classes derived from NSObject. One is 
> a standard AppController, and the other is just a simple support class.
> 
> When I build my application it comes up with "Unknown class 
> `AppController' in nib file, using `NSObject' instead." The same error 
> occurs with my other class.
> 
> I checked and all of the examples build fine. I have gone through every 
> piece of code in the samples to try and find out what I'm missing, but 
> I can't find anything.
> 
> My class files are named the exact class name in IB (including case). 
> They are in the same folder as the project file.
> I have all my require and includes, and my class definitions are in the 
> exact same format as in the examples.

You forgot to do subclassing AppController on "classes" tab of a
nib window of Interface Builder. Didn't you?  If this guess is
wrong, I'm sorry.

Have you learned some simple tutorial of Cocoa like Currency
Converter with Objective-C, Java or others? If you have done, you
can do a same almost with RubyCocoa.

regards
-- 
FUJIMOTO Hisakuni

[Rubycocoa-talk] build problems

[Dan W. <dwe...@ri...>]

This may seem like a stupid question, but I can't seem to figure it out 
on my own.

My rubycocoa application has two classes derived from NSObject. One is 
a standard AppController, and the other is just a simple support class.

When I build my application it comes up with "Unknown class 
`AppController' in nib file, using `NSObject' instead." The same error 
occurs with my other class.

I checked and all of the examples build fine. I have gone through every 
piece of code in the samples to try and find out what I'm missing, but 
I can't find anything.

My class files are named the exact class name in IB (including case). 
They are in the same folder as the project file.
I have all my require and includes, and my class definitions are in the 
exact same format as in the examples.

I have looked through all the documentation, the examples, and  the 
list archives, but I can't find any reference to any additional step I 
may have neglected to take.

It seems like it should be something pretty simple, a stupid mistake 
even, but I just can't figure it out.

Thanks in advance.

-Dan Weinand

[Rubycocoa-talk] patch for Panther

[FUJIMOTO H. <hi...@im...>]

Kimura-san have posted a rubycocoa patch for Panther in rubycocoa
mailing-list for Japanese:

  http://www.freeml.com/message/rub...@fr.../0000222

URL for the patch is:

  http://homepage.mac.com/kimuraw/archive/rubycocoa-10.3.patch.gz

A translated message of Kimura-san is the following:

I tried to make a patch to 4.1-d9.

I have confirmed that result of testall.rb is all OK on:
  * ruby 1.6.8 included in Panther package
  * ruby 1.8.0 with "--enable-shared" option

http://homepage.mac.com/kimuraw/archive/rubycocoa-10.3.patch.gz

Contents of a patch as follows:

 * avoid SEGV error in config with ruby 1.6.8
 * execute "ruby gen_cocoa_wrapper.rb -f" in config phase
 * add several files which a project does not include to a target
 * patch for DummyProtocolHandler.m
 * if a xcodebuild exists, use it instead of pbxbuild
 * link libruby.dylib instead of libruby-static.a
 * link lFoundation.framework

And there are the following limit/problems:

 * libruby.dylib is required for build (ruby included in Panther
     is no problem about this)
 * Build is possible only on Panther

How to use of a patch
----
% (get 0.4.1-d9 from CVS)
% cd rubycocoa
% patch -p0 < rubycocoa-10.3.patch
% ruby install.rb config
% ruby install.rb setup
% sudo ruby install.rb install
----

Re: [Rubycocoa-talk] Bad project file?

[Mark H. <di...@ma...>]

On Nov 25, 2003, at 9:54 AM, rsc...@xm... wrote:

> When I try to open the RubyCocoa framework project file 
> (RubyCocoa.pbproj)
> in Xcode I get a message saying it can't open the file because the 
> .pbxproj
> file is missing. I don't see that file and it doesn't appear to come 
> with
> the source download. Anybody else run into this?

It will do that if you don't run "ruby install.rb config" before you 
try to open the project. the .pbxproj file starts out with '.in' 
appended to it's extension, and running the config script modifies the 
file and  renames it properly. This one had me stumped for  quite a 
while.

[Rubycocoa-talk] Bad project file?

[<rsc...@xm...>]

When I try to open the RubyCocoa framework project file (RubyCocoa.pbproj)
in Xcode I get a message saying it can't open the file because the .pbxproj
file is missing. I don't see that file and it doesn't appear to come with
the source download. Anybody else run into this?

Thanks,

Rod Schmidt

Re: [Rubycocoa-talk] Panther (more?)

[FUJIMOTO H. <hi...@im...>]

At Wed, 12 Nov 2003 11:33:35 +1100,
Charles Miller wrote:
> On 12/11/2003, at 10:49 AM, Kevin Bullock wrote:
> > I just subscribed, so I don't know if this has been discussed further, 
> > but I've been attempting to get RubyCocoa working on Panther, using 
> > the included ruby installation (1.6.8, libruby and headers are 
> > included, unlike in Jaguar). Despite applying the patch 
> > (http://www.imasy.or.jp/~hisa/mac/rubycocoa/build.en.html#label:19), I 
> > still get a segfault during the configure process. Here's a 
> > transcript:
> 
> I had the same problem. The weird thing was that the segfault always 
> occurred during processing of the _second_ file in post-config.rb, no 
> matter which order I told it to process the files in.
> 
> Running in gdb, I found the following backtrace: the problem seemed to 
> be happening in the garbage collector somewhere.
> 
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> 0x00019918 in rb_gc_mark ()
> (gdb) bt
> #0  0x00019918 in rb_gc_mark ()
> #1  0x00019f7c in rb_gc_mark ()
> #2  0x0001973c in rb_source_filename ()
> #3  0x0001a86c in rb_gc ()
> #4  0x000194b8 in rb_newobj ()
> 
> When I edited post-config.rb and put a call to "GC.start" right 
> underneath "load 'tool/create-appkit-and-foundation.rb'", the config 
> worked.

I'm going to apply this modification into cvs repository of rubycocoa.
Thank you for useful info.
-- 
FUJIMOTO Hisakuni

Re: [Rubycocoa-talk] Panther (much more info)

[Kevin B. <krb...@ma...>]

Further accounts of my progress follow below.

Charles Miller wrote:

<snip>
> I had the same problem. The weird thing was that the segfault always
> occurred during processing of the _second_ file in post-config.rb, no
> matter which order I told it to process the files in.
>
<snip>
> When I edited post-config.rb and put a call to "GC.start" right
> underneath "load 'tool/create-appkit-and-foundation.rb'", the config
> worked.

This worked for me as well. I then ran into the problem of not being  
able to find libruby.a (I'm really going from a stock Panther install,  
no recompiling ruby even for the static library), so I opened the  
project (framework/RubyCocoa.pbproj) in Xcode and made it link to the  
installed libruby.1.dylib instead. I'm still not sure if building it  
against the dynamic library will work, but I'm giving it a shot since  
Panther includes it.

Here's another issue I ran into:

src/objc/cocoa/rb_NSGraphics.m: In function `init_NSGraphics':
src/objc/cocoa/rb_NSGraphics.m:1483: error: `NSAlphaEqualToData'  
undeclared (first use in this function)
src/objc/cocoa/rb_NSGraphics.m:1484: error: `NSAlphaAlwaysOne'  
undeclared (first use in this function)

 From Mac OS X Panther Release Notes: Cocoa Application Framework  
(http://developer.apple.com/documentation/ReleaseNotes/Cocoa/ 
AppKit.html):

Obsolete Symbols
NSAlphaEqualToData and NSAlphaAlwaysOne (with values of 1 and 2,  
respectively) have been removed from NSGraphics.h as they have not been  
used since before 10.0.

I commented out the two appropriate lines in  
framework/src/objc/rb_NSGraphics.m, and the build continued.

Similarly, I found a number of constants in NSSavePanel that were  
deprecated and have been removed as of 10.3:

NSFileHandlingPanelImageButton
NSFileHandlingPanelTitleField
NSFileHandlingPanelBrowser
NSFileHandlingPanelForm
NSFileHandlingPanelHomeButton
NSFileHandlingPanelDiskButton
NSFileHandlingPanelDiskEjectButton

I commented these out in framework/src/objc/rb_NSSavePanel.m. After  
this, the build completed successfully, but it still doesn't appear to  
result in a working RubyCocoa:

kbullock:Source/ruby/rubycocoa-0.4.0% irb -r 'osx/cocoa'
objc: failed objc_getClass(NSObject) for NSServicesPasteboard->isa->isa
objc: please link appropriate classes in your program

This one I can't figure out. I can't even find what  
NSServicesPasteboard is on Apple's developer site. Any ideas here? Is  
anyone on the Japanese list working on this? (I unfortunately can't  
read Japanese.) Thanks for your help so far. If I can get this working,  
I'll submit a patch back.

Pacem in terris / Mir / Shanti / Salaam / Heiwa
Kevin R. Bullock

Re: [Rubycocoa-talk] Panther (more?)

[Jin C. <jin...@ma...>]

I've managed to get RubyCocoa built and running on Panther against ruby 
1.8.0.  I haven't tried redoing this with the default ruby that comes 
with Panther, but these experiences may help others to figure that out.

There were several issues; I will just detail them in the form of a 
recipe for what I did to get it all working.

1. Install ruby-1.8. I used fink. If you install from source, make sure 
you build the shared library (configure --enable-shared).

2. Get the RubyCocoa source tree from CVS (I used the CVS version; 
other sources from packaged distributions may work but I have not 
tried).

3. There are several Cocoa constants defined in the ruby wrappers that 
are now obsolete on Panther. You must rebuild them:
     cd framework/src/objc/cocoa
     rm rb_*.m
     ruby gen_cocoa_wrapper.rb

4. Run "ruby install.rb config"

5. Open the framework project file (framework/RubyCocoa.pbproj) using 
Xcode; we'll have to make two changes:

Problem: The error "objc: failed objc_getClass(NSObject) for 
NSServicesPasteboard->isa->isa" when attempting to load the rubycocoa 
bundle.
Resolution: I have yet to figure out what NSServicesPasteboard is 
(completely undocumented); there are symbols for it in the AppKit 
framework, but strangely, it is linking against the Foundation 
framework that causes this error to go away. So: in the project, go 
down to RubyCocoa->External Frameworks and check the button beside 
Foundation.framework.

Problem: The error "/sw/lib/ruby/site_ruby/1.8/osx/cocoa.rb:12:in 
`require': No such file to load -- osx/objc/cocoa (LoadError)" when 
attempting to require 'osx/cocoa'.
Resolution: This comes about because the code in the bundle to patch 
the ruby load path doesn't access the same global variable rb_load_path 
when linked against the ruby static library as the one in the ruby 
image. Simply unselect libruby-static.a from the file list.

That's it. Hit build while you're in xcode. If you want to do it from 
the command line, modify install.rb to use xcodebuild rather than 
pbxbuild and run "ruby install.rb setup". Then "ruby install.rb 
install" as usual.

Hope this helps somebody.

-Jin

Re: [Rubycocoa-talk] Panther (more?)

[Charles M. <cm...@pa...>]

On 12/11/2003, at 10:49 AM, Kevin Bullock wrote:

> I just subscribed, so I don't know if this has been discussed further, 
> but I've been attempting to get RubyCocoa working on Panther, using 
> the included ruby installation (1.6.8, libruby and headers are 
> included, unlike in Jaguar). Despite applying the patch 
> (http://www.imasy.or.jp/~hisa/mac/rubycocoa/build.en.html#label:19), I 
> still get a segfault during the configure process. Here's a 
> transcript:

I had the same problem. The weird thing was that the segfault always 
occurred during processing of the _second_ file in post-config.rb, no 
matter which order I told it to process the files in.

Running in gdb, I found the following backtrace: the problem seemed to 
be happening in the garbage collector somewhere.

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x00019918 in rb_gc_mark ()
(gdb) bt
#0  0x00019918 in rb_gc_mark ()
#1  0x00019f7c in rb_gc_mark ()
#2  0x0001973c in rb_source_filename ()
#3  0x0001a86c in rb_gc ()
#4  0x000194b8 in rb_newobj ()

When I edited post-config.rb and put a call to "GC.start" right 
underneath "load 'tool/create-appkit-and-foundation.rb'", the config 
worked.

It worked for me, but I have no idea why it worked so it might not work 
for you.

Charles Miller

-- 
Contributing to the heat death of the Universe since 1975
cm...@pa...           http://fishbowl.pastiche.org

[Rubycocoa-talk] Panther (more?)

[Kevin B. <krb...@ma...>]

I just subscribed, so I don't know if this has been discussed further,  
but I've been attempting to get RubyCocoa working on Panther, using the  
included ruby installation (1.6.8, libruby and headers are included,  
unlike in Jaguar). Despite applying the patch  
(http://www.imasy.or.jp/~hisa/mac/rubycocoa/build.en.html#label:19), I  
still get a segfault during the configure process. Here's a transcript:

kbullock:Source/ruby/rubycocoa-0.4.0% sudo ruby install.rb config
install.rb: entering config phase...
create ext/rubycocoa/extconf.rb
create ext/rubycocoa/rubycocoa.m
create framework/RubyCocoa.pbproj/project.pbxproj
create framework/src/objc/RBObject.h
create framework/src/objc/RBSlaveObject.h
create framework/src/objc/RubyCocoa.h
create framework/src/objc/Version.h
---> framework
create  
/Users/kbullock/Source/ruby/rubycocoa-0.4.0/framework/src/objc/ 
osx_ruby.h ...
create  
/Users/kbullock/Source/ruby/rubycocoa-0.4.0/framework/src/objc/ 
osx_intern.h ...
/Users/kbullock/Source/ruby/rubycocoa-0.4.0/framework/post-config.rb: 
14: [BUG] Segmentation fault
ruby 1.6.8 (2002-12-24) [powerpc-darwin7.0]

The reason for this segfault, I sense, is buried somewhere in Ruby's  
internals, or is a problem with the OS X installation of it. Any ideas?  
I haven't gotten any further than this, so I don't know if it will  
build properly or not. Thanks.

Pacem in terris / Mir / Shanti / Salaam / Heiwa
Kevin R. Bullock

Re: [Rubycocoa-talk] undefined superclass `ObjcID' (TypeError) [SOLVED]

[<li...@po...>]

Just for the record, RubyCocoa 0.4.1d9 has fixed the problem for me.

Thanks,
-Ralph.

> Hi,
>
> is it possible to run RubyCocoa with ruby 1.8.0 on MacOS 10.2.8?
>
> I built both from source, but RubyCocoa's tests fail with
>> $ ruby testall.rb
>> No such file to load -- osx/objc/cocoa (LoadError)
>
> I worked around that problem, but now I get a TypeError:
>> $ ruby  -I 
>> /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby 
>> testall.rb
>> undefined superclass `ObjcID' (TypeError)
>
> The problem occurs whenever 'osx/cocoa' is required. Requiring 
> 'rubycocoa' seems to work fine.
>
> Can anyone help? None of the suggestions I found on the web have 
> worked for me. I'd be happy to provide more diagnostic information.
>
> Thanks in advance,
> -Ralph.

[Rubycocoa-talk] Panther

[Rod S. <rsc...@xm...>]

Anybody get RubyCocoa to work under Panther with Xcode yet? If so, what 
did you have to do?

Rod Schmidt

Re: [Rubycocoa-talk] Calling RubyCocoa from Objective-C app

[FUJIMOTO H. <hi...@im...>]

At Mon, 13 Oct 2003 10:13:09 -0600,
Rod Schmidt wrote:
> Unless I'm missing something (you may need to point me to something more
> specific), I think you misunderstood me. I'm not trying to call Cocoa
> classes from Ruby but Ruby classes from an Objective-C Cocoa app.

I'm very sorry. You was not missing anything, but I had jumped to
a misleading conclusion about your message. Now, I have understood
your question, maybe.

> Is there another way to do this besides using Ruby's C API.? How
> could I do it using the RubyCocoa framework?

I guess that the following show an answer of your question:

/* cc -I/usr/lib/ruby/1.6/powerpc-darwin6.0 -framework Cocoa -framework RubyCocoa test.m */
#import <Cocoa/Cocoa.h>
#import <RubyCocoa/RubyCocoa.h>

int main()
{
  id pool;
  id obj;

  RBRubyCocoaInit();  /* initialize Ruby and RubyCocoa */
  pool = [[NSAutoreleasePool alloc] init];
  obj = [RBObject RBObjectWithRubyScriptCString: "'hello world'" ]; /* eval string */
  NSLog(@"%@", obj);
  obj = [[RBObject alloc] initWithRubyObject: rb_cTime];
  NSLog(@"%@", obj);
  obj = [obj now];   /* obj is a RBObject with wrapping a result of obj.now */
  NSLog(@"%@", obj);
  [pool release];
  return 0;
}

--
Hisa

Re: [Rubycocoa-talk] Calling RubyCocoa from Objective-C app

[<rsc...@xm...>]

Unless I'm missing something (you may need to point me to something more
specific), I think you misunderstood me. I'm not trying to call Cocoa
classes from Ruby but Ruby classes from an Objective-C Cocoa app.

Is there another way to do this besides using Ruby's C API.? How could I do
it using the RubyCocoa framework?

Rod Schmidt
infiniteNIL Software

Quoting FUJIMOTO Hisakuni <hi...@im...>:

> At Tue, 07 Oct 2003 07:44:04 +0900,
> hi...@im... wrote:
> > 
> > At Sun, 5 Oct 2003 13:26:12 -0600,
> > Rod Schmidt wrote:
> > > If I create an Objective-C cocoa app with Project Builder, can I also
> 
> > > create some RubyCocoa classes and use them in my program like they
> are 
> > > normal Cocoa classes? If so, how would I do that?
> > 
> > You may need to read soruce of addressbook.rb or webkit.rb in AAA,
> > in the {SOURCE}/framework/src/ruby/osx/objc directory.  Perhaps,
> > it is helpful.
> 
> correct the above:
> 
> You may need to read soruce of addressbook.rb or webkit.rb in the
> {SOURCE}/framework/src/ruby/osx/objc directory.  Perhaps, it is
> helpful.
> 
> --
> Hisa
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
> 

[Rubycocoa-talk] undefined superclass `ObjcID' (TypeError)

[<li...@po...>]

Hi,

is it possible to run RubyCocoa with ruby 1.8.0 on MacOS 10.2.8?

I built both from source, but RubyCocoa's tests fail with
> $ ruby testall.rb
> No such file to load -- osx/objc/cocoa (LoadError)

I worked around that problem, but now I get a TypeError:
> $ ruby  -I 
> /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby 
> testall.rb
> undefined superclass `ObjcID' (TypeError)

The problem occurs whenever 'osx/cocoa' is required. Requiring 
'rubycocoa' seems to work fine.

Can anyone help? None of the suggestions I found on the web have worked 
for me. I'd be happy to provide more diagnostic information.

Thanks in advance,
-Ralph.

Re: [Rubycocoa-talk] Calling RubyCocoa from Objective-C app

[FUJIMOTO H. <hi...@im...>]

At Tue, 07 Oct 2003 07:44:04 +0900,
hi...@im... wrote:
> 
> At Sun, 5 Oct 2003 13:26:12 -0600,
> Rod Schmidt wrote:
> > If I create an Objective-C cocoa app with Project Builder, can I also 
> > create some RubyCocoa classes and use them in my program like they are 
> > normal Cocoa classes? If so, how would I do that?
> 
> You may need to read soruce of addressbook.rb or webkit.rb in AAA,
> in the {SOURCE}/framework/src/ruby/osx/objc directory.  Perhaps,
> it is helpful.

correct the above:

You may need to read soruce of addressbook.rb or webkit.rb in the
{SOURCE}/framework/src/ruby/osx/objc directory.  Perhaps, it is
helpful.

--
Hisa

Re: [Rubycocoa-talk] Calling RubyCocoa from Objective-C app

[FUJIMOTO H. <hi...@im...>]

At Sun, 5 Oct 2003 13:26:12 -0600,
Rod Schmidt wrote:
> If I create an Objective-C cocoa app with Project Builder, can I also 
> create some RubyCocoa classes and use them in my program like they are 
> normal Cocoa classes? If so, how would I do that?

You may need to read soruce of addressbook.rb or webkit.rb in AAA,
in the {SOURCE}/framework/src/ruby/osx/objc directory.  Perhaps,
it is helpful.

--
Hisa

[Rubycocoa-talk] Calling RubyCocoa from Objective-C app

[Rod S. <rod...@in...>]

If I create an Objective-C cocoa app with Project Builder, can I also 
create some RubyCocoa classes and use them in my program like they are 
normal Cocoa classes? If so, how would I do that?

Rod Schmidt
infiniteNIL Software
www.infinitenil.com

[Rubycocoa-talk] build on panther?

[Mark H. <di...@ma...>]

Hi there
Has anyone had any success compiling or installing RubyCocoa on Panther 
(10.3)? For me, installing fails, and building fails. I hunted down 
*one* of the problems: "pbxbuild" is renamed to "xcodebuild". It still 
won't compile successfully, though, and I'm wondering if anyone has 
gotten similar results.
Thanks in advance for any help,
Mark

[Rubycocoa-talk] Re: 1 Rubycocoa-talk admin request(s) waiting

[FUJIMOTO H. <hi...@im...>]

Hi, Brian,

The rubycocoa-talk list manager said "Your message was too big;
please trim it to less than 40 KB in size."

Your full install log was too big and unreadable format
also. Could you paste a plain text on a message simply, instead of
an attached file?

Thanks,
--
Hisa

Re: [Rubycocoa-talk] RubyCocoa install problems

[FUJIMOTO H. <hi...@im...>]

At Wed, 10 Sep 2003 13:31:07 -0400,
Brian McCallister wrote:
(snip)
> ld: table of contents for archive:  
> /Users/mccallister/opt/apps/ruby-1.8.0/lib/libruby-static.a is out of  
> date; rerun ranlib(1) (can't load from it)
> /usr/bin/libtool: internal link edit command failed
> ...failed DynamicLibrary.LinkUsingFileList  
> /Users/mccallister/work/rubycocoa-0.4.0/framework/build/ 
> RubyCocoa.framework/Versions/A/RubyCocoa ...
> ** BUILD FAILED **
> setup failed
(snip)

Execute the following once:

  $ cd /Users/mccallister/opt/apps/ruby-1.8.0/lib
  $ sudo cp -p libruby-static.a libruby-static.a.backup  # backup copy (optional)
  $ sudo ranlib libruby-static.a

Then build RubyCocoa. This process may bring about a good result.

--
Hisa

Re: [Rubycocoa-talk] RubyCocoa install problems

[FUJIMOTO H. <hi...@im...>]

At Wed, 10 Sep 2003 13:31:07 -0400,
Brian McCallister wrote:
(snip)
> ld: table of contents for archive:  
> /Users/mccallister/opt/apps/ruby-1.8.0/lib/libruby-static.a is out of  
> date; rerun ranlib(1) (can't load from it)
> /usr/bin/libtool: internal link edit command failed
> ...failed DynamicLibrary.LinkUsingFileList  
> /Users/mccallister/work/rubycocoa-0.4.0/framework/build/ 
> RubyCocoa.framework/Versions/A/RubyCocoa ...
> ** BUILD FAILED **
> setup failed
(snip)

Execute the following once:

  $ cd /Users/mccallister/opt/apps/ruby-1.8.0/lib
  $ sudo cp -p libruby-static.a libruby-static.a.backup  # backup copy (optional)
  $ sudo ranlib libruby-static.a

Then build RubyCocoa. This process may bring about a good result.

--
Hisa

Re: [Rubycocoa-talk] RubyCocoa install problems

[Gavin E. <gav...@ma...>]

At 3:56 PM -0400 9/10/03, Brian McCallister wrote:
>Attached are my links. Notably, I do not have an osx_aeosa.bundle 
>anywhere on my system.
>
>Still getting the errors.

... hmm, looks like your links are good in that they point to the 
right relative location.

     was your RubyCocoa.framework build also told to refer into the 
~/opt/apps/ruby-1.8.0 directory?

     not having osx_aeosa.bundle is not critical
     (I just deleted the symlink on my laptop and HelloWorld.rb still works)

     You mention various troubles with builds of RubyCocoa -- but my 
suggestion about links is ONLY related to the error "No such file to 
load -- osx/objc/cocoa (LoadError)".  If you have build problems, 
that's something else.

     I'm afraid I'm just making guesses now and that's not what you 
need.  Sorry.