rubycocoa-talk — talking about RubyCocoa

[Rubycocoa-talk] I too am failing at installation.

[Jeremy N. <jn...@gn...>]

    Alright, I have a fresh install of OS X.  I have used Macports to 
install Ruby, and when I attempt to install RubyCocoa I get the following:

install.rb: entering config phase...
dyld: Symbol not found: __cg_jpeg_resync_to_restart
  Referenced from: 
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
  Expected in: /opt/local/lib/libJPEG.dylib

create ext/rubycocoa/extconf.rb
create framework/GeneratedConfig.xcconfig
create framework/src/objc/Version.h
create tests/Makefile
---> framework
create /Users/eltiare/src/RubyCocoa-0.13.0/framework/src/objc/osx_ruby.h ...
create 
/Users/eltiare/src/RubyCocoa-0.13.0/framework/src/objc/osx_intern.h ...
BSROOT="/Users/eltiare/src/RubyCocoa-0.13.0/framework/bridge-support" 
CFLAGS="" /opt/local/bin/ruby build.rb
Generating BridgeSupport metadata for: CoreFoundation ...
    Collect metadata (13.74782 seconds)
/opt/local/lib/ruby/1.8/rexml/document.rb:186:in `write': undefined 
local variable or method `transitive' for <UNDEFINED> ... 
</>:REXML::Document (NameError)
        from ./gen_bridge_metadata.rb:1516:in `generate_xml'
        from ./gen_bridge_metadata.rb:1516:in `open'
        from ./gen_bridge_metadata.rb:1516:in `generate_xml'
        from ./gen_bridge_metadata.rb:542:in `write'
        from build.rb:106
        from build.rb:50:in `measure'
        from build.rb:104
        from build.rb:62:in `each'
        from build.rb:62
config failed
hook /Users/eltiare/src/RubyCocoa-0.13.0/framework/post-config.rb failed:
'system 
BSROOT="/Users/eltiare/src/RubyCocoa-0.13.0/framework/bridge-support" 
CFLAGS="" /opt/local/bin/ruby build.rb' failed
try 'ruby install.rb --help' for usage

    I have tried everything I can think of (which admittedly is not much 
at this point).  Any hints that would point me in the right direction?

TIA,
Jeremy

[Rubycocoa-talk] rubycocoa and rucola/ruby installed from source

[Stephen B. <ste...@gm...>]

I've got ruby-1.8.6-p111 installed in /usr/local and have had a 
number of troubles installing rubycocoa and rucola.

I did solve them but thought a short narrative might be helpful for 
somebody else with similar issues (and perhaps also for adding to the 
documentation online which describes how to get started).

I'm on macos 10.4.11 using rubygems version 0.9.5.

I saw the announcement about rucola and thought -- "That sounds cool, 
I'd like to try that!"

$ sudo gem install rucola

failed installing rubynode -- the latest rubygems installs 
dependencies automatically so the fact that the error occurred 
installing rubynode might be so obvious.

Checking the page for the rubynode gem showed the problem (so did the 
error message). Setting an environment variable before installing 
rubynode got it installed:

$ RUBY_SOURCE_DIR="/Users/stephen/dev/ruby/src/ruby-1.8.6-p111" sudo 
gem install rubynode
Building native extensions.  This could take a while...
Successfully installed rubynode-0.1.3
1 gem installed

Then installing rucola worked.

$ sudo gem install rucola
Successfully installed rucola-0.0.2
1 gem installed
Installing ri documentation for rucola-0.0.2...
Installing RDoc documentation for rucola-0.0.2...

But after making a new rubycocoa app with rucola and trying to run it 
I got this error:

rake aborted!
no such file to load -- osx/cocoa

Ooops, rubycocoa  wasn't just a gem dependency!

So first I downloaded the dmg and ran it -- when that didn't help 
(probably installed for the original ruby that came with tiger) I 
first tried the svn version and then the 0.13 tgz. With both of these 
options my ruby prefix is set correctly but I get this error in the 
config phase:

$ ruby install.rb config
install.rb: entering config phase...
create ext/rubycocoa/extconf.rb
create framework/GeneratedConfig.xcconfig
create framework/src/objc/Version.h
create tests/Makefile
---> framework
create /Users/stephen/dev/ruby/src/rubycocoa/framework/src/objc/osx_ruby.h ...
create 
/Users/stephen/dev/ruby/src/rubycocoa/framework/src/objc/osx_intern.h 
...
BSROOT="/Users/stephen/dev/ruby/src/rubycocoa/framework/bridge-support" 
CFLAGS="" /usr/local/bin/ruby build.rb
Generating BridgeSupport metadata for: CoreFoundation ...
     Collect metadata (20.65495 seconds)
/usr/local/lib/ruby/1.8/rexml/document.rb:186:in `write': undefined 
local variable or method `transitive' for <UNDEFINED> ... 
</>:REXML::Document (NameError)
         from ./gen_bridge_metadata.rb:1516:in `generate_xml'
         from ./gen_bridge_metadata.rb:1516:in `open'
         from ./gen_bridge_metadata.rb:1516:in `generate_xml'
         from ./gen_bridge_metadata.rb:542:in `write'
         from build.rb:106
         from build.rb:50:in `measure'
         from build.rb:104
         from build.rb:62:in `each'
         from build.rb:62
config failed
hook /Users/stephen/dev/ruby/src/rubycocoa/framework/post-config.rb failed:
'system 
BSROOT="/Users/stephen/dev/ruby/src/rubycocoa/framework/bridge-support" 
CFLAGS="" /usr/local/bin/ruby build.rb' failed

OK, I subscribed to the mailing list and also searched the list 
archives and found the rexml bug and applied the patch in this 
message:

   http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/32040

then rubycocoa built successfully and I got back to superalloy's 
screencast and saw my own version of the first Leecher window as I'm 
following along -- now I'm finally back to to the part where I'm 
saying ...

"That's cool!"

...

-- 
- Stephen Bannasch
   Concord Consortium, http://www.concord.org

Re: [Rubycocoa-talk] [ANN] Rucola 0.0.2 released.

[Eloy D. <elo...@gm...>]

Err, forgot to add this link where you can find a screencast on =20
creating a Rucola/RubyCocoa app with BDD.

http://www.superalloy.nl/blog/2007/11/26/rucola-002-released/

Cheers,
Eloy

On 26 nov 2007, at 21:30, Eloy Duran wrote:

> Hello,
>
> We are pleased to announce the second release of Rucola today.
> http://rucola.rubyforge.org/
>
> This release has some major enhancements and therefore uses the new =20=

> RubyCocoa 0.13.
>
> We're happy to announce that Chris McGrath & Satoshi Nakagawa have =20
> joined the team.
> Chris added the foundation for ActiveRecord usage with Rucola. (No =20
> fixtures etc yet.)
> And Satoshi-san uses the crash reporter plugin in his excellent =20
> RubyCocoa based irc client LimeChat,
> for which he has provided lots of patches.
>
> Also there's support for autotest and some plugins.
>
> And lots of other improvements.
>
> Cheers,
> Rucola team.
>
> =3D=20
> =3D=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> A Framework for building Cocoa applications in Ruby
>
> Rucola is a light weight framework that helps you write RubyCocoa =20
> apps.
> It allows you to build, test, and deploy applications using rake =20
> commands,
> eliminating the need to use XCode, however you can use XCode if you =20=

> wish.
>
> Rucola provides a set of generators to help you generate =20
> controllers, window controllers,
> and document-based applications. It also provides APIs for =20
> simplifying some of Objective-C=92s
> ways of doing things.
> =3D=20
> =3D=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> CHANGES:
>
> RUCOLA Core:
> - Initializer: Spec'd the class methods of Initializer.
> - Initializer: Change initializer to check if environment is release =20=

> rather than debug so that we can have the same setup for debug and =20
> test. Fixes problem when AR plugin installed in app.
>
> - Plugin: Added script/generate rucola_plugin for rucola apps
> - Plugin: Add the initial Plugin code and hook it into the initializer
> - Plugin: Added Plugin#after_launch which uses a PluginRunner class =20=

> that uses NSNotifications to run plugin hooks after the application =20=

> has started.
>
> - Notifications: Added a helper for firing notifications.
> - Notifications: Moved notification name resolution to a separate =20
> method, and don't raise NameErrors when the constant doesn't exist.
>
> - Support: Added Rucola::InfoPlist#app_name & Rucola::RCApp#app_name =20=

> which return the CFBundleExecutable value from the Info.plist file.
>
> - Testing: Added the code to make autotest play nice with a rucola =20
> app!!
> - Testing: Added autotest sound plugin, original idea from: Jeremy =20
> Seitz.
> - Testing: Added autotest images plugin, copyright: John Nunemaker.
> - Testing: Added useful skeleton tests using test/spec and mocha.
> - Testing: Added a few more test helpers which provide a shortcut =20
> for getting ivars (ib_outlets).
>
> - InitializeHooks: The initialize_hooks will now call #after_init on =20=

> an instance if it exists. This is so that #init doesn't have to be =20
> overriden to setup defaults etc.
>
> - Generator: Updated the generators with better banners.
> - Generator: The document_model_generator will not longer run if no =20=

> extension is specified, but rather display the usage banner.
>
> - Nib: Fixed bugs where destructive methods were called on immutable =20=

> objects. This was a change in RubyCocoa.
> - Nib: Nib#add_class now takes an optional superclass.
>
> - Rake: Fixed a bug in the xcode rake task where the local var =20
> 'executable' was not passed explicitly into the thread. So the app =20
> would sometimes not come to the front.
> - Rake: The rake test task will now print with the -rr pretty test/=20
> spec output.
> - Rake: Modified xcode:build rake task to do xcodebuild everytime. =20
> Otherwise changes in the nibs will not be reflected in the app bundle.
> - Rake: Make main.rake load tasks from vendor/plugins/*/tasks/*.rake
>
> EXTRAS:
> - AR: Add basic ActiveRecord model, proxy and migration generator.
> - AR: The AR generator also adds the proxy and =20
> ActiveRecordSetController to the specified nibs.
> - AR: Move the ActiveRecord code into a rucola_activerecord plugin
> - AR: Added support for migrations and other AR tasks
>
> - Samples: Added another simple sample app (Leecher) which simply =20
> downloads files and displays the progress.
>
> - SACrashReporter: Fixed bug if ~/Library/Logs/CrashReporter doesn't =20=

> exist.
> - SACrashReporter: Fixed bug in the crash log naming style on 10.5.
> - SACrashReporter: The crash reporter will never be ran if it's the =20=

> very first time.
> - SACrashReporter: Replaced the http posting with the cocoa =20
> equivalent and display message while the reporter is doing the post.
> - SACrashReporter: On Leopard every crash is logged in an individual =20=

> file, now reads and writes those too.
> - SACrashReporter: SACrashReporter/init.rb now uses the new Plugin =20
> system to alter Initializer.do_boot and run SACrashReporter.submit =20
> after the application has started.
>
> - Rucola TM Bundle: Going to the view from the application =20
> controller will now open the MainMenu.nib in IB.

[Rubycocoa-talk] [ANN] Rucola 0.0.2 released.

[Eloy D. <elo...@gm...>]

Hello,

We are pleased to announce the second release of Rucola today.
http://rucola.rubyforge.org/

This release has some major enhancements and therefore uses the new =20
RubyCocoa 0.13.

We're happy to announce that Chris McGrath & Satoshi Nakagawa have =20
joined the team.
Chris added the foundation for ActiveRecord usage with Rucola. (No =20
fixtures etc yet.)
And Satoshi-san uses the crash reporter plugin in his excellent =20
RubyCocoa based irc client LimeChat,
for which he has provided lots of patches.

Also there's support for autotest and some plugins.

And lots of other improvements.

Cheers,
Rucola team.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
A Framework for building Cocoa applications in Ruby

Rucola is a light weight framework that helps you write RubyCocoa apps.
It allows you to build, test, and deploy applications using rake =20
commands,
eliminating the need to use XCode, however you can use XCode if you =20
wish.

Rucola provides a set of generators to help you generate controllers, =20=

window controllers,
and document-based applications. It also provides APIs for simplifying =20=

some of Objective-C=92s
ways of doing things.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

CHANGES:

RUCOLA Core:
- Initializer: Spec'd the class methods of Initializer.
- Initializer: Change initializer to check if environment is release =20
rather than debug so that we can have the same setup for debug and =20
test. Fixes problem when AR plugin installed in app.

- Plugin: Added script/generate rucola_plugin for rucola apps
- Plugin: Add the initial Plugin code and hook it into the initializer
- Plugin: Added Plugin#after_launch which uses a PluginRunner class =20
that uses NSNotifications to run plugin hooks after the application =20
has started.

- Notifications: Added a helper for firing notifications.
- Notifications: Moved notification name resolution to a separate =20
method, and don't raise NameErrors when the constant doesn't exist.

- Support: Added Rucola::InfoPlist#app_name & Rucola::RCApp#app_name =20
which return the CFBundleExecutable value from the Info.plist file.

- Testing: Added the code to make autotest play nice with a rucola app!!
- Testing: Added autotest sound plugin, original idea from: Jeremy =20
Seitz.
- Testing: Added autotest images plugin, copyright: John Nunemaker.
- Testing: Added useful skeleton tests using test/spec and mocha.
- Testing: Added a few more test helpers which provide a shortcut for =20=

getting ivars (ib_outlets).

- InitializeHooks: The initialize_hooks will now call #after_init on =20
an instance if it exists. This is so that #init doesn't have to be =20
overriden to setup defaults etc.

- Generator: Updated the generators with better banners.
- Generator: The document_model_generator will not longer run if no =20
extension is specified, but rather display the usage banner.

- Nib: Fixed bugs where destructive methods were called on immutable =20
objects. This was a change in RubyCocoa.
- Nib: Nib#add_class now takes an optional superclass.

- Rake: Fixed a bug in the xcode rake task where the local var =20
'executable' was not passed explicitly into the thread. So the app =20
would sometimes not come to the front.
- Rake: The rake test task will now print with the -rr pretty test/=20
spec output.
- Rake: Modified xcode:build rake task to do xcodebuild everytime. =20
Otherwise changes in the nibs will not be reflected in the app bundle.
- Rake: Make main.rake load tasks from vendor/plugins/*/tasks/*.rake

EXTRAS:
- AR: Add basic ActiveRecord model, proxy and migration generator.
- AR: The AR generator also adds the proxy and =20
ActiveRecordSetController to the specified nibs.
- AR: Move the ActiveRecord code into a rucola_activerecord plugin
- AR: Added support for migrations and other AR tasks

- Samples: Added another simple sample app (Leecher) which simply =20
downloads files and displays the progress.

- SACrashReporter: Fixed bug if ~/Library/Logs/CrashReporter doesn't =20
exist.
- SACrashReporter: Fixed bug in the crash log naming style on 10.5.
- SACrashReporter: The crash reporter will never be ran if it's the =20
very first time.
- SACrashReporter: Replaced the http posting with the cocoa equivalent =20=

and display message while the reporter is doing the post.
- SACrashReporter: On Leopard every crash is logged in an individual =20
file, now reads and writes those too.
- SACrashReporter: SACrashReporter/init.rb now uses the new Plugin =20
system to alter Initializer.do_boot and run SACrashReporter.submit =20
after the application has started.

- Rucola TM Bundle: Going to the view from the application controller =20=

will now open the MainMenu.nib in IB.=

Re: [Rubycocoa-talk] Broken RC install!

[Laurent S. <lsa...@ap...>]

This is just a warning and this can be ignored. You can perhaps fix it  
by removing the modified version of libruby in /usr/lib (normally the  
installer keeps a backup there of the original version).

At a glance it seems that RubyCocoa was built with the stock version  
of ruby, then you try to use it with a custom version of ruby.

Laurent

On Nov 26, 2007, at 4:36 PM, Tim Perrett wrote:

> Hey Laurent,
>
> Thanks for the speedy reply. I think its because I have two versions
> of ruby installed. Ive managed to get it registering in IRB on my
> custom install, but now in IRB I get this message:
>
> 2007-11-26 15:34:26.220 irb[1999] WARNING: multiple libruby.dylib
> found: '/usr/local/lib/libruby.dylib' and '/usr/lib/libruby.1.dylib'
> 2007-11-26 15:34:26.220 irb[1999]
> RBCocoaInstallRubyThreadSchedulerHooks: warning:
> rb_set_cocoa_thread_hooks is linked from a different library (/usr/
> lib/libruby.1.dylib) than ruby_init (/usr/local/lib/libruby.dylib)
>
> How do I stop it linking to the stock version of ruby?
>
> Cheers
>
> Tim
>
>
>
> On 26 Nov 2007, at 15:28, Laurent Sansonetti wrote:
>
>> How did you install? (binary installer, or from the sources?)
>>
>> On which system did you install on? Do you reproduce the same problem
>> on both 10.4 and 10.5?
>>
>> What happens when you do require 'osx/cocoa'?
>>
>> What's your Ruby load path? (ruby -e 'p $:'). Verify that the
>> RubyCocoa files are there.
>>
>> Laurent
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] Broken RC install!

[Tim P. <he...@ti...>]

Hmm, im not getting that problem on leopard now I have switched back  
to the new leopard distributed 1.8.6 ruby - Im not so worried about  
tiger anyway as thats just on my macbookpro which isn't my main dev  
machine.

Thanks for the pointers

Tim

On 26 Nov 2007, at 15:28, Laurent Sansonetti wrote:

> How did you install? (binary installer, or from the sources?)
>
> On which system did you install on? Do you reproduce the same problem
> on both 10.4 and 10.5?
>
> What happens when you do require 'osx/cocoa'?
>
> What's your Ruby load path? (ruby -e 'p $:'). Verify that the
> RubyCocoa files are there.

Re: [Rubycocoa-talk] Broken RC install!

[Tim P. <he...@ti...>]

Hey Laurent,

Thanks for the speedy reply. I think its because I have two versions  
of ruby installed. Ive managed to get it registering in IRB on my  
custom install, but now in IRB I get this message:

2007-11-26 15:34:26.220 irb[1999] WARNING: multiple libruby.dylib  
found: '/usr/local/lib/libruby.dylib' and '/usr/lib/libruby.1.dylib'
2007-11-26 15:34:26.220 irb[1999]  
RBCocoaInstallRubyThreadSchedulerHooks: warning:  
rb_set_cocoa_thread_hooks is linked from a different library (/usr/ 
lib/libruby.1.dylib) than ruby_init (/usr/local/lib/libruby.dylib)

How do I stop it linking to the stock version of ruby?

Cheers

Tim



On 26 Nov 2007, at 15:28, Laurent Sansonetti wrote:

> How did you install? (binary installer, or from the sources?)
>
> On which system did you install on? Do you reproduce the same problem
> on both 10.4 and 10.5?
>
> What happens when you do require 'osx/cocoa'?
>
> What's your Ruby load path? (ruby -e 'p $:'). Verify that the
> RubyCocoa files are there.
>
> Laurent

Re: [Rubycocoa-talk] Broken RC install!

[Laurent S. <lsa...@ap...>]

How did you install? (binary installer, or from the sources?)

On which system did you install on? Do you reproduce the same problem  
on both 10.4 and 10.5?

What happens when you do require 'osx/cocoa'?

What's your Ruby load path? (ruby -e 'p $:'). Verify that the  
RubyCocoa files are there.

Laurent

On Nov 26, 2007, at 4:11 PM, Tim Perrett wrote:

> Hey Chaps
>
> Ive installed the latest version of RC, but I don't seem to be able
> to do "require 'osx/cocoa'" in IRB? This seems to be the base on both
> 10.4 and 10.5 - any ideas?
>
> Im on RC 0.13
>
> Cheers
>
> Tim
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

[Rubycocoa-talk] Broken RC install!

[Tim P. <he...@ti...>]

Hey Chaps

Ive installed the latest version of RC, but I don't seem to be able  
to do "require 'osx/cocoa'" in IRB? This seems to be the base on both  
10.4 and 10.5 - any ideas?

Im on RC 0.13

Cheers

Tim

Re: [Rubycocoa-talk] [ANN] RubyInject 0.1.0

[Lon B. <lo...@ma...>]

Laurent,

You are on fire. Amazing project.

--
Lon

Doing more with less.
http://speedymac.com
http://macurls.com

[Rubycocoa-talk] [ANN] RubyInject 0.1.0

[Laurent S. <lau...@gm...>]

Hi,

I am glad to announce the first version of the RubyInject project.

RubyInject is a Mac OS X framework that allows you to inject at
runtime the Ruby interpreter into any running application, using the
mach_star mechanism.

It will spawn a new thread on the remote process, initialize the Ruby
interpreter, start a new DRb server that exposes an expression
evaluator object, and advertises the DRb server URI on Bonjour.

A client is provided, inject.rb, that waits on Bonjour for the DRb
server URI, connects to it, then either executes a given Ruby script
or starts an IRB session.

RubyInject is especially useful when combined with RubyCocoa. You can
at runtime inject RubyCocoa into an Objective-C application and start
introspecting and messaging its objects.

Check out the following link for more details:

http://rubycocoa.sourceforge.net/RubyInject

Enjoy,

Laurent

[Rubycocoa-talk] [ANN] RubyCocoa 0.13.0

[Laurent S. <lau...@gm...>]

Hi,

I am honored to announce the immediate release of RubyCocoa 0.13.0.

RubyCocoa is a Mac OS X framework that allows Cocoa programming in the
object-oriented scripting language Ruby. In other words, it is a
bridge that let you access Objective-C objects from Ruby, and
vice-versa.

You can learn more about RubyCocoa on our website:

http://rubycocoa.sf.net

A source tarball as well as binary installers for Mac OS X 10.4 and
10.5 are provided.

This is mostly a bugs fix release, addressing many critical issues,
but it also brings some nice enhancements. All users are encouraged to
upgrade, and report us feedback.

Mac OS X 10.5, Leopard, is as you can see supported by this release.
Installing this release using the binary installer or manually with
the default build parameters won't override the system version, it
will go in /Library while the system version is in /System.

The release notes are following. Enjoy!

Laurent

New features:

- NSArray and NSDictionary now respond to the same messages of their
Ruby equivalents, respectively Array and Hash. NSString responds to
the String messages too, except #=~ and #match. The implementation is
fast and reliable, but respects the Cocoa semantics. The
#method_missing hack has been removed.

- Added utility methods to NSRect, NSPoint, NSSize and NSRange.

- Added useful inspect methods to NSString, NSNumber, NSArray,
NSDictionary, NSCFBoolean and NSDate. Added pretty print support to
NSString, NSArray, NSDictionary.

- Added a #to_ns method to Array, Hash, String, Numeric, TrueClass,
FalseClass, Time, to convert them to their Cocoa equivalent.

- Added ObjcPtr#cast_as(encoding) for more generic casting from void*.

- Added Leopard-only samples.

Bugs fixed:

- Fixed various memory leaks in the RubyCocoa initialization code, and
in the bridge support parsing code. No memory should now be leaked
during initialization.

- Improved the ruby obj -> ocid and ruby obj -> SEL conversions performance.

- Fixed a crash when passing a pointer to an ObjC object, then trying
to convert it as a Ruby object after the API call, but crashing
because the pointer wasn't touched by the API. Now preparing
passed-by-reference pointers to NULL.

- Fixed an error, "Please install again" on reinstalling using the
binary installer.

- Do not translate 'set' methods that get more than one argument.

- Create the slave objects at demand, if they do not exist yet. This
fixes a bindings / CoreData problem in 10.5.

- Now resetting the context autorelease pools on every thread restore.

- Fixed a bug when an object that was being allocated from a Ruby
thread was still in the cache while the thread was killed, resulting
in a corrupted cache.

- Make sure we do not cache CF-based objects.

- Fixed a circular retain cycle from ObjC objects allocated from an
NSObject-based Ruby class, resulting in a leak of both the ObjC object
and its Ruby proxy.

- Hook [copyWithZone:] and reset the slave object so that every ObjC
object has a different slave object. This fixes a crash when releasing
a slave object that could be shared by multiple ObjC objects.

- #objc_send will now pass a frozen selector to the core, where
underscore characters won't be transformed as ':'. This is a
convenience utility to call ObjC methods that contain underscores as
part of their selector, like for example [__rbobj__].

- Better OvMix retain cycle: if an OvMix object is created from Ruby,
we by default don't retain its Ruby proxy, and start tracking
retain/release messages, and appropriately re-retain/re-release the
Ruby proxy.

- Removed the old __slave_nsobj__ ivar hook. Now all pure-Ruby objects
will be wrapped in an autoreleased RBObject.

- Fixed a bug, when ObjC arguments that were passed from an ObjC
closure to Ruby were not retained, as they should. Added a test case.

- Better facility (10.5 only) that dispatches messages from threads to
the thread where RubyCocoa was initialized. It was previously assuming
that RubyCocoa was run in the main thread, which may not be always
true (Ruby could be ran in a different thread).

- Now allow the send the of 'new' message to any ObjC class that will
respond to it. Keep the old behavior (raising an exception) for
classes that don't implement new.

- Added threading support for 10.5.

- Updated metaconfig and Rakefile to use '--gen-bridge-support=no' on 10.5.

- New metaconfig option --sdkroot. Fix setup error
--macosx-deployment-target=10.4 on 10.5.

- Fixed String#to_nsstring for 10.5.

- String#nsenconding, to_nsstring, to_nsmutablestring are now
deprecated. Developers are encouraged to switch to #to_ns.

- Fixed a bug, calling to_ns for a Ruby String which has illegal utf-8
sequences caused a bus error.

- Avoid an infinite loop when creating the slave proxy, which could be
caused by an attempt to pass an object to Objective-C in its
#initialize method.

- sample/Scripts/darkroom.rb: fix SEGV of darkroom.rb on 10.5.

- Added CoreData.define_wrapper_for_entity(). This feature was part of
CoreData.define_wrapper(). Removed "to_a" for NSArray in CoreData
module.

- Load the libSystem.bridgesupport file if it exists (10.5 only).

- rb_nibtool: Fixed a crash when the provided Ruby script only defines
actions but no outlets, or vice-versa.

- rb_nibtool: Fixed bug where #each was called on nil if there were
either no actions OR outlets in the class.

- rb_nibtool: Fixed bug where a new class from a source file would not
show up in the class list in IB because the superclass is unknown to
the classes list in IB. If the superclass const is not found it will
default to NSObject. This change is not effective when rb_nibtool is
used with rubynode.

- rb_nibtool: Fixed problem when not detecting existing classes.

- standaloneify: Now sets the environment variable
ENV['RUBYCOCOA_STANDALONEIFYING?']. This is to be able to prevent code
from being ran when an application is being standaloneified.

- standaloneify: Will now skip all the source files at any depth in Resources.

- gen_bridge_doc: Updated to work with the latest Apple documentation and 10.5.

- gen_bridge_doc: Fixed a bug where </i> tags weren't replaced by '_'.

- gen_bridge_doc: Added documentation for the translated bool methods,
eg: isRunning -> running?.

[Rubycocoa-talk] Joining forces

[Alistair H. <ali...@gm...>]

I've got a great little idea for an app but I've not got much experience in
RubyCocoa yet so I was wondering if anyone would like to join in on this
project with me? I'll give more details to anyone who is interested.
Cheers

-- 
Alistair Holt
ali...@gm...

Re: [Rubycocoa-talk] Manipulating Core Data

[Tim P. <he...@ti...>]

Off the top of my head

@@media =  
NSEntityDescription 
.insertNewObjectForEntityForName_inManagedObjectContext("Media",context)

HTH

Tim


On 18 Nov 2007, at 15:48, Alistair Holt wrote:

> NSManagedObject *media = [NSEntityDescription  
> insertNewObjectForEntityForName:@"Media"  
> inManagedObjectContext:context];
>

[Rubycocoa-talk] Manipulating Core Data

[Alistair H. <ali...@gm...>]

Hello,
I'm feeling like an idiot at the moment. I just can not figure out how to
convert this objective-c code over to ruby:

NSManagedObject *media = [NSEntityDescription
insertNewObjectForEntityForName:@"Media" inManagedObjectContext:context];


Cheers

-- 
Alistair Holt
ali...@gm...

Re: [Rubycocoa-talk] Web server inside a RubyCocoa App

[Tim P. <he...@ti...>]

Sweet, Cheers as always Eloy :)


On 18 Nov 2007, at 14:28, Eloy Duran wrote:

> I'm using a NSTask for this. It's pretty straightforward.
> If you or Alistair have some problems just email to the list and I'll
> see if I can help out. :)

Re: [Rubycocoa-talk] Web server inside a RubyCocoa App

[Eloy D. <elo...@gm...>]

I'm using a NSTask for this. It's pretty straightforward.
If you or Alistair have some problems just email to the list and I'll  
see if I can help out. :)

Eloy

On 18 nov 2007, at 15:15, Tim Perrett wrote:

> Sure, so the camping server is webrick based? (I know thats a bit OT
> btw, sorry)
>
> Has anyone actually implemented an NSTask (firing mongrel) based
> system? I must admit I never actually got around to implementing it.
> If anyone has done it, it would be great if they could share there
> experiences :)
>
> Cheers
>
> Tim
>
>
>
>
> On 18 Nov 2007, at 14:06, Eloy Duran wrote:
>
>> I would however use webrick first and switch to mongrel if you really
>> need the extra speed. Because mongrel uses a C extension it will take
>> a bit more work to bundle it and adds approx. 1mb to your app size.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] Web server inside a RubyCocoa App

[Tim P. <he...@ti...>]

Sure, so the camping server is webrick based? (I know thats a bit OT  
btw, sorry)

Has anyone actually implemented an NSTask (firing mongrel) based  
system? I must admit I never actually got around to implementing it.  
If anyone has done it, it would be great if they could share there  
experiences :)

Cheers

Tim




On 18 Nov 2007, at 14:06, Eloy Duran wrote:

> I would however use webrick first and switch to mongrel if you really
> need the extra speed. Because mongrel uses a C extension it will take
> a bit more work to bundle it and adds approx. 1mb to your app size.

Re: [Rubycocoa-talk] Web server inside a RubyCocoa App

[Eloy D. <elo...@gm...>]

I would however use webrick first and switch to mongrel if you really  
need the extra speed. Because mongrel uses a C extension it will take  
a bit more work to bundle it and adds approx. 1mb to your app size.

Eloy

On 18-nov-2007, at 14:45, Tim Perrett <he...@ti...> wrote:

> Hey Eloy, Alistair,
>
> Im sure this topic has come up before on the list.
>
> http://sourceforge.net/mailarchive/message.php?msg_id=BDCAF4E2-E8BB-451F-9257-65AF07DC8D26%40timperrett.com
>
> Although its Rails, not camping - but doesn't camping use Mongrel as
> the HTTP server also?
>
> Cheers
>
> Tim
>
> On 17 Nov 2007, at 14:46, elo...@gm... wrote:
>
>> Hey Alistair,
>>
>>
>> Standaloneify will already do this for you. Only one catch is that if
>> you are going to fork the process standalonify will never know  of  
>> the
>> dependencies. So you have to require the depencies in your app as  
>> well
>> when running standaloneify. Other than that it works great in an app
>> I'm working on.
>>
>> Cheers,
>> Eloy
>
>
> --- 
> ----------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] Web server inside a RubyCocoa App

[Tim P. <he...@ti...>]

Hey Eloy, Alistair,

Im sure this topic has come up before on the list.

http://sourceforge.net/mailarchive/message.php?msg_id=BDCAF4E2-E8BB-451F-9257-65AF07DC8D26%40timperrett.com

Although its Rails, not camping - but doesn't camping use Mongrel as  
the HTTP server also?

Cheers

Tim

On 17 Nov 2007, at 14:46, elo...@gm... wrote:

> Hey Alistair,
>
>
> Standaloneify will already do this for you. Only one catch is that if
> you are going to fork the process standalonify will never know  of the
> dependencies. So you have to require the depencies in your app as well
> when running standaloneify. Other than that it works great in an app
> I'm working on.
>
> Cheers,
> Eloy

Re: [Rubycocoa-talk] stanaloneify.rb in Leopard

[Eloy D. <elo...@gm...>]

Ah ok. Actually, yes that's the way you would use it.
But it might be more convient to add it to your PATH or create an  
alias which points to that script.

Eloy

On 18 nov 2007, at 13:33, Alistair Holt wrote:

> @ Rod - I've not tried using anything I've produced in Leopard back  
> in Tiger but to be honest I'm thinking I may not support Tiger anyway.
>
> @ Eloy - I'm still pretty fresh into RubyCocoa so I'm really  
> learning as I go along. Would you issue a command such as 'ruby / 
> System/Library/Frameworks/RubyCocoa.framework/Versions/A/Tools/ 
> standaloneify.rb MyNewApp.app MyOldApp.app' ? I'm guessing there is  
> a nicer way of doing this?
>
> Cheers
>
> On 18/11/2007, elo...@gm... <elo...@gm...>  
> wrote:
> Hi Alistair,
>
> Could you please explain what specifically is your problem with
> running the the standaloneify that's included with the framework?
>
> Because it would be much better to use that one since it includes
> several enhancements/fixes which I don't think are backported to the
> original script.
>
> Cheers,
> Eloy
>
> On 11/17/07, Alistair Holt <ali...@gm... > wrote:
> > Hello all!
> > I've just been playing with standaloneify.rb in Leopard and  
> thought I'd
> > document my findings for reference.
> >
> > I'm not sure how one goes about using the standaloneify.rb which  
> is included
> > in Leopard
> > (/System/Library/Frameworks/RubyCocoa.framework/Versions/A/Tools/ 
> standaloneify.rb
> > ) so I instead downloaded the .rb from
> > http://www.jpaisley.com/software/ruby/ . If anyone knows how to do  
> it
> > properly please let me know!
> >
> >
> > I then encountered a problem with the .rb I had downloaded in that  
> it was
> > looking for frameworks in '/Library/Frameworks'.. now I'm not sure  
> about
> > other Leopard installations but in mine this folder was empty so I  
> had to
> > drop into the Terminal, delete 'Library/Frameworks' and create a  
> symbolic
> > link between '/Developer/SDKs/MacOSX10.5.sdk/System/Library/ 
> Frameworks/' and
> > '/Library/Frameworks'.
> >
> > After that it worked great!
> >
> > --
> > Alistair Holt
> > ali...@gm...
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>
>
>
> -- 
> Alistair Holt
> ali...@gm...
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk

Re: [Rubycocoa-talk] stanaloneify.rb in Leopard

[Alistair H. <ali...@gm...>]

@ Rod - I've not tried using anything I've produced in Leopard back in Tiger
but to be honest I'm thinking I may not support Tiger anyway.
@ Eloy - I'm still pretty fresh into RubyCocoa so I'm really learning as I
go along. Would you issue a command such as
'ruby /System/Library/Frameworks/RubyCocoa.framework/Versions/A/Tools/standaloneify.rb
MyNewApp.app MyOldApp.app' ? I'm guessing there is a nicer way of doing
this?

Cheers

On 18/11/2007, elo...@gm... <elo...@gm...> wrote:
>
> Hi Alistair,
>
> Could you please explain what specifically is your problem with
> running the the standaloneify that's included with the framework?
>
> Because it would be much better to use that one since it includes
> several enhancements/fixes which I don't think are backported to the
> original script.
>
> Cheers,
> Eloy
>
> On 11/17/07, Alistair Holt <ali...@gm...> wrote:
> > Hello all!
> > I've just been playing with standaloneify.rb in Leopard and thought I'd
> > document my findings for reference.
> >
> > I'm not sure how one goes about using the standaloneify.rb which is
> included
> > in Leopard
> >
> (/System/Library/Frameworks/RubyCocoa.framework/Versions/A/Tools/standaloneify.rb
> > ) so I instead downloaded the .rb from
> > http://www.jpaisley.com/software/ruby/ . If anyone knows how to do it
> > properly please let me know!
> >
> >
> > I then encountered a problem with the .rb I had downloaded in that it
> was
> > looking for frameworks in '/Library/Frameworks'.. now I'm not sure about
> > other Leopard installations but in mine this folder was empty so I had
> to
> > drop into the Terminal, delete 'Library/Frameworks' and create a
> symbolic
> > link between '/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/'
> and
> > '/Library/Frameworks'.
> >
> > After that it worked great!
> >
> > --
> > Alistair Holt
> > ali...@gm...
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>



-- 
Alistair Holt
ali...@gm...

Re: [Rubycocoa-talk] stanaloneify.rb in Leopard

[<elo...@gm...>]

Hi Alistair,

Could you please explain what specifically is your problem with
running the the standaloneify that's included with the framework?

Because it would be much better to use that one since it includes
several enhancements/fixes which I don't think are backported to the
original script.

Cheers,
Eloy

On 11/17/07, Alistair Holt <ali...@gm...> wrote:
> Hello all!
> I've just been playing with standaloneify.rb in Leopard and thought I'd
> document my findings for reference.
>
> I'm not sure how one goes about using the standaloneify.rb which is included
> in Leopard
> (/System/Library/Frameworks/RubyCocoa.framework/Versions/A/Tools/standaloneify.rb
> ) so I instead downloaded the .rb from
> http://www.jpaisley.com/software/ruby/ . If anyone knows how to do it
> properly please let me know!
>
>
> I then encountered a problem with the .rb I had downloaded in that it was
> looking for frameworks in '/Library/Frameworks'.. now I'm not sure about
> other Leopard installations but in mine this folder was empty so I had to
> drop into the Terminal, delete 'Library/Frameworks' and create a symbolic
> link between '/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/' and
> '/Library/Frameworks'.
>
> After that it worked great!
>
> --
> Alistair Holt
> ali...@gm...
>

[Rubycocoa-talk] Leopard update for rubycocoa.com

[Tim B. <tim...@gm...>]

With all of the work that has gone into RubyCocoa for Leopard, the
articles that I wrote for my "RubyCocoa Resources" site need an
update.

But lately I've had my hands full with a different project, the new
language that I called "Nu" (http://programming.nu).  Nu a Lisp-like
language that I wrote in Objective-C to specifically get around the
impedance mismatches between Ruby (or Python) and Objective-C.   You
can read more about those mismatches here:
http://programming.nu/rubycocoa-and-rubyobjc (but I think regular
readers of this list are very aware of them).

For my purposes, Nu has been working out wonderfully, and not only do
I no longer consider serious use of RubyCocoa, I've also found that I
can use Nu for everything that I previously did with Ruby (Nu is
Apple-only, but right now, so am I).

So with that, it's time to decide what to do with "RubyCocoa
Resources".  I've heard that Apple had lots of RubyCocoa documentation
in the works for Leopard. If that's enough, then I could just shut
down my site and point the domain to http://rubycocoa.sourceforge.net.
 Otherwise, I think it needs a new maintainer.  Any volunteers?

Tim

p.s. for questions and discussions about Nu, please see our Google
group: http://groups.google.com/group/programming-nu.

Re: [Rubycocoa-talk] stanaloneify.rb in Leopard

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

On Nov 17, 2007, at 3:57 PM, Alistair Holt wrote:

> Hello all!
>
> I've just been playing with standaloneify.rb in Leopard and thought  
> I'd document my findings for reference.
>
> I'm not sure how one goes about using the standaloneify.rb which is  
> included in Leopard (/System/Library/Frameworks/RubyCocoa.framework/ 
> Versions/A/Tools/standaloneify.rb
> ) so I instead downloaded the .rb from  http://www.jpaisley.com/software/ruby/ 
>  . If anyone knows how to do it properly please let me know!
>
>
> I then encountered a problem with the .rb I had downloaded in that  
> it was looking for frameworks in '/Library/Frameworks'.. now I'm not  
> sure about other Leopard installations but in mine this folder was  
> empty so I had to drop into the Terminal, delete 'Library/ 
> Frameworks' and create a symbolic link between '/Developer/SDKs/ 
> MacOSX10.5.sdk/System/Library/Frameworks/' and '/Library/Frameworks'.
>
> After that it worked great!

Does your app that you built with standaloneify in Leopard, work in  
Tiger?

I have not been able to get something to build in Leopard and run in  
Tiger.

Rod Schmidt
infiniteNIL Software