rubycocoa-talk — talking about RubyCocoa

[Rubycocoa-talk] Re: Rubycocoa-talk digest, Vol 1 #53 - 2 msgs

[harry <hv...@ch...>]

> Message: 1
> From: Kevin Bullock <krb...@ma...>
> Date: Fri, 28 May 2004 00:41:41 -0500
> To: rub...@li...
> Subject: [Rubycocoa-talk] Re: Rubycocoa-talk digest, Vol 1 #52 - 1 msg
> Reply-To: rub...@li...

> [...]

> In doing so, you removed the things that disappeared from Cocoa in=20
> 10.3, but you didn't add support for any of the new things that=20
> appeared. To do that, all you have to do is re-run the script that=20
> generates the class bindings:
>
> % cd framework/src/objc/cocoa/ && ruby gen_cocoa_wrapper.rb
>
> Then re-configure and re-build as normal. That should get you going.

Thx for the tip, but unfortunately it didn't solve my problem ... I get  
the same error-message mentioned before ...

If I do the tutorial on Apple's ADC-site  
(http://developer.apple.com/cocoa/cocoabindings.html) as a  
ruby-project, and run from Xcode, I get a different message:

2004-05-30 12:49:15.280 bindprefs[3209] *** -[NSCFNumber bytes]:  
selector not recognized
/Users/hvs/tmp/bindprefs/build/bindprefs.app/Contents/Resources/ 
rb_main.rb:19:in `NSApplicationMain': NSApplicationMain -  
NSInvalidArgumentException - *** -[NSCFNumber bytes]: selector not  
recognized (OSX::OCException)
	from  
/Users/hvs/tmp/bindprefs/build/bindprefs.app/Contents/Resources/ 
rb_main.rb:19

The Objective-C version is working fine.


Is Cocoa Bindings working with RubyCocoa? Any successtories amongst the  
listas?

If so, it may just be a shaky install on my system ...

Harry

RE: [Rubycocoa-talk] Re: Rubycocoa-talk digest, Vol 1 #52 - 1 ms

[John N. A. <li...@li...>]

On 28-May-04 Kevin Bullock wrote:
> In doing so, you removed the things that disappeared from Cocoa in 
> 10.3, but you didn't add support for any of the new things that 
> appeared. To do that, all you have to do is re-run the script that 
> generates the class bindings:
> 
> % cd framework/src/objc/cocoa/ && ruby gen_cocoa_wrapper.rb
> 
> Then re-configure and re-build as normal. That should get you going.
> 
Is this taken care of by the application of the posted patch and then
rebuilding?

john
------------------------------------
John N. Alegre                   o
Andante Systems               o
eCommerce Consulting       o
Custom Web Development <*{{{{}><
------------------------------------ 

[Rubycocoa-talk] Re: Rubycocoa-talk digest, Vol 1 #52 - 1 msg

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

Hi there=97 (reply below)

On May 27, 2004, at 10:44 PM,=20
rub...@li... wrote:

> From: harry <hv...@ch...>
> Date: Thu, 27 May 2004 08:43:25 +0200
> To: rub...@li...
> Subject: [Rubycocoa-talk] Re: Re: Cocoa Bindings support?
> Reply-To: rub...@li...
>
>
> On 27-mei-04, at 5:46, rub...@li...
> wrote:
>
>> From: Chris Thomas <cj...@cj...>
>> Subject: Re: [Rubycocoa-talk] Cocoa Bindings support?
>> Date: Wed, 26 May 2004 13:45:49 -0700
>> To: rub...@li...
>> Reply-To: rub...@li...
>>
>> If you build RubyCocoa yourself, it will contain support for all of=20=

>> the
>> new Panther Cocoa classes. The build process scans the Cocoa headers=20=

>> to
>> generate the Ruby interfaces.
>>
>> Chris
>
> I did build RubyCocoa myself, because at the time the binary install
> didn't work; I had to remove some deprecated constants from
> framework/src/objc/cocoa/rb_NSGraphics.m and rb_NSSavePanel.m in order
> to get it build. After that, it works fine, untill I tried my hands on
> Cocoa Bindings, new in Panther.

In doing so, you removed the things that disappeared from Cocoa in=20
10.3, but you didn't add support for any of the new things that=20
appeared. To do that, all you have to do is re-run the script that=20
generates the class bindings:

% cd framework/src/objc/cocoa/ && ruby gen_cocoa_wrapper.rb

Then re-configure and re-build as normal. That should get you going.

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

[Rubycocoa-talk] Re: Re: Cocoa Bindings support?

[harry <hv...@ch...>]

On 27-mei-04, at 5:46, rub...@li...  
wrote:

>
> Today's Topics:
>
>    1. Cocoa Bindings support? (harry)
>    2. Re: Cocoa Bindings support? (Chris Thomas)
>
> --__--__--
>
> Message: 1
> To: rub...@li...
> From: harry <hv...@ch...>
> Date: Wed, 26 May 2004 22:08:53 +0200
> Subject: [Rubycocoa-talk] Cocoa Bindings support?
> Reply-To: rub...@li...
>
>
> Hi all,
> recently I started experimenting with the new Controller layer in

[...]

> --__--__--
>
> Message: 2
> From: Chris Thomas <cj...@cj...>
> Subject: Re: [Rubycocoa-talk] Cocoa Bindings support?
> Date: Wed, 26 May 2004 13:45:49 -0700
> To: rub...@li...
> Reply-To: rub...@li...
>
>
> --Apple-Mail-41--77032666
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain;
> 	charset=US-ASCII;
> 	format=flowed
>
> If you build RubyCocoa yourself, it will contain support for all of the
> new Panther Cocoa classes. The build process scans the Cocoa headers to
> generate the Ruby interfaces.
>
> Chris

I did build RubyCocoa myself, because at the time the binary install  
didn't work; I had to remove some deprecated constants from  
framework/src/objc/cocoa/rb_NSGraphics.m and rb_NSSavePanel.m in order  
to get it build. After that, it works fine, untill I tried my hands on  
Cocoa Bindings, new in Panther.

My dummy-app is the demo-project found at:

  	http://www.macdevcenter.com/pub/a/mac/2004/04/06/cocoa.html?page=1

I decided to do it with ruby and then the Book-class will be:

	def Book < OSX::NSObject
    		attr_accessor :title
    		attr_accessor :author
	end

All fine, untill I try to run the app from Xcode, which shows this  
error:

/Users/hvs/tmp/bibliotecha/build/bibliotecha.app/Contents/Resources/ 
rb_main.rb:19:in
`NSApplicationMain': NSApplicationMain - NSUnknownKeyException -
[<Book 0x4f2540> valueForUndefinedKey:]: this class is not key value
coding-compliant for the key title. (OSX::OCException)
  from  
/Users/hvs/tmp/bibliotecha/build/bibliotecha.app/Contents/Resources/ 
rb_main.rb:19

Am I missing something?

Harry

Re: [Rubycocoa-talk] Cocoa Bindings support?

[Chris T. <cj...@cj...>]

If you build RubyCocoa yourself, it will contain support for all of the 
new Panther Cocoa classes. The build process scans the Cocoa headers to 
generate the Ruby interfaces.

Chris

On May 26, 2004, at 1:08 PM, harry wrote:

>
> Hi all,
> recently I started experimenting with the new Controller layer in 
> OSX-Panther, and like it a lot; when I created some dummy 
> Ruby1.8/RubyCocoa 0.4.0 project using Cocoa Bindings, I got some 
> errors indicating that Cocoa Bindings are not yet supported in 
> RubyCocoa; after some investigation in the source-code, it is my 
> understanding that it was build under Jaguar, and as such for Panther 
> missing some wrapper classes, found under framework/src/objc/cocoa, 
> and perhaps more supporting code.
> Is this the case?
>
> Will this otherwise great package be updated in the foreseeable future 
> to support  these and other new features in Panther's Cocoa version?
>
> thx, Harry
>
>
> PS: if needs be I'm willing to contribute; I'd like to see this 
> package stay updated with OSX/Cocoa-versions ...
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 
> 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>

[Rubycocoa-talk] Cocoa Bindings support?

[harry <hv...@ch...>]

Hi all,
recently I started experimenting with the new Controller layer in 
OSX-Panther, and like it a lot; when I created some dummy 
Ruby1.8/RubyCocoa 0.4.0 project using Cocoa Bindings, I got some errors 
indicating that Cocoa Bindings are not yet supported in RubyCocoa; 
after some investigation in the source-code, it is my understanding 
that it was build under Jaguar, and as such for Panther missing some 
wrapper classes, found under framework/src/objc/cocoa, and perhaps more 
supporting code.
Is this the case?

Will this otherwise great package be updated in the foreseeable future 
to support  these and other new features in Panther's Cocoa version?

thx, Harry


PS: if needs be I'm willing to contribute; I'd like to see this package 
stay updated with OSX/Cocoa-versions ...

Re: [Rubycocoa-talk] Self-contained .app bundle?

[Chris T. <cj...@cj...>]

On Apr 7, 2004, at 11:33 AM, Phil Tomson wrote:

> On Wed, 7 Apr 2004, John Platte wrote:
>
>> It looks like it's possible to create a completely self-contained .app
>> bundle that contains Ruby on-board. These pages suggest that libruby
>> and RubyCocoa could live in an app bundle's Contents/Frameworks
>> directory:
>>
>> * http://www.imasy.or.jp/~hisa/mac/rubycocoa/changelog.html
>> * http://cocoadevcentral.com/articles/000042.php
>> * http://qin.laya.com/tech_coding_help/dylib_linking.html
>>
>> Can folks on this list contribute toward a recipe for building the 
>> Ruby
>> and RubyCocoa dylibs appropriately? I will collect responses on Ruby
>> Garden at
>>
>> http://www.rubygarden.org/ruby?BundleRubyExecutableInMacOSX
>>
>
> I don't have anything to contribute yet, but I am very eager to learn 
> how
> to do this.  I would like to develop RubyCocoa apps and be able to
> distribute them to others who may not have the RubyCocoa bindings (or 
> may
> not have the latest version of Ruby installed).

It goes something like this:

Start by getting the dylibs linked correctly, then link the executable 
against them, and then copy them to the executable.

Linking the libraries:
Set the install name of RubyCocoa.framework to 
"@executable_path/../Frameworks".
Set the install name of libruby.dylib to "@executable_path/".

Copying:
Copy the built libruby.dylib into /YourApp.app/Contents/MacOS/
And copy the built RubyCocoa.framework into 
/YourApp.app/Contents/Frameworks/
You can do this easily in Xcode by adding a couple of Copy Files build 
phases to your target.

Chris

Re: [Rubycocoa-talk] Self-contained .app bundle?

[Phil T. <pt...@ar...>]

On Wed, 7 Apr 2004, John Platte wrote:

> It looks like it's possible to create a completely self-contained .app 
> bundle that contains Ruby on-board. These pages suggest that libruby 
> and RubyCocoa could live in an app bundle's Contents/Frameworks 
> directory:
> 
> * http://www.imasy.or.jp/~hisa/mac/rubycocoa/changelog.html
> * http://cocoadevcentral.com/articles/000042.php
> * http://qin.laya.com/tech_coding_help/dylib_linking.html
> 
> Can folks on this list contribute toward a recipe for building the Ruby 
> and RubyCocoa dylibs appropriately? I will collect responses on Ruby 
> Garden at
> 
> http://www.rubygarden.org/ruby?BundleRubyExecutableInMacOSX
> 

I don't have anything to contribute yet, but I am very eager to learn how 
to do this.  I would like to develop RubyCocoa apps and be able to 
distribute them to others who may not have the RubyCocoa bindings (or may 
not have the latest version of Ruby installed).

Phil

[Rubycocoa-talk] Self-contained .app bundle?

[John P. <joh...@ni...>]

It looks like it's possible to create a completely self-contained .app 
bundle that contains Ruby on-board. These pages suggest that libruby 
and RubyCocoa could live in an app bundle's Contents/Frameworks 
directory:

* http://www.imasy.or.jp/~hisa/mac/rubycocoa/changelog.html
* http://cocoadevcentral.com/articles/000042.php
* http://qin.laya.com/tech_coding_help/dylib_linking.html

Can folks on this list contribute toward a recipe for building the Ruby 
and RubyCocoa dylibs appropriately? I will collect responses on Ruby 
Garden at

http://www.rubygarden.org/ruby?BundleRubyExecutableInMacOSX

so we can all keep it updated and refer to it for FAQ's. That page has 
what I know so far. The rest of the message is what's currently on the 
wiki page:

=====

The libruby.X.X.X.dylib apparently needs to go in the 
Example.app/Contents/Frameworks/ directory. So I'm guessing we need to 
do:

  ./configure --libdir = @executable_path/../Frameworks ? /

But then what? Where does the libruby.X.X.X.dylib go at build time? And 
then do we just copy it straight into the bundle's Contents/Frameworks?

Also, how then to start a Ruby script? Do we embed the interpreter and 
use a C call to load our rb_main.rb, like described in ProgrammingRuby 
in <http://www.rubycentral.com/book/ext_ruby.html#S6>?

RubyCocoa too

The 2003-07-25 entry in [[RubyCocoa's changelog]] says it supports 
living in an .app bundle like this. Could someone write down how to do 
this? It looks like it involves tweaking the project in Project Builder 
/ Xcode.

-- 
Ryan "John" Platte
Custom services, NIKA Consulting
http://nikaconsulting.com/

[Rubycocoa-talk] multiple definitions of symbol _rb_obj_clone

[Phil T. <pt...@ar...>]

I installed ruby 1.8.1 from darwinports, then I installed rb_cocoa-0.4.0 
from the ports as well.

I tried one of the script examples on the RubyCoca page and I get:

phil% ruby -v
ruby 1.8.1 (2003-12-25) [powerpc-darwin]
[phils-Computer:~] phil% ruby speak.rb 
dyld: ruby multiple definitions of symbol _rb_obj_clone
/opt/local/lib/libruby.dylib(object.o) definition of _rb_obj_clone
/Library/Frameworks/RubyCocoa.framework/Versions/A/RubyCocoa(single 
module) definition of _rb_obj_clone
Trace/BPT trap

Any ideas?

(I'm running OS X 10.3 )


Phil

[Rubycocoa-talk] Thread issues

[Kevin B. <kbu...@ri...>]

I've got a bit of a problem with interactions between RubyCocoa and  
Ruby's threading. I've seen this in a number of instances:

2004-02-05 11:30:17.592 sim[2208] *** Exception handlers were not  
properly removed. Some code has jumped or returned out of an  
NS_DURING...NS_HANDLER region without using the NS_VOIDRETURN or  
NS_VALUERETURN macros.
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/ 
objc/oc_wrapper.rb:17: [BUG] Bus Error

My suspicion is that the thread scheduler is being run before an ObjC  
method completes... but I'm not sure, because I haven't had time to  
delve into the runtime code.

Does anyone know what this is about, or have a fix?

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

Re: [Rubycocoa-talk] NSSortDescriptor

[Chris T. <ch...@m-...>]

On Jan 31, 2004, at 2:16 PM, andi wrote:

> is the foundation kit class NSSortDescriptor available in rubycocoa?

It should be, although I haven't tried it. Are you having trouble with 
it?

> (and: is this nice project still alive? I'd hate to see it dying..)

I suspect it's just that the author is extremely busy at his day job, 
so new development occurs when time is available. :) I don't think 
there's any danger of the project permanently disappearing.

Chris

[Rubycocoa-talk] NSSortDescriptor

[andi <ap...@ur...>]

is the foundation kit class NSSortDescriptor available in rubycocoa?

(and: is this nice project still alive? I'd hate to see it dying..)

a

[Rubycocoa-talk] printing and NSRangePointer

[andi <ap...@ur...>]

hi,

I am writing an application with rubycocoa and until now it has been a 
smooth experience.

I ran into one obstacle I could not solve yet:

I added printing support and want to use custom pagination using a 
subclass of NSView implementing the #knowsPageRange method. The method 
according to the cocoa documentation should look something like this:

- (BOOL)knowsPageRange:(NSRangePointer)range {
     range->location = 1;
     range->length = 7
     return YES;
}

.. which would cause 7 pages to be printed.

the problem is that i cannot deference the NSRangePointer to set the 
location and length  fields in ruby. certainly this ruby version of the 
above method does not work:

     def knowsPageRange(range)
         range.location = 1
         range.length = 7
         return 1
     end

the range parameter is an OSX::ObjcPtr instance, which is all too 
generic i think and has no methods to reconstruct the NSRange object i 
am interested in.

can anybody help, please? if the solution is obvious, please forgive my 
ignorance, I am still learning ruyb AND cocoa..

andi

[Rubycocoa-talk] [patch] RubyCocoa apps don't run if the executable pathname contains whitespace

[Chris T. <ch...@m-...>]

Looks like a bug in Dir.glob in 1.6.8. The enclosed patch is against 
the /template directory only, I haven't checked the examples yet.

Although this seems to be fixed in 1.8.1, Panther includes a 1.6.8 
libruby.dylib. It would be nice to be able to distribute smaller 
applications by embedding the RubyCocoa framework and linking against 
libruby.dylib. Because libruby is part of the BSD subset of the system, 
this isn't really a guarantee the resulting app will work on a random 
end-user system or continue to work in the future -- but it's still 
convenient for ad-hoc applications.

Chris

irb(main):001:0> VERSION
=> "1.6.8"
irb(main):002:0> Dir.chdir "/Users/chris/Code/Whisper/Examples"
=> 0
irb(main):003:0> Dir.entries("XML Compiler")
=> [".", "..", "CVS", "Read Me.txt", "Resources", "Source", "XML 
Compiler Data", "XML Compiler.mcp"]
irb(main):004:0> Dir.glob("XML Compiler/*")
=> []
irb(main):005:0> Dir.entries("StringTableBuilder")
=> [".", "..", "CVS", "Read Me.txt", "Resources", "Source", 
"StringTableBuilder Data", "StringTableBuilder.mcp"]
irb(main):006:0> Dir.glob("StringTableBuilder/*")
=> ["StringTableBuilder/CVS", "StringTableBuilder/Read Me.txt", 
"StringTableBuilder/Resources", "StringTableBuilder/Source", 
"StringTableBuilder/StringTableBuilder Data", 
"StringTableBuilder/StringTableBuilder.mcp"]

Fixed in 1.8.1:

irb(main):002:0> VERSION
=> "1.8.1"
irb(main):003:0> Dir.chdir "/Users/chris/Code/Whisper/Examples"
=> 0
irb(main):004:0> Dir.entries("XML Compiler")
=> [".", "..", "CVS", "Read Me.txt", "Resources", "Source", "XML 
Compiler Data", "XML Compiler.mcp"]
irb(main):005:0> Dir.glob("XML Compiler/*")
=> ["XML Compiler/CVS", "XML Compiler/Read Me.txt", "XML 
Compiler/Resources", "XML Compiler/Source", "XML Compiler/XML Compiler 
Data", "XML Compiler/XML Compiler.mcp"]

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

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

At Thu, 1 Jan 2004 17:35:27 -0700,
Rod Schmidt wrote:
> I was wondering how the below would work with your own class and with
> calling methods with arguments. For example I have a class called
> Engine written in Ruby with a constructor that takes a file name. How
> do I get the class to pass to initWithRubyObject and how do I pass
> arguments to a method. Is it as simple as [class new: filename] or
> [[class alloc] init: filename]; Basically how do ruby's allocation
> scheme translate when you're trying to use it as an objective-c class.

I tried it now. Then I noticed that there is no way to pass
arguments as you say, sorry.

I want to keep developing rubycocoa for totally redesigning and
refactoring including the above issue. But it's impossible to do
so immediately, without a sponsor for a cost, because I have to do
many real work.

thanks,
--
Hisa

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

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

  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.

I was wondering how the below would work with your own class and with 
calling methods with arguments. For example I have a class called 
Engine written in Ruby with a constructor that takes a file name. How 
do I get the class to pass to initWithRubyObject and how do I pass 
arguments to a method. Is it as simple as [class new: filename] or 
[[class alloc] init: filename]; Basically how do ruby's allocation 
scheme translate when you're trying to use it as an objective-c class.

Rod


 > 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

[Rubycocoa-talk] reading property lists in rubycocoa

[Ed H. <ed...@fa...>]

I'm very new to rubycocoa, and I'm not sure how to interpret this error.

Here is a script which demonstrates the problem:
--
#!/usr/bin/ruby

require 'osx/cocoa'

data=OSX::NSString.stringWithContentsOfFile('HTTPCookies.plist')
mo=OSX::NSPropertyListMutableContainersAndLeaves
fmt=OSX::NSPropertyListXMLFormat_v1_0
errst=OSX::NSString.alloc.init

pl=OSX::NSPropertyListSerialization.propertyListFromData_mutabilityOptio 
n_format_errorDescription(data,mo,fmt,errst)

puts pl.inspect

--

It fails with this error:

bash-2.05a$ ./plist.rb
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/ 
objc/oc_wrapper.rb:17:in `ocm_send':  
NSPropertyListSerialization#propertyListFromData:mutabilityOption:format 
:errorDescription: - cannot convert the argument #2 as '^i' to NS  
argument. (OSX::OCDataConvException)
         from  
/Library/Frameworks/RubyCocoa.framework/Versions/A/Resources/ruby/osx/ 
objc/oc_wrapper.rb:17:in `method_missing'
         from ./plist.rb:10

I'm not sure what I'm doing wrong here.  I assume argument #2 refers to  
mo, the mutability option, and I've determined that its value is 1.   
(The value of fmt is 100.)

I tried wrapping those arguments up in conversions to NSNumber, like  
this:

mo=OSX::NSNumber.numberWithInt(OSX::NSPropertyListMutableContainersAndLe 
aves)
fmt=OSX::NSNumber.numberWithInt(OSX::NSPropertyListXMLFormat_v1_0)

But I get the same error.

[Rubycocoa-talk] How to use Delegates?

[<pet...@ka...>]

Hi,

Could someone provide me an example of how to properly use/specify a
delegate to the NSSpeechSynthesizer class?  I can't seem to get any
delegate method that has more than one argument to work.  For example,
here is one of the several methods that I've tried:

class MyDelegate < OSX::NSObject
  def speechSynthesizer_didFinishSpeaking_(sender, flag)
    puts "Made it to the delegate"
  end
end

synth = OSX::NSSpeechSynthesizer.alloc.init
synth.setDelegate(MyDelegate.alloc.init)
synth.startSpeakingString("This is a test")

sleep 10

Thanks!
Pete

Re: [Rubycocoa-talk] can't set up because of more than one Project Builder project

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

At Fri, 5 Dec 2003 11:36:40 +1100,
Sven Schott wrote:
> I found that the RubyCocoa.frmwk.pbproj is empty(from CVS) and I 
> deleted it(shock!). I installed it on 10.3 with the installed ruby and 
> it works frin . I also applied the 10.3 panther patch.
> 
> http://homepage.mac.com/kimuraw/archive/rubycocoa-10.3.patch.gz
> 
> Works well. I also included the framework using Xcode and I ran the app 
> on a computer that didn't have rubycocoa installed. yay!.

A message about the issue from kimuraw-san is attached to the following:

------- Forwarded Message

>'system xcodebuild' failed
>try 'ruby install.rb --help' for usage

 Sorry, the pacth has a bug in install.rb. 

fixed setup_dir_framework() in install.rb
----
  def setup_dir_framework( relpath )
    if test(?x, '/usr/bin/xcodebuild') then
      command 'xcodebuild'
    else
      command 'pbxbuild'
    end
  end
----

 I've replaced the pacth with a fixed one.

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



------- End of Forwarded Message

-- 
FUJIMOTO Hisakuni

Re: [Rubycocoa-talk] can't set up because of more than one Project Builder project

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

At Fri, 5 Dec 2003 11:36:40 +1100,
Sven Schott wrote:
> I found that the RubyCocoa.frmwk.pbproj is empty(from CVS) and I 
> deleted it(shock!). I installed it on 10.3 with the installed ruby and 
> it works frin . I also applied the 10.3 panther patch.
> 
> http://homepage.mac.com/kimuraw/archive/rubycocoa-10.3.patch.gz
> 
> Works well. I also included the framework using Xcode and I ran the app 
> on a computer that didn't have rubycocoa installed. yay!.

Thanks Sven-san, 

And now, I prepared branch for Panther into the CVS repository,
named "branch-devel-panther". Kimura-san who is an author of the
patch is working on the branch.

Please be aware that development on the branch considers only
Panther fundamentally.

checkout devel-panther branch:

  cvs -z3 -d:pserver:ano...@cv...:/cvsroot/rubycocoa co -P -r branch-devel-panther

-- 
FUJIMOTO Hisakuni

Re: [Rubycocoa-talk] can't set up because of more than one Project Builder project

[Sven S. <sve...@co...>]

I found that the RubyCocoa.frmwk.pbproj is empty(from CVS) and I 
deleted it(shock!). I installed it on 10.3 with the installed ruby and 
it works frin . I also applied the 10.3 panther patch.

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

Works well. I also included the framework using Xcode and I ran the app 
on a computer that didn't have rubycocoa installed. yay!.

Sven
On 05/12/2003, at 11:12 AM, Rincon Jinn wrote:

>
> I got rubycocoa from cvs and ruby 1.8.1 installed.
>
> Panther 10.3.1 installed.
>
> [gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% ruby --version
> ruby 1.8.1 (2003-10-31) [powerpc-darwin]
> [gavin-unix:ruby/rubyCocoa/rubycocoa] gjin%
>
>
>
> [gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% ruby install.rb
> setup
> install.rb: entering setup phase...
> ---> framework
> /usr/bin/xcodebuild
> xcodebuild
> xcodebuild: Error: the directory
> /Volumes/development/openSource/ruby/rubyCocoa/rubycocoa/framework
> contains more than one Project Builder project (it has 2 of
> them). You will need to specify the project to build with the
> -project option.
> setup failed
> 'system xcodebuild' failed
> try 'ruby install.rb --help' for usage
> [gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% ls -lt framework/
> total 8
> drwxr-xr-x    6 gjin     staff         204 Dec  4 13:23
> RubyCocoa.pbproj
> -rw-r--r--    1 gjin     staff         807 Dec  4 13:23
> post-config.rb
> drwxr-xr-x    5 gjin     staff         170 Dec  4 13:22 src
> drwxr-xr-x    4 gjin     staff         136 Dec  4 13:22 tool
> drwxr-xr-x    6 gjin     staff         204 Dec  4 13:21 CVS
> drwxr-xr-x    4 gjin     staff         136 Dec  4 13:21
> English.lproj
> drwxr-xr-x    3 gjin     staff         102 Dec  4 13:21
> RubyCocoa.frmwk.pbproj
> -rw-r--r--    1 gjin     staff         828 Dec 27  2002
> pre-install.rb
> [gavin-unix:ruby/rubyCocoa/rubycocoa] gjin%
> ________________________________
> 15 Mbytes Free Web-based and  POP3
> Sign up now: http://www.gawab.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for 
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys 
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>

[Rubycocoa-talk] can't set up because of more than one Project Builder project

[Rincon J. <ri...@ga...>]

I got rubycocoa from cvs and ruby 1.8.1 installed.

Panther 10.3.1 installed.

[gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% ruby --version
ruby 1.8.1 (2003-10-31) [powerpc-darwin]
[gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% 



[gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% ruby install.rb
setup
install.rb: entering setup phase...
---> framework
/usr/bin/xcodebuild
xcodebuild
xcodebuild: Error: the directory
/Volumes/development/openSource/ruby/rubyCocoa/rubycocoa/framework
contains more than one Project Builder project (it has 2 of
them). You will need to specify the project to build with the
-project option.
setup failed
'system xcodebuild' failed
try 'ruby install.rb --help' for usage
[gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% ls -lt framework/
total 8
drwxr-xr-x    6 gjin     staff         204 Dec  4 13:23
RubyCocoa.pbproj
-rw-r--r--    1 gjin     staff         807 Dec  4 13:23
post-config.rb
drwxr-xr-x    5 gjin     staff         170 Dec  4 13:22 src
drwxr-xr-x    4 gjin     staff         136 Dec  4 13:22 tool
drwxr-xr-x    6 gjin     staff         204 Dec  4 13:21 CVS
drwxr-xr-x    4 gjin     staff         136 Dec  4 13:21
English.lproj
drwxr-xr-x    3 gjin     staff         102 Dec  4 13:21
RubyCocoa.frmwk.pbproj
-rw-r--r--    1 gjin     staff         828 Dec 27  2002
pre-install.rb
[gavin-unix:ruby/rubyCocoa/rubycocoa] gjin% 
________________________________
15 Mbytes Free Web-based and  POP3
Sign up now: http://www.gawab.com

Re: [Rubycocoa-talk] build problems

[Chris T. <ch...@m-...>]

On Dec 2, 2003, at 5:12 AM, Jim Menard wrote:

> Dan,
>
>> 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.
>
> Could this be a character encoding issue? If the file isn't straight 
> ASCII mightn't that confuse the Ruby parser?

Yes, or it could be line endings as well. The Ruby interpreter does not 
like CR or CR/LF. Bit me at least once.

PB/Xcode defaults to MacRoman and LF or UTF-8 and LF, so it's not 
likely, but you never know.

Chris

--
Essential reading for Americans:
http://www.economist.com/world/na/displayStory.cfm?story_id=2246429

Re: [Rubycocoa-talk] build problems

[Jim M. <ji...@io...>]

Dan,

> 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.

Could this be a character encoding issue? If the file isn't straight 
ASCII mightn't that confuse the Ruby parser?

Jim
-- 
Jim Menard, ji...@io..., http://www.io.com/~jimm/
"Any sufficiently advanced technology is insufficiently documented"
     -- kabdib on slashdot