rubycocoa-talk — talking about RubyCocoa

Re: [Rubycocoa-talk] RubyCocoa, CoreData, & NSPersistentDocumentTutorial

[kimura w. <ki...@us...>]

Hi,

I'm trying this tutorial.


Thu, 3 Nov 2005 23:13:03 +0000, Jonathan Paisley wrote:
>On 3 Nov 2005, at 21:31, Rupert Barrow wrote:
>

>Since you're using Core Data, all the data members of the class are  
>already managed for you. Therefore, you should not define firstName  
>and lastName as accessors, nor should you use ruby @firstName/ 
>@lastName variables.
>
>Instead, just access firstName etc as if it were already defined as  
>an accessor (or perhaps you need to use setValue:forKey: and  
>valueForKey:). RubyCocoa will forward the call through to Objective  
>C, where Core Data will handle the request for you.
>

It's right. To access attributes of an Employee, we have to use 
setValue:forKey and valueForKey:. 

for example:
------------
  def fullNameAndID
    return OSX::NSString.stringWithString(valueForKey("lastName").to_s + 
           ", " +  valueForKey("firstName").to_s)
  end
------------


I felt that was not smart. I defined a method "kvc_wrapper". This method 
defines accessors wrapping "valueForKey:" and "setValue:forKey:".
# tell me a better name of "kvc_wrapper", please.

my Employee.rb:
---------------
require 'osx/cocoa'
require 'osx/coredata'

# add kvc_wrapper
module OSX

  module NSKVCBehaviorAttachment

    # accessor for keys defined in Cocoa
    def kvc_wrapper(*keys)
      keys.each do |key|
        class_eval <<-EOE_KVC_WRAPPER,__FILE__,__LINE__+1
        def #{key}
          valueForKey("#{key}")
        end
        def #{key}=(val)
          setValue_forKey(val, "#{key}")
        end
        EOE_KVC_WRAPPER
      end
    end
  
  end

end

# Employee class 
class Employee < OSX::NSManagedObject
  
  kvc_depends_on [:lastName, :firstName], :fullNameAndID

  # define wrappers
  kvc_wrapper :lastName, :firstName, :employeeID 

  def fullNameAndID
    sprintf('%s, %s (%d)', lastName.to_s, firstName.to_s, employeeID)
  end
  
end
---------------


I think that is possible to define wrappers automatically from 
NSManagedObjectModel#entities -> NSEntityDescription, but I do not
know how to implement.



-- 
kimura wataru

Re: [Rubycocoa-talk] RubyCocoa, CoreData, & NSPersistentDocumentTutorial

[Jonathan P. <jp...@dc...>]

On 3 Nov 2005, at 21:31, Rupert Barrow wrote:

> I have got to chapter 3 (creating the custome Employee class) :  
> this works with Employee.rb, I have even got fullNameAndID working,  
> dynamically computed from firstName and lastName, and displayed in  
> the GUI.
> However, I do not seem to be able to connect firstName in the GUI  
> with the model in Employee.rb; ditto for lastName. This is my  
> Employee class :

I'm not entirely sure from your description what the problem you're  
having is. However, I do notice a problem with your code that may be  
related:

> class Employee < OSX::NSManagedObject
>     include OSX
>
>     attr_accessor :firstName
>     attr_accessor :lastName
>
>     kvc_accessor :lastName, :firstName
>     kvc_depends_on([ :lastName, :firstName], :fullNameAndID)
>
>     def initialize
>         @firstName = "MyFirst"
>         @lastName  = "MyLast"
>     end
>

[Let me say first that I've not used Core Data yet, so this is my  
understanding from glancing over the documentation. Please correct  
any misunderstanding!]

Since you're using Core Data, all the data members of the class are  
already managed for you. Therefore, you should not define firstName  
and lastName as accessors, nor should you use ruby @firstName/ 
@lastName variables.

Instead, just access firstName etc as if it were already defined as  
an accessor (or perhaps you need to use setValue:forKey: and  
valueForKey:). RubyCocoa will forward the call through to Objective  
C, where Core Data will handle the request for you.


Hope that is of some help,
Jonathan

[Rubycocoa-talk] RubyCocoa, CoreData, & NSPersistentDocumentTutorial

[Rupert B. <rup...@li...>]

Hi,

I am using today's latest CVS version of RubyCocoa, and trying  
coredata and kvc_depends_on : great !
I am trying to "translate" the NSPersistentDocumentTutorial into Ruby :
     http://developer.apple.com/documentation/Cocoa/Conceptual/ 
NSPersistentDocumentTutorial

I have got to chapter 3 (creating the custome Employee class) : this  
works with Employee.rb, I have even got fullNameAndID working,  
dynamically computed from firstName and lastName, and displayed in  
the GUI.
However, I do not seem to be able to connect firstName in the GUI  
with the model in Employee.rb; ditto for lastName. This is my  
Employee class :

class Employee < OSX::NSManagedObject
     include OSX

     attr_accessor :firstName
     attr_accessor :lastName

     kvc_accessor :lastName, :firstName
     kvc_depends_on([ :lastName, :firstName], :fullNameAndID)

     def initialize
         @firstName = "MyFirst"
         @lastName  = "MyLast"
     end

     def fullNameAndID
         return OSX::NSString.stringWithString(@lastName + ", " +  
@firstName)
     end

end

What am I missing ?  Is there something not obvious which should be  
done, considering that this tutorial uses bindings (of course) ad  
core data (including a data model with entities) ?

Thanks for any help,
Rup

[Rubycocoa-talk] [ANN]re-release of RubyCocoa 0.4.1 binary package for tiger(10.4)

[kimura w. <ki...@us...>]

Hi,

It's a bad news. The RubyCocoa binary package for tiger was broken.
We released fixed RubyCocoa-0.4.1-tiger.dmg.

http://prdownloads.sourceforge.net/rubycocoa/RubyCocoa-0.4.1-tiger.dmg?download
MD5: a38e14cb592e39b2460d3a1ec9a081bc

(old file's MD5: 4c8e25313e07800b7b4c3b610f728b48)

= more info =

The package did not contain following files:

* lib/ruby/site_ruby/powerpc-darwin8.0/rubycocoa.bundle
* lib/ruby/site_ruby/osx/*.rb

A ruby script on command line fails at `require "osx/cocoa"', 
but an RubyCocoa application runs without problem.


-- 
kimura wataru

Re: [Rubycocoa-talk] Ruby/Cocoa and CoreData

[kimura w. <ki...@us...>]

Hi,

I added kvc_depends_on(keys, *dependencies) to CVS.
Thanks!

Tue, 13 Sep 2005 18:06:21 +0200, Sean Legassick wrote:
>
>On 13 Sep 2005, at 17:08, Jonathan Paisley wrote:
>> Even if the triggerChangeNotifications... method worked, I like the  
>> idea of a ruby meta-method for setting them up - much less to type!
>
>Absolutely, and I've made mine more flexible just now so you can say:
>
>cocoa_depends_on :key, :dependency
>cocoa_depends_on [ :key1, :key2 ], :dependency
>cocoa_depends_on :key, [ :dependency1. :dependency2 ]
>cocoa_depends_on [ :key1, :key2 ], [ :dependency1, :dependency2 ]
>
>(I think on reflection cocoa_depends_on is a little more clear than  
>cocoa_depends)


-- 
kimura wataru

Re: [Rubycocoa-talk] Segmentation fault in Typing Tutor

[Dave B. <dav...@3d...>]

Thanks,  that did the trick and Typing Tutor and my app are rock  
solid now.

Dave.

On 3 Oct 2005, at 18:15, Jonathan Paisley wrote:

> On 3 Oct 2005, at 17:51, Dave Baldwin wrote:
>
>>
>> When I run the Typing Tutor example and always on the 9th  
>> character I get the following error:
>>
>> /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/ 
>> osx/objc/oc_wrapper.rb:79: [BUG] Segmentation fault
>> ruby 1.8.2 (2004-12-25) [powerpc-darwin8.0]
>>
>> rubyapp has exited due to signal 6 (SIGABRT).
>>
>> I am running with 0.4.1 on Tiger (10.4.2).  This is also occurring  
>> in my own application and is making development difficult as you  
>> might imagine.
>>
>
> I can reproduce this with the 0.4.1 Tiger dmg release, but not with  
> my own-compiled recent CVS version. So I suppose it must be a  
> rubycocoa bug which has since been fixed.
>
> If you can build up the CVS version yourself it might be worth trying.
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,  
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>

Re: [Rubycocoa-talk] Segmentation fault in Typing Tutor

[Jonathan P. <jp...@dc...>]

On 3 Oct 2005, at 17:51, Dave Baldwin wrote:
>
> When I run the Typing Tutor example and always on the 9th character  
> I get the following error:
>
> /Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/ 
> osx/objc/oc_wrapper.rb:79: [BUG] Segmentation fault
> ruby 1.8.2 (2004-12-25) [powerpc-darwin8.0]
>
> rubyapp has exited due to signal 6 (SIGABRT).
>
> I am running with 0.4.1 on Tiger (10.4.2).  This is also occurring  
> in my own application and is making development difficult as you  
> might imagine.

I can reproduce this with the 0.4.1 Tiger dmg release, but not with  
my own-compiled recent CVS version. So I suppose it must be a  
rubycocoa bug which has since been fixed.

If you can build up the CVS version yourself it might be worth trying.

[Rubycocoa-talk] Segmentation fault in Typing Tutor

[Dave B. <dav...@3d...>]

Hi,

When I run the Typing Tutor example and always on the 9th character I  
get the following error:

/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/ 
objc/oc_wrapper.rb:79: [BUG] Segmentation fault
ruby 1.8.2 (2004-12-25) [powerpc-darwin8.0]

rubyapp has exited due to signal 6 (SIGABRT).

I am running with 0.4.1 on Tiger (10.4.2).  This is also occurring in  
my own application and is making development difficult as you might  
imagine.

Getting a core dump of my app and looking at it in gdb gave:

#0  0x9004a12c in kill ()
#1  0x90120954 in abort ()
#2  0x968ff668 in ?? ()
#3  0x9695fea8 in ?? ()
#4  <signal handler called>
#5  0x909ad100 in ?? ()
#6  0x000662f4 in rb_set_kcode ()
#7  0x969206cc in ?? ()
#8  0x96920f08 in ?? ()
#9  0x9691f4ec in ?? ()
#10 0x96962b7c in ?? ()
#11 0x96962d78 in ?? ()
#12 0x96908cf0 in ?? ()
#13 0x96907b04 in ?? ()
#14 0x9690d12c in ?? ()
#15 0x9690d5c0 in ?? ()
#16 0x96907e9c in ?? ()
#17 0x96907268 in ?? ()
#18 0x96908784 in ?? ()
#19 0x9690d12c in ?? ()
#20 0x9690d5c0 in ?? ()
#21 0x9690c8f0 in ?? ()
#22 0x9690d594 in ?? ()
#23 0x96907e9c in ?? ()
#24 0x9690d12c in ?? ()
#25 0x9690d5c0 in ?? ()
#26 0x9690d6b0 in ?? ()
#27 0x0006b3b0 in st_insert ()
#28 0x0006b760 in st_delete ()
#29 0x92878710 in ?? ()
#30 0x0006a424 in ruby_qsort ()
#31 0x9367a438 in -[NSWindow sendEvent:] ()
#32 0x93622f5c in -[NSApplication sendEvent:] ()
#33 0x9361a3f0 in -[NSApplication run] ()
#34 0x9370ac1c in NSApplicationMain ()
#35 0x00070448 in ruby_re_compile_pattern ()
#36 0x9690cc7c in ?? ()
#37 0x9690d5c0 in ?? ()
#38 0x96907e9c in ?? ()
#39 0x96903c6c in ?? ()
#40 0x96903cc8 in ?? ()
#41 0x96903d10 in ?? ()
#42 0x0006bc54 in re_set_syntax ()
#43 0x00002d04 in rb_undef_alloc_func ()
#44 0x00002520 in rb_secure ()
#45 0x000023c0 in start ()

with symbols from ruby, rubyCocoa, appKit, coreFoundation, HIToolbox  
and System loaded.

I have googled and looked on the mailing list for any solutions but  
not found anything.  Anyone got any suggestions or solutions?

Dave.

[Rubycocoa-talk] Interface builder problems

[Matt M. <mat...@gm...>]

Hi folks,

I'm having problems with Interface Builder which I'm told are uncommon
so I'm wondering if this is a RubyCocoa related problem.

I have generated a new XCode project as a RubyCocoa project.  Then I
enter Interface Builder add a couple of controls and use Cmd-R to test
the interface.  This all works okay.

When I exit the "scaffolding" application Interface Builder hosts my
tested interface in I find that I have 2 application menus in the menu
bar: Interface Builder but also, inserted between it and the apple
menu, a blank item (about the width of "New Application") with the New
Application menu in it.

About this point, mousing about in the menu, Interface  Builder then
crashes.   From the Crash Reporter logs it appears to be related to
calls to either 'CarbonToNSMenuIndex' or 'AppKitMenuEventHandler'

This is quite reproducable for me but other Interface Builder users
(who are not RubyCocoa users) that I talk to look quizzically at me
when I mention it.

Could this be related to the Nib file generated for a RubyCocoa
project?  Has anyone else seen anything like this?  And, most
important, can anyone help me stop it happening again? ;-)

Thanks,

Matt

--
Matt Mower :: http://matt.blogs.it/

Re: [Rubycocoa-talk] Undefined constants?

[Jonathan P. <jp...@dc...>]

On 22 Sep 2005, at 20:09, Dave Howell wrote:

> On Sep 22, 2005, at 7:21, Jonathan Paisley wrote:
>
>> Ah - my apologies for not checking this. I found the constant in  
>> my rubycocoa, but I'm running the CVS version so didn't think that  
>> it might not have been there before.
>>
>
> A solution proposed for a different problem I was having was to  
> "install darwinports." For this one, will only upgrading via CVS  
> get me the version that has the constants defined? And to what,  
> exactly, would I be upgrading to?

The 0.4.1 release of RubyCocoa does not have the constants. No newer  
version has yet been released. The 'CVS' version refers to whatever  
is the latest code changes made by the developers and committed to  
the CVS system (see, for example [1] and [2] to find out more about  
what CVS is).

Releases are generally made when developers feel the updates made to  
the code are ready for public consumption. This means that the  
current CVS version may contain bugs or other unexpected behaviour.  
However, it's the only way to get newer features before they're given  
a versioned (e.g., 0.4.2) release.

In summary: the CVS version is likely to contain more features and  
also bugfixes against 0.4.1, but may also introduce other bugs that  
may come to bite you.

A temporary work-around would be to give the actual value for the  
constant. For example, NSScreenSaverWindowLevel is 1000. However,  
these 'constants' are defined in such a way by Mac OS X that they are  
derived at run-time (this is the reason that 0.4.1 doesn't support  
them), so it's not something to be relied upon long-term.

Jonathan


[1] http://www.nongnu.org/cvs/
[2] http://cvsbook.red-bean.com/cvsbook.html#Introduction

Re: [Rubycocoa-talk] Undefined constants?

[Dave H. <gr...@gr...>]

On Sep 22, 2005, at 7:21, Jonathan Paisley wrote:
> Ah - my apologies for not checking this. I found the constant in my 
> rubycocoa, but I'm running the CVS version so didn't think that it 
> might not have been there before.

A solution proposed for a different problem I was having was to 
"install darwinports." For this one, will only upgrading via CVS get me 
the version that has the constants defined? And to what, exactly, would 
I be upgrading to?

Re: [Rubycocoa-talk] Undefined constants?

[Jonathan P. <jp...@dc...>]

>>
>> (1) Reference OSX:: directly rather than OSX::NSWindow::
>> (2) Spell NSScreenSaverWindowLevel correctly :)
>>
>>     NScreenSaverWindowLevel
>> vs.
>>     NSScreenSaverWindowLevel
>
> and..  The version 0.4.1 or earlier does not support constants about
> WindowLevel for a technical reason. The constants are available in
> CVS later 2005-07-16.

Ah - my apologies for not checking this. I found the constant in my  
rubycocoa, but I'm running the CVS version so didn't think that it  
might not have been there before.

Re: [Rubycocoa-talk] Here's a puzzle

[kimura w. <ki...@us...>]

Hi,

Wed, 21 Sep 2005 23:56:07 +0100, Jonathan Paisley wrote:
>
>On 21 Sep 2005, at 23:36, Matt Mower wrote:
>
>> Irulan:~ matt$ irb -r osx/cocoa
>> /opt/local/lib/ruby/site_ruby/1.8/powerpc-darwin8.1.0/ 
>> rubycocoa.bundle:
>> [BUG] Bus Error
>> ruby 1.8.2 (2004-12-25) [powerpc-darwin8.1.0]
>>
>> Abort trap
>> Irulan:~ matt$ irb
>> irb(main):001:0> require 'osx/cocoa'
>> => true
>> irb(main):002:0>
>>
>> MacOSX10.4.2, anyone?
>
>It's a bug in CoreFoundation that's triggered by the presence of  
>command line arguments.
>
>More detail in this message (posted by me :) and others in the thread  
>from ruby-talk:
>
>    http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/142893
>
>I *think* a workaround should be in 1.8.3.
>

I think so. This problem occurs with other extension libraries, too.

It's a immediate solution by modification of "irb.rb" in 
{prefix}/lib/ruby/1.8, but this modification effects a bit
initialization process of irb.

-----
--- irb.rb.org  2005-04-20 04:24:56.000000000 +0900
+++ irb.rb      2005-09-22 21:45:11.000000000 +0900
@@ -49,9 +49,9 @@
 
   # initialize IRB and start TOP_LEVEL irb
   def IRB.start(ap_path = nil)
-    $0 = File::basename(ap_path, ".rb") if ap_path
 
     IRB.setup(ap_path)
+    $0 = File::basename(ap_path, ".rb") if ap_path
 
     if @CONF[:SCRIPT]
       irb = Irb.new(nil, @CONF[:SCRIPT])
-----

-- 
kimura wataru

Re: [Rubycocoa-talk] Undefined constants?

[kimura w. <ki...@us...>]

Hi,

Thu, 22 Sep 2005 11:23:01 +0100, Jonathan Paisley wrote:
>On 22 Sep 2005, at 1:21, Dave Howell wrote:
>
>> I'm trying to put images on an otherwise blank screen. The  
>> following code should do that, however, it errors out with  
>> "uninitialized constant OSX::NScreenSaverWindowLevel" if the two  
>> lines that are commented out are enabled.
>>
>>         #windowLevel = (OSX::NSWindow::NScreenSaverWindowLevel) #  
>> this fails
>>
>> How do I get those constants defined?
>
>(1) Reference OSX:: directly rather than OSX::NSWindow::
>(2) Spell NSScreenSaverWindowLevel correctly :)
>
>     NScreenSaverWindowLevel
>vs.
>     NSScreenSaverWindowLevel
>
>

and..  The version 0.4.1 or earlier does not support constants about 
WindowLevel for a technical reason. The constants are available in
CVS later 2005-07-16.


-- 
kimura wataru

Re: [Rubycocoa-talk] Undefined constants?

[Jonathan P. <jp...@dc...>]

On 22 Sep 2005, at 1:21, Dave Howell wrote:

> I'm trying to put images on an otherwise blank screen. The  
> following code should do that, however, it errors out with  
> "uninitialized constant OSX::NScreenSaverWindowLevel" if the two  
> lines that are commented out are enabled.
>
>         #windowLevel = (OSX::NSWindow::NScreenSaverWindowLevel) #  
> this fails
>
> How do I get those constants defined?

(1) Reference OSX:: directly rather than OSX::NSWindow::
(2) Spell NSScreenSaverWindowLevel correctly :)

     NScreenSaverWindowLevel
vs.
     NSScreenSaverWindowLevel

[Rubycocoa-talk] Undefined constants?

[Dave H. <gr...@gr...>]

I'm trying to put images on an otherwise blank screen. The following  
code should do that, however, it errors out with "uninitialized  
constant OSX::NScreenSaverWindowLevel" if the two lines that are  
commented out are enabled.

class PictureDisplay < OSX::NSWindowController
	def init()
		screenRect = OSX::NSScreen.screens.objectAtIndex(0).frame
		mainWindow = OSX::NSWindow.alloc
		displayScreen = OSX::NSScreen.screens.objectAtIndex(0)
		windowMask = OSX::NSBorderlessWindowMask
		windowBacking = OSX::NSBackingStoreRetained
		 
mainWindow.initWithContentRect_styleMask_backing_defer_screen(screenRect 
, windowMask, windowBacking, nil, displayScreen)
		#windowLevel = (OSX::NSWindow::NScreenSaverWindowLevel) # this fails
		#mainWindow.setLevel(windowLevel)
		mainWindow.setBackgroundColor(OSX::NSColor.blackColor)
		mainWindow.makeKeyAndOrderFront_
		return self
	end
end
	
How do I get those constants defined?

Re: [Rubycocoa-talk] Here's a puzzle

[Jonathan P. <jp...@dc...>]

On 21 Sep 2005, at 23:36, Matt Mower wrote:

> Irulan:~ matt$ irb -r osx/cocoa
> /opt/local/lib/ruby/site_ruby/1.8/powerpc-darwin8.1.0/ 
> rubycocoa.bundle:
> [BUG] Bus Error
> ruby 1.8.2 (2004-12-25) [powerpc-darwin8.1.0]
>
> Abort trap
> Irulan:~ matt$ irb
> irb(main):001:0> require 'osx/cocoa'
> => true
> irb(main):002:0>
>
> MacOSX10.4.2, anyone?

It's a bug in CoreFoundation that's triggered by the presence of  
command line arguments.

More detail in this message (posted by me :) and others in the thread  
from ruby-talk:

    http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/142893

I *think* a workaround should be in 1.8.3.

Hope that helps
Jonathan

[Rubycocoa-talk] Here's a puzzle

[Matt M. <mat...@gm...>]

Irulan:~ matt$ irb -r osx/cocoa
/opt/local/lib/ruby/site_ruby/1.8/powerpc-darwin8.1.0/rubycocoa.bundle:
[BUG] Bus Error
ruby 1.8.2 (2004-12-25) [powerpc-darwin8.1.0]

Abort trap
Irulan:~ matt$ irb
irb(main):001:0> require 'osx/cocoa'
=3D> true
irb(main):002:0>

MacOSX10.4.2, anyone?

Matt

--
Matt Mower :: http://matt.blogs.it/

Re: [Rubycocoa-talk] generate_yaml_index.rb

[Matt M. <mat...@gm...>]

On 19/09/05, kimura wataru <ki...@us...> wrote:
> The sample applications except "SimpleApp.app" are provided as source.
> To run a sample, we must build an app with Xcode (or `make' command on
> some samples that has "Makefile").
>

Thanks Kimura, it was my bad for not spotting the English.lproj file ;-)

Regards,

Matt

--=20
Matt Mower :: http://matt.blogs.it/

Re: [Rubycocoa-talk] generate_yaml_index.rb

[kimura w. <ki...@us...>]

Hi,

The sample applications except "SimpleApp.app" are provided as source.
To run a sample, we must build an app with Xcode (or `make' command on
some samples that has "Makefile").

Sun, 18 Sep 2005 18:57:52 +0100, Matt Mower wrote:
>Hi guys,
>
>Quite a few of the sample apps I've tried to run (e.g.
>CurrencyConverter, simpleapp, ...) fail in rb_main.rb with the
>following kind of error:
>
>Irulan:~/build/ruby-cocoa/src/sample/CurrencyConverter matt$ ruby rb_main.rb 
>rb_main.rb:9:in `require': No such file to load --
>generate_yaml_index.rb (LoadError)
>        from rb_main.rb:9:in `rb_main_init'
>        from rb_main.rb:8:in `each'
>        from rb_main.rb:8:in `rb_main_init'
>        from rb_main.rb:14
>
>This generate_yam_index business appears to be related to RubyGems and
>running a gem server but I can't fathom the relevance to RubyCocoa.
>
>Can anyone enlighten me?
>


-- 
kimura wataru

[Rubycocoa-talk] generate_yaml_index.rb

[Matt M. <mat...@gm...>]

Hi guys,

Quite a few of the sample apps I've tried to run (e.g.
CurrencyConverter, simpleapp, ...) fail in rb_main.rb with the
following kind of error:

Irulan:~/build/ruby-cocoa/src/sample/CurrencyConverter matt$ ruby rb_main.r=
b=20
rb_main.rb:9:in `require': No such file to load --
generate_yaml_index.rb (LoadError)
        from rb_main.rb:9:in `rb_main_init'
        from rb_main.rb:8:in `each'
        from rb_main.rb:8:in `rb_main_init'
        from rb_main.rb:14

This generate_yam_index business appears to be related to RubyGems and
running a gem server but I can't fathom the relevance to RubyCocoa.

Can anyone enlighten me?

M

--=20
Matt Mower :: http://matt.blogs.it/

Re: [Rubycocoa-talk] Problem with RubyCocoa install

[kimura w. <ki...@us...>]

Hi,

I merged your fix to CVS. Now, the tests will run without any error.
Thanks!


Sat, 17 Sep 2005 13:19:35 +0100, Jonathan Paisley wrote:
>
>On 17 Sep 2005, at 10:57, Matt Mower wrote:
>>
>> which I don't really understand since line 68 is passing 'guess1' to
>> respond_to?  I didn't get any hits on a google search.
>
>Heh - you beat me to posting about this. After mentioning CVS  
>yesterday I realised that I'd had to make the patch below.
>
>The line in question, from:
>
>/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/ 
>objc/cocoa_macros.rb:68
>

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Matt M. <mat...@gm...>]

On 17/09/05, Tim Lucas <t....@to...> wrote:
> On 17/09/2005, at 7:56 AM, Dave howell wrote:
>=20
>=20
> > Let's try again....nope, my installation directory is now
> > mysteriously corrupted. I must now erase it and download a whole
> > new copy of Ruby.  I guess I'll try the package that 'discordantus'
> > put together. After I finish banging my head against the wall.
> >
>=20
> Why not install from darwinports?
>=20

What Tim said.

M

--=20
Matt Mower :: http://matt.blogs.it/

Re: [Rubycocoa-talk] New ways to not install Ruby things.

[Tim L. <t....@to...>]

On 17/09/2005, at 7:56 AM, Dave howell wrote:


> Let's try again....nope, my installation directory is now  
> mysteriously corrupted. I must now erase it and download a whole  
> new copy of Ruby.  I guess I'll try the package that 'discordantus'  
> put together. After I finish banging my head against the wall.
>

Why not install from darwinports?

Step 1) Install darwinports
Step 2) sudo port install ruby rails rubygems
Step 3) there is no step 3 :)

Rubycocoa and anything else can use the darwinports ruby install just  
fine by adding /opt/local/bin to your path and changing the shebangs  
to '/usr/bin/env ruby'

... oh, and darwinports doesn't clutter your system -- everything  
sits under /opt/local/ so you can try it out w/o fear of nuking your  
default system libraries.

-- tim lucas

Re: [Rubycocoa-talk] Ruby/Cocoa and CoreData

[Rupert B. <rup...@fr...>]

Jonathan,
Thanks for the tip, I will try my stuff out without subclassing.

Rupert



> I think that currently it's not possible to subclass a Ruby class  
> that derives from OSX::NSObject, due to some implementation details  
> in the creation of Objective C class corresponding to the Ruby class.
>
>