Well... Yes my macbook is a 32 bit system... So there not going to be a
solution fro my problem in the near future. Anyway I made a kind of
workaround...
Thank you for your help!
anyway I hope the bug will be solved.
___
MacRuby-devel mailing list
MacRub
Hi there!
I'm having problems of getting a list of methods from Classes, declared in
Objective-C.
I have a class compiled, and fully working, look like this:
// Vector.h
@interface Vector : NSObject {
float x,y,z;
}
@property float x,y,z;
@property float length;
@end
// Vector.m
@imple
HI,
I think for calling the .methods method from MacRuby you should add two
additional MacRuby specific arguments.
to get the list of all methods use this:
.methods(true,true)or.methods true, true
--- András Zalavári schrieb am So, 21.11.2010:
Von: András Zalavári
Betreff: [MacRuby-devel] Objec
You can pass two arguments to #methods, which are to include methods from
ancestors and to include Objective-C methods, So you probably want:
vector.methods(false, true)
On 21 nov 2010, at 18:55, András Zalavári wrote:
> Hi there!
>
> I'm having problems of getting a list of methods from Class
Hello, and thank you very much to the developers of MacRuby. It's an amazing
technology and I hope to see it continue to grow.
I've managed to figure out, after an hour or two of wasted time, that although
MacRuby now includes a debugger, that debugger can't be used to debug a MacRuby
Cocoa ap
On Nov 21, 2010, at 3:49 PM, Ryan Porter wrote:
> I've managed to figure out, after an hour or two of wasted time, that
> although MacRuby now includes a debugger, that debugger can't be used to
> debug a MacRuby Cocoa app. Not only through XCode, but at all. Is that
> correct? The release
Hi Gregoire,
I ran your snippet from the terminal and the panel was only able to select
these file types, in my environment.
What version of Mac OS X do you run? It's possible that there is a Cocoa bug
somewhere.
Laurent
On Nov 13, 2010, at 5:38 AM, Gregoire LEJEUNE wrote:
> Hi,
>
> I try t
Hi Scott,
Supporting this has been in discussion for a while, however I'm against it for
consistency sake. If we allow methods to be defined or messaged using different
styles, it can create confusion and ambiguity in some cases (especially if you
start overloading methods).
If you have a good
I commented the #999 ticket, I believe there is a way to make MacRuby classes
automatically conform to protocols (once all required methods are implemented).
Let's try to get that done for the upcoming release :)
Laurent
On Nov 20, 2010, at 2:28 PM, Charles Steinman wrote:
> In case anyone nee
Hi Alan,
Indeed, if you link a specific framework into your project's executable in
Xcode, its BridgeSupport file won't be loaded at runtime by MacRuby. I
re-opened #1000 as I think MacRuby should do it for you, nevertheless. I
believe this issue might hit other persons as MacRuby will gain pop
Hi Alan,
Thanks for reporting that problem in the tracker. In the meantime, keeping a
reference to the Proc object in the Ruby side might work around the problem (as
I suspect that the proc here is being garbage-collected prematurely).
@b = TestBlock.alloc.initWithBlock (@tmp ||= Proc.n
Hi Andras,
Let's try to get this fixed in the upcoming release. Could you file a ticket in
our trac? (if not already done, I just had a quick glance at it so far).
Thanks,
Laurent
On Nov 21, 2010, at 7:49 AM, András Zalavári wrote:
> Well... Yes my macbook is a 32 bit system... So there not go
Hi Ryan,
As Jordan mentioned, the debugger is alpha quality :) It should be able to
debug Xcode apps assuming you tweak a few things out, but not out of the box,
I'm afraid. Also, the code has been neglected a bit as we have been working on
other things. If you file a ticket we will try to get
13 matches
Mail list logo
