rubycocoa-talk — talking about RubyCocoa

[Rubycocoa-talk] putting arbitrary strings on the clipboard

[Brian M. <ma...@ex...>]

I want to put arbitrary ASCII strings onto the clipboard (including  
NULs, control chars, etc.). I could do this:

def copy(string)
   applescript = "set the clipboard to \"#{string}\""
   OSX.do_osascript(applescript)
   true
end

But I see no way in applescript to quote peculiar characters (other  
than tab and newline). As a hack, I can convert the string into  
UTF-8, then back into a string, and paste that:

def to_hex(string)
   string.unpack('c*').collect { | char | sprintf("%x", char)}.join
end

def copy(string)
   applescript="
     set unicode_version to \xc7data utf8#{to_hex(string)}\xc8
     set the clipboard to unicode_version as string
   "
   OSX.do_osascript(applescript)
   true
end

(The funny quoted characters are the chevrons applescript uses to  
surround unprintable stuff.)

This happens to work even for Mac-Roman characters (those with the  
high-order bit set), though I think that's an unintended side-effect  
of the way "as string" works.

I'd rather go through a lower-level API than through applescript, but  
I'm ignorant enough of OSA and other topics specific to the Mac that  
I can't find what that would look like.

Can anyone help?


-----
Brian Marick, independent consultant
Mostly on agile methods with a testing slant
www.exampler.com, www.testing.com/cgi-bin/blog
Book in progress: www.exampler.com/book





-----
Brian Marick, independent consultant
Mostly on agile methods with a testing slant
www.exampler.com, www.testing.com/cgi-bin/blog
Book in progress: www.exampler.com/book

Re: [Rubycocoa-talk] Building 'universal' binaries

[Neil S. <ne...@ha...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Neil Stevens wrote:
> How would I go about building a 'universal' (ppc + i386) version of
> RubyCocoa?

OK, I just did a lot of digging around and managed to do it.

The hard part was building the framework; importing the project into
Xcode and trying that just wouldn't work.

So, turns out, the way to go for me anyway was to manually edit the
RubyCocoa.pbproj/project.pbxproj after configuring, and add the
necessary flags to OTHER_CFLAGS and OTHER_LDFLAGS.

The Ruby extension apparently just works fine if the ruby itself is
build correctly.

Hope this helps the next person who tries,

- --
Neil Stevens - ne...@ha...

'A republic, if you can keep it.' -- Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDyODyf7mnligQOmERAmxtAJ9l6tY21gwNXSfZrFqFwiqOAECLDgCggp6f
YnpdyGDmNC3R35IJmc7UCnc=
=GJ9M
-----END PGP SIGNATURE-----

[Rubycocoa-talk] Building 'universal' binaries

[Neil S. <ne...@ha...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How would I go about building a 'universal' (ppc + i386) version of
RubyCocoa?

I have ruby 1.8.4 already built for it, so once ruby cocoa is fixed I
should be set.

thanks,
- --
Neil Stevens - ne...@ha...

'A republic, if you can keep it.' -- Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDx6QEf7mnligQOmERArmyAJ4xXFTMTv/tmR1tekpCMzMwU/F8HQCfcbkf
DUA+t2DqHjHhA9Oc74GqLQM=
=rimk
-----END PGP SIGNATURE-----

Re: [Rubycocoa-talk] online introduction to rubycocoa

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

On 13 Jan 2006, at 9:40, Tim Burks wrote:
>
> I'm working on some documentation of various aspects of RubyCocoa,
> beginning with an introduction.  I've put the introduction online at
> http://www.rubycocoa.com and would welcome your comments and review.

Hi Tim,

I've had a quick read through - it looks very good. I think this will  
be a valuable resource for the community.

I have a few nit-picky comments below - feel free to ignore me :)

> irb(main):002:0> sound = OSX::NSSound.soundNamed "Submarine"

People who have installed a tryout of Photoshop 7 (and possibly other  
Adobe products of that era) will have a corrupt Submarine.aiff - I  
just tried that example and I heard most of the sound then a chirp of  
noise at the end. Possibly worth choosing a different sound just so  
people aren't put off :)

>     i = i.intValue() if i.class != Fixnum

A couple of things

   * having empty brackets doesn't seem very ruby-like - i.intValue
   * 'i === Numeric' rather than 'i.class != Fixnum'
   * instances of NSNumber will support to_i (see to_i method in  
oc_wrapper.rb),
     so you could do 'return i.to_i + j.to_i'

> OSX::ns_import :Client

I prefer OSX.ns_import (I like to think of methods with a dot), and  
use :: for constants.

Cheers,
Jonathan

[Rubycocoa-talk] online introduction to rubycocoa

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

Hi,

I'm working on some documentation of various aspects of RubyCocoa,
beginning with an introduction.  I've put the introduction online at
http://www.rubycocoa.com and would welcome your comments and review.

thanks!

Tim

Re: [Rubycocoa-talk] Wrapping an existing ObjC class

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

On 6 Jan 2006, at 16:01, Aidan Rogers wrote:

> I'm trying to wrap a class from one of Apple's frameworks that's  
> not yet supported by RubyCocoa.  If successful, I'd be keen to  
> share it out with everyone else :-)

Which class is it specifically you're trying to support?


Here is part of my response to a previous post asking about support  
for CoreImage:

<<<<
You could possibly have a go yourself by looking at how the WebKit  
interface is handled - purely from ruby. See osx/webkit.rb and osx/ 
objc/webkit.rb. To summarise (you need to look at osx/objc/webkit.rb  
to see the details):

  (1) load the CoreImage framework
  (2) ns_import the classes needed
  (3) define integer constants/enums
  (4) create NSString (or other object) constants by using  
objc_symbol_to_obj
 >>>>

Hope that is of some help.

Re: [Rubycocoa-talk] Wrapping an existing ObjC class

[Aidan R. <ai...@yo...>]

Hi Jonathan,

I'm trying to wrap a class from one of Apple's frameworks that's not  
yet supported by RubyCocoa.  If successful, I'd be keen to share it  
out with everyone else :-)

Aidan

On 06/01/2006, at 11:07 PM, Jonathan Paisley wrote:

>
> On 3 Jan 2006, at 22:07, Aidan Rogers wrote:
>
>> How do I go about wrapping an existing ObjC class?  Is there an  
>> example somewhere I can work from, or some documentation?
>
> Could you be more specific about what you're trying to do? Is it a  
> class from AppKit/Foundation you want to deal with that's not yet  
> supported in RubyCocoa, or some ObjC class of your own devising? If  
> it's the latter, you can pretty much just use it like this:
>
>  # Do this once to create the Ruby classes corresponding to the  
> ObjC classes
>  OSX.ns_import :YourClassName
>
>  # Then use the class
>  obj = OSX::YourClassName.alloc.init
>  obj.someMethod("hello")
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>

Re: [Rubycocoa-talk] Wrapping an existing ObjC class

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

On 3 Jan 2006, at 22:07, Aidan Rogers wrote:

> How do I go about wrapping an existing ObjC class?  Is there an  
> example somewhere I can work from, or some documentation?

Could you be more specific about what you're trying to do? Is it a  
class from AppKit/Foundation you want to deal with that's not yet  
supported in RubyCocoa, or some ObjC class of your own devising? If  
it's the latter, you can pretty much just use it like this:

  # Do this once to create the Ruby classes corresponding to the ObjC  
classes
  OSX.ns_import :YourClassName

  # Then use the class
  obj = OSX::YourClassName.alloc.init
  obj.someMethod("hello")

Re: [Rubycocoa-talk] Building NSMatrix from scratch.[MESSAGE NOT SCANNED]

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

On 3 Jan 2006, at 0:45, Dave Howell wrote:

> What the log says is
>
> 	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you  
> forget to call super?
>
> I don't understand the question. Does it not like my NSRect? The  
> program keeps running, but the matrix doesn't appear in the window.

This log message is independent of the other problems you were  
seeing. It's a result of a peculiarity in the way RubyCocoa  
initialises objects, whereby the call sequence actually looks like:

   [[[NSViewSubClass alloc] retain] init]

The implementation of 'retain' for NSView notices that init hasn't  
been called yet and issues that log message. This can probably be  
fixed in RubyCocoa. For now, don't worry about it.

[The above is from my memory of investigating this a bit a month or  
so back - some of the details may be slightly different]

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

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

On Jan 5, 2006, at 18:51, Dave Howell wrote:

> Aha.
>
> So if I'm making this new NSView object, how does Cocoa know in which 
> window (or rather, which contentView of which window) I want this new 
> NSMatrix to appear? That's my first guess as to why I can't see it: I 
> haven't "put it into the window" yet.
>
> (My Cocoa Programming book doesn't seem to think anybody would ever 
> want to create these things programmatically.)
>

Never mind. I found it.

inside my NSWindowController object...


self.window.contentView.addSubview(MyMatrix.alloc.init(parameters))

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

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

On Jan 5, 2006, at 7:03, kimura wataru wrote:

>>
>> 	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you 
>> forget
>> to call super?
>>
>> I don't understand the question. Does it not like my NSRect? The
>> program keeps running, but the matrix doesn't appear in the window.
>>
>
> This message is a warning not an error. The view is initialized 
> correctly
> and you can ignore the message. When RubyCocoa generantes a instance of
> subclass of NSView, this message is displayed.
>
> I think that is a bug of RubyCocoa but to solve this problem is 
> difficult.
>
Aha.

So if I'm making this new NSView object, how does Cocoa know in which 
window (or rather, which contentView of which window) I want this new 
NSMatrix to appear? That's my first guess as to why I can't see it: I 
haven't "put it into the window" yet.

(My Cocoa Programming book doesn't seem to think anybody would ever 
want to create these things programmatically.)

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

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

Hi,

OSX::NSRect#new generates a NSRect object.

  OSX::NSRect.new(origin_x, origin_y, size_widhth, size_height)


Mon, Jan 2, 2006 4:45:48 PM, Dave Howell wrote:
>OK, building my cells from scratch isn't working either.
>
>		matrixFrame = NSRect.new
>		matrixFrame.size.height = 40.0
>		matrixFrame.size.width = 28.0
>		matrixFrame.origin.x = 20.0
>		matrixFrame.origin.y = 20.0
>		newMatrix = OSX::NSMatrix.alloc.initWithFrame(matrixFrame)
>
>What the log says is
>
>	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you forget 
>to call super?
>
>I don't understand the question. Does it not like my NSRect? The 
>program keeps running, but the matrix doesn't appear in the window.
>

This message is a warning not an error. The view is initialized correctly
and you can ignore the message. When RubyCocoa generantes a instance of 
subclass of NSView, this message is displayed.

I think that is a bug of RubyCocoa but to solve this problem is difficult.


-- 
kimura wataru

Re: [Rubycocoa-talk] Accessing RubyCocoa instances instantiated by a NIB file.

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

Hi,

If the super class of your cell class confirms to protcol NSCoding (such 
as NSView), we can copy an object with NSArchiver/NSUnarchiver.

  data = OSX::NSArchiver.archivedDataWithRootObject(view)
  newview = OSX::NSUnarchiver.unarchiveObjectWithData(data)


Sun, Jan 1, 2006 4:20:39 PM, Dave Howell wrote:
>I'm trying to set up a Sudoku number puzzle solving tool, which 
>involves (in part) having a nine by nine grid in a window. Each cell of 
>this grid contains the digits 1 through 9 in a 3x3 array.
>
>I have this window, and one cell, in a separate NIB file from the 
>MainMenu file. So I can use code like this to open that window and 
>instantiate the contents:
>
>	mainWindow  = SudokuWindow.alloc.init.createWindow
>
>	(createWindow is a method I created in SudokuWindow for working on the 
>window, since :window isn't defined when the init code runs)
>
>So far so good. Now, I need 80 more cells like the one already in the 
>NIB file, but trying to create them "by hand" seems more than a little 
>crazy. The nine digits are represented as an NSMatrix of NSButtonCells, 
>and the NSMatrix is linked to
>
>class SuCell < OSX::NSObject
>	blah blah blah
>end
>

-- 
kimura wataru

[Rubycocoa-talk] Wrapping an existing ObjC class

[Aidan R. <ai...@yo...>]

Hi all,

How do I go about wrapping an existing ObjC class?  Is there an  
example somewhere I can work from, or some documentation?

Thanks!

Aidan

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

[John L. <jo...@jo...>]

>> I expect you should have initialized your OSX.NSRect thus :
>> 			matrixFrame = NSRect.alloc.init
>
> I thought so too. I tried that first, but
>
> 	RBException_NoMethodError - undefined method `alloc' for  
> OSX::NSRect:Class (OSX::OCException)
> 	RBException_NoMethodError - undefined method `init' for  
> OSX::NSRect:Class (OSX::OCException)

I haven't done all that much with ruby-cocoa lately, but as I recall,  
NSRect is a Ruby class, not an Objective-C class.  And I remember  
using #to_a to convert it to a format that Cocoa methods seemed to like.

Of course, I could be all wrong here.

--John

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

[Neil S. <ne...@ha...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rupert BARROW wrote:
> I expect you should have initialized your OSX.NSRect thus :
>             matrixFrame = NSRect.alloc.init

That doesn't work here.  NSRect is a C struct, not an Objective C class,
so that the very least there is no init possible for it.

- --
Neil Stevens - ne...@ha...

'A republic, if you can keep it.' -- Benjamin Franklin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDuqbxf7mnligQOmERAjAnAJ4hHmMoCsTKMKLtG76e2uj05btrYACeKdXB
17si4q2VYrLlCJ5Yer2o8no=
=4s2S
-----END PGP SIGNATURE-----

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

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

On Jan 3, 2006, at 6:17, Rupert BARROW wrote:

>
> Le 3 janv. 06 =E0 05:42, rub...@li... =
a=20
> =E9crit :
>
>> To: rub...@li...
>> From: Dave Howell <gr...@gr...>
>> Date: Mon, 2 Jan 2006 16:45:48 -0800
>> Subject: [Rubycocoa-talk] Building NSMatrix from scratch.
>> Reply-To: rub...@li...
>>
>> OK, building my cells from scratch isn't working either.
>>
>> 		matrixFrame =3D NSRect.new
>
> I expect you should have initialized your OSX.NSRect thus :
> 			matrixFrame =3D NSRect.alloc.init

I thought so too. I tried that first, but

	RBException_NoMethodError - undefined method `alloc' for=20
OSX::NSRect:Class (OSX::OCException)
	RBException_NoMethodError - undefined method `init' for=20
OSX::NSRect:Class (OSX::OCException)

Also, using NSRect.new, if I

	p matrixFrame

I see this in the log:

	#<OSX::NSRect:0x28aa7c @size=3D#<OSX::NSSize:0x28a874 =
@height=3D40.0,=20
@width=3D28.0>, @origin=3D#<OSX::NSPoint:0x28a888 @x=3D20.0, @y=3D20.0>>


Which is exactly what the NSRect frame looks like from a matrix built=20
in Interface Builder. So as far as I can tell, my matrixFrame is set up=20=

correctly. {shrug}

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

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

Le 3 janv. 06 =C3=A0 05:42, rub...@li... =
=20
a =C3=A9crit :

> To: rub...@li...
> From: Dave Howell <gr...@gr...>
> Date: Mon, 2 Jan 2006 16:45:48 -0800
> Subject: [Rubycocoa-talk] Building NSMatrix from scratch.
> Reply-To: rub...@li...
>
> OK, building my cells from scratch isn't working either.
>
> 		matrixFrame =3D NSRect.new

I expect you should have initialized your OSX.NSRect thus :
			matrixFrame =3D NSRect.alloc.init

> 		matrixFrame.size.height =3D 40.0
> 		matrixFrame.size.width =3D 28.0
> 		matrixFrame.origin.x =3D 20.0
> 		matrixFrame.origin.y =3D 20.0
> 		newMatrix =3D =
OSX::NSMatrix.alloc.initWithFrame(matrixFrame)
>
> What the log says is
>
> 	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you =20=

> forget
> to call super?
>
> I don't understand the question. Does it not like my NSRect? The
> program keeps running, but the matrix doesn't appear in the window.

Cheers,
Rupert

[Rubycocoa-talk] Building NSMatrix from scratch.

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

OK, building my cells from scratch isn't working either.

		matrixFrame = NSRect.new
		matrixFrame.size.height = 40.0
		matrixFrame.size.width = 28.0
		matrixFrame.origin.x = 20.0
		matrixFrame.origin.y = 20.0
		newMatrix = OSX::NSMatrix.alloc.initWithFrame(matrixFrame)

What the log says is

	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you forget 
to call super?

I don't understand the question. Does it not like my NSRect? The 
program keeps running, but the matrix doesn't appear in the window.

[Rubycocoa-talk] Accessing RubyCocoa instances instantiated by a NIB file.

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

I'm trying to set up a Sudoku number puzzle solving tool, which 
involves (in part) having a nine by nine grid in a window. Each cell of 
this grid contains the digits 1 through 9 in a 3x3 array.

I have this window, and one cell, in a separate NIB file from the 
MainMenu file. So I can use code like this to open that window and 
instantiate the contents:

	mainWindow  = SudokuWindow.alloc.init.createWindow

	(createWindow is a method I created in SudokuWindow for working on the 
window, since :window isn't defined when the init code runs)

So far so good. Now, I need 80 more cells like the one already in the 
NIB file, but trying to create them "by hand" seems more than a little 
crazy. The nine digits are represented as an NSMatrix of NSButtonCells, 
and the NSMatrix is linked to

class SuCell < OSX::NSObject
	blah blah blah
end

I can't figure out how to make copies of the cell I have. One approach 
would be to make SuCell create the interface elements to which it's 
bonded. However, trying to recreate this NSMatrix programmatically 
seems very complicated. It would be so much easier to just duplicate 
the one I have already built in Interface Builder, except I can't 
figure out how.

I can usually see the window by accessing self.window from within the 
WindowController code, but attempting to access self.window.contentView 
always returns nil, or sometimes an error complaining that self.window 
itself is nil, even though if I ask Ruby to "p self.window" I do get an 
NSWindow object dumped in the log.

  I'd hoped to use Cocoa's "copy" function to duplicate the NSMatrix. I 
could then create a new SuCell and programmatically link the elements. 
Except I can't figure out how to "get" the first IB object to copy it. 
How do I access the actual instantiated object(s) in order to invoke 
the Cocoa "copy" method?

I hope I've asked the right question. :)

Thanks!

Re: [Rubycocoa-talk] Xcode Class Browser

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

On 31 Dec 2005, at 11:15, C=E9dric Mesnage wrote:

> I am new to rubycocoa. I am setting up an application to manage bibtex
> entries. Doing this project helps me learning both Cocoa and Ruby.
>
> I was wondering if it is possible to use the Xcode Class Browser to
> visualize Ruby code (this would be really helpful).

I don't think the Xcode browser will work here. Other editors may =20
have some level of browsing support (e.g., vim or jedit).

I assume you are aware of BibDesk for bibtex editing:

    http://bibdesk.sourceforge.net/

Cheers,
Jonathan

[Rubycocoa-talk] Xcode Class Browser

[<ced...@gm...>]

Hi everyone,

I am new to rubycocoa. I am setting up an application to manage bibtex
entries. Doing this project helps me learning both Cocoa and Ruby.

I was wondering if it is possible to use the Xcode Class Browser to
visualize Ruby code (this would be really helpful).

Thanks.

--
C=E9dric Mesnage
PhD student, Faculty of Informatics, Lugano
ced...@gm...

Re: [Rubycocoa-talk] Install failure

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

Hi,

Please install gcc3.3 from the package of Xcode Tools.

Wed, Dec 28, 2005 8:03:46 PM, Per Holten wrote:
>Can anyone help with the following prob?  (Latest Tiger, Xcode, etc.)  Also
>tried Darwin Port method, but that fails too (with some other problems!)
>Thanks!
>


-- 
kimura wataru

[Rubycocoa-talk] Install failure

[Per H. <per...@gm...>]

Can anyone help with the following prob?  (Latest Tiger, Xcode, etc.)  Also
tried Darwin Port method, but that fails too (with some other problems!)
Thanks!

Home:~/src/rubycocoa-0.4.2 per$ ruby install.rb config
install.rb: entering config phase...
create ext/rubycocoa/extconf.rb
create ext/rubycocoa/rubycocoa.m
create framework/RubyCocoa.pbproj/project.pbxproj
create framework/src/objc/RBObject.h
create framework/src/objc/RBSlaveObject.h
create framework/src/objc/RubyCocoa.h
create framework/src/objc/Version.h
---> framework
create /Users/per/src/rubycocoa-0.4.2/framework/src/objc/osx_ruby.h ...
create /Users/per/src/rubycocoa-0.4.2/framework/src/objc/osx_intern.h ...
ruby gen_cocoa_wrapper.rb
cpp3: installation problem, cannot exec
`/usr/libexec/gcc/darwin/ppc/cpp-precomp': No such file or directory
/usr/bin/cpp3 returned 1 exit status
../../../../tool/och_analyzer3.rb:205:in `do_cpp'
../../../../tool/och_analyzer3.rb:32:in `initialize'
gen_cocoa_wrapper.rb:310:in `gen_skelton'
gen_cocoa_wrapper.rb:376
gen_cocoa_wrapper.rb:376
gen_cocoa_wrapper.rb:364config failed
hook /Users/per/src/rubycocoa-0.4.2/framework/post-config.rb failed:
'system ruby gen_cocoa_wrapper.rb' failed
try 'ruby install.rb --help' for usage

Re: [Rubycocoa-talk] [PATCH] allocWithZone fix

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

Hi,

This patch was merged to CVS. Thank you.

Fri, Dec 23, 2005 11:13:37 AM, Jonathan Paisley wrote:
>Hello,
>
>This patch came up in a discussion a few weeks ago but hasn't been  
>merged yet as far as I can tell.
>
>class_createInstanceFromZone can't take a NULL zone argument - so  
>it's necessary to look up NSDefaultMallocZone() manually.
>
>Cheers,
>Jonathan
>


-- 
kimura wataru