You can subscribe to this list here.
2002 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(3) |
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(1) |
Feb
(11) |
Mar
(9) |
Apr
(1) |
May
(5) |
Jun
(5) |
Jul
(4) |
Aug
(3) |
Sep
(15) |
Oct
(8) |
Nov
(9) |
Dec
(11) |
2004 |
Jan
(5) |
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
(6) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
|
Dec
(3) |
2005 |
Jan
(1) |
Feb
(7) |
Mar
(6) |
Apr
(36) |
May
(20) |
Jun
(42) |
Jul
(21) |
Aug
(12) |
Sep
(56) |
Oct
(5) |
Nov
(55) |
Dec
(53) |
2006 |
Jan
(43) |
Feb
(83) |
Mar
(98) |
Apr
(42) |
May
(68) |
Jun
(55) |
Jul
(50) |
Aug
(104) |
Sep
(13) |
Oct
(70) |
Nov
(37) |
Dec
(42) |
2007 |
Jan
(56) |
Feb
(18) |
Mar
(43) |
Apr
(80) |
May
(65) |
Jun
(149) |
Jul
(103) |
Aug
(71) |
Sep
(62) |
Oct
(67) |
Nov
(72) |
Dec
(63) |
2008 |
Jan
(64) |
Feb
(63) |
Mar
(31) |
Apr
(42) |
May
(71) |
Jun
(62) |
Jul
(37) |
Aug
(25) |
Sep
(5) |
Oct
(2) |
Nov
(7) |
Dec
(14) |
2009 |
Jan
(20) |
Feb
(15) |
Mar
(19) |
Apr
(8) |
May
(7) |
Jun
|
Jul
(37) |
Aug
(12) |
Sep
(19) |
Oct
(5) |
Nov
(1) |
Dec
(4) |
2010 |
Jan
(5) |
Feb
(24) |
Mar
(16) |
Apr
(9) |
May
(4) |
Jun
|
Jul
|
Aug
(6) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(5) |
Dec
|
2016 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Eloy D. <elo...@gm...> - 2008-06-11 14:14:03
|
Hey Craig, You shouldn't need to remove any gems. If you're on Leopard you have the sqlite gem by default. So if you're only targeting Leopard machines you don't need to do anything. Well except for may indeed including your own newer build of RubyCocoa.framework. Standalonify can be found inside the RubyCocoa.framework :) % ls -l /System/Library/Frameworks/RubyCocoa.framework/Versions/ Current/Tools total 72 -rw-r--r-- 1 root wheel 4093 15 dec 23:40 gen_bridge_doc.rb -rwxr-xr-x 1 root wheel 13764 15 dec 23:40 rb_nibtool.rb -rw-r--r-- 1 root wheel 12557 15 dec 23:40 standaloneify.rb Don't mind asking anything :) Cheers, Eloy On 11 jun 2008, at 16:09, Craig Williams wrote: > > On Jun 11, 2008, at 7:29 AM, Eloy Duran wrote: > >> Hey Craig, >> >> Like someone else already pointed out, you'll need to use >> standaloneify >> if you want to package libraries with your app. Like for instance the >> sqlite gem. >> http://rubycocoa.sourceforge.net/EmbedRubyCocoa >> >> Cheers, >> Eloy > > > Hi Eloy, > > I am going through the Sparkle tutorial right now. What I was wanting > to do > is *remove* the gems from my computer and install the standard way > like > Alli is doing so that I do not have to package the gems. > > From what everyone is saying this appears to be the preferable way. > > I have searched for standaloneify on my computer and have not located > it. > I do not have a Tools folder. > > Forgive my ignorance in all this. I just started learning Ruby two > weeks ago. > I am coming from AppleScript where very little *core operating system* > knowledge is required. > > I can tell you that programming in Ruby is more fun than AppleScript > and a lot less wordy. > > Anyway, thanks again for all the help. Once I get going my questions > will > become less *junior*:) > > Cheers, > > Craig > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |
From: Craig W. <cwi...@ma...> - 2008-06-11 14:09:12
|
On Jun 11, 2008, at 7:29 AM, Eloy Duran wrote: > Hey Craig, > > Like someone else already pointed out, you'll need to use > standaloneify > if you want to package libraries with your app. Like for instance the > sqlite gem. > http://rubycocoa.sourceforge.net/EmbedRubyCocoa > > Cheers, > Eloy Hi Eloy, I am going through the Sparkle tutorial right now. What I was wanting to do is *remove* the gems from my computer and install the standard way like Alli is doing so that I do not have to package the gems. From what everyone is saying this appears to be the preferable way. I have searched for standaloneify on my computer and have not located it. I do not have a Tools folder. Forgive my ignorance in all this. I just started learning Ruby two weeks ago. I am coming from AppleScript where very little *core operating system* knowledge is required. I can tell you that programming in Ruby is more fun than AppleScript and a lot less wordy. Anyway, thanks again for all the help. Once I get going my questions will become less *junior*:) Cheers, Craig |
From: Eloy D. <elo...@gm...> - 2008-06-11 13:29:27
|
Hey Craig, Like someone else already pointed out, you'll need to use standaloneify if you want to package libraries with your app. Like for instance the sqlite gem. http://rubycocoa.sourceforge.net/EmbedRubyCocoa Cheers, Eloy On 11 jun 2008, at 15:23, Craig Williams wrote: > Thanks everyone. The gems is the issue. > > Can you point me to some docs on how to remove them and use > the standard ruby libs? > > Craig > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |
From: Craig W. <cwi...@ma...> - 2008-06-11 13:23:26
|
Thanks everyone. The gems is the issue. Can you point me to some docs on how to remove them and use the standard ruby libs? Craig |
From: Patrick G. <pge...@wa...> - 2008-06-11 08:57:59
|
> The reason I asked is I created a RubyCocoa app. Did a release > build and when I tried to open it on another Leopard machine it > bounced > in the dock once and went away. Was the Leopard version on the other machine older ? Using 'old stuff', like someNSArray.length instead of someNSArray.count crashes on older versions. You'll need to bundle your version of RubyCocoa with your app if you want it to work on older Leopards. |
From: Allison N. <dem...@ma...> - 2008-06-11 06:34:20
|
Craig, You might try using the Console app to see what error messages were spat out during the launching of the app. That could give you a better idea of what's going on. >From my own experience, I have had no problems moving an app between Leopard on a G5 and Leopard on a Core 2 Duo. But then again, I haven't used any gems either, just the standard ruby libs. Alli On Wednesday, June 11, 2008, at 07:53AM, "Craig Williams" <cwi...@ma...> wrote: > >Thanks for the reply Alli. I will check out the Sparkle doc. > >The reason I asked is I created a RubyCocoa app. Did a release >build and when I tried to open it on another Leopard machine it bounced >in the dock once and went away. > >I built the app on a PPC G5 running Leopard and tried opening it on >a MacBook Pro running Leopard. > >I am using gems for sqlite3. > >Craig > >------------------------------------------------------------------------- >Check out the new SourceForge.net Marketplace. >It's the best place to buy or sell services for >just about anything Open Source. >http://sourceforge.net/services/buy/index.php >_______________________________________________ >Rubycocoa-talk mailing list >Rub...@li... >https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > > |
From: Axel M. R. <rub...@ro...> - 2008-06-11 06:04:48
|
At 23:52 -0600 10-06-2008, Craig Williams wrote: >I built the app on a PPC G5 running Leopard and tried opening it on >a MacBook Pro running Leopard. > >I am using gems for sqlite3. Did you use the standalonify tool to include the gems in your package? The system.log might show you why your ruby app crashed, in /var/log or open the Console.app. If you included a ppc only gem, it might not work on an intel machine. I must say, when I wanted to deploy my Leopard RC app on Tiger, I ended up installing RubyCocoa on the clients machine. Easier than trying to get the frameworks and all kinds of libraries included in the bundle. Axel -- _________________________ Axel Roest axelloroestello@{AIM/MSN} - Skype:axellofono - XOIP: 084-8749988 |
From: Craig W. <cwi...@ma...> - 2008-06-11 05:52:57
|
On Jun 10, 2008, at 11:04 PM, Allison Newman wrote: > When you create a RubyCocoa app, it IS a standalone app, at least if > you are deploying for Leopard, as the RubyCocoa.framework is already > installed as standard. > > If you are deploying for Tiger, you'll need to add the RubyCocoa > framework to your app bundle. > > I don't have a link to any official docs for how to do this to hand, > but if you look at this doc for installing the Sparkle framework - http://foolsworkshop.com/applescript/2008/05/adding-a-check-updates-feature/ > - it explains pretty clearly how you install a framework to be > bundled with an app. > > Actually, having written that, this leads me to wonder exactly how > version management works. I know that RubyCocoa has different > versions of the framework depending on if you are on Leopard or Tiger, > so I'm wondering how that's managed at a framework level? > > Do any of the rubycocoa dev-types on this list have any more info to > add on this? > > Alli > Thanks for the reply Alli. I will check out the Sparkle doc. The reason I asked is I created a RubyCocoa app. Did a release build and when I tried to open it on another Leopard machine it bounced in the dock once and went away. I built the app on a PPC G5 running Leopard and tried opening it on a MacBook Pro running Leopard. I am using gems for sqlite3. Craig |
From: Allison N. <dem...@ma...> - 2008-06-11 05:04:26
|
When you create a RubyCocoa app, it IS a standalone app, at least if you are deploying for Leopard, as the RubyCocoa.framework is already installed as standard. If you are deploying for Tiger, you'll need to add the RubyCocoa framework to your app bundle. I don't have a link to any official docs for how to do this to hand, but if you look at this doc for installing the Sparkle framework - http://foolsworkshop.com/applescript/2008/05/adding-a-check-updates-feature/ - it explains pretty clearly how you install a framework to be bundled with an app. Actually, having written that, this leads me to wonder exactly how version management works. I know that RubyCocoa has different versions of the framework depending on if you are on Leopard or Tiger, so I'm wondering how that's managed at a framework level? Do any of the rubycocoa dev-types on this list have any more info to add on this? Alli Le 11 juin 08 à 00:08, Craig Williams a écrit : > How do we create a stand-alone app? > > Thanks, > > Craig > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |
From: Craig W. <cwi...@ma...> - 2008-06-10 22:08:15
|
How do we create a stand-alone app? Thanks, Craig |
From: Paul N. S. <pn...@vi...> - 2008-06-08 19:23:28
|
At 9:20 AM +0200 6/8/08, Allison Newman wrote >One other thing you might try would be to reinstall RubyCocoa on >your system - it may have become corrupted somehow. > >You can download it from here: >http://sourceforge.net/project/showfiles.php?group_id=44114 > >Alli ************************* Alli, thanks ever so much! I first tried reinstalling the Developer package from the Leopard DVD. It made no difference. I then reinstalled the RubyCocoa from the source above. Everything now seems to work beautifully. Thanks for the quick and accurate help! Paul -- -- Paul Schatz Chem Dept University of Virginia |
From: Allison N. <dem...@ma...> - 2008-06-07 20:59:54
|
Hmmm, I get the impression that your system thinks that your RubyCocoa framework is PPC, not Intel. Have you tried building a RubyCocoa project by hand? That is, 1) Create a Cocoa application project. Build it and run to very that this works 2) Right click on the project item to the left of the project window. Select 'Add Existing Framework'. Choose /System/Library/Frameworks/ RubyCocoa.framework 3) Replace the main.m from a main.m that you have in a rubycocoa project that you have already 4) Add a copy of rb_main.rb from a RubyCocoa project. 5) in the rb_main.rb file, add a puts statement at the end of rb_main_init so that you can see that ruby is running. 6) Run the app. Verify that the trace that you add shows up in the console. Verify that the app runs. Anyway, give that a go, maybe it will at least give you a clue as to what is going wrong. Alli Le 7 juin 08 à 21:25, Paul N. Schatz a écrit : > Allison, many thanks for the help. I intersperse below replies to > your various suggestions. I think the information will be helpful to > you: > > At 1:10 AM -0700 6/6/08, Allison Newman wrote >> Hi Paul, >> >> Hmmm, I assume that you've done a Clean All on the project? > > ***************** > > Yes, I did that. It made no difference. > > ************************ > >> >> Have you tried runing dsymutil on the app executable? That might >> give you some useful info. cd to >> $ProjectDir/build/Debug/$AppName/$AppName.app/Contents/MacOS, and >> then run the command >> >> dsymutil -s $AppName >> >> Substituting appropriate values for $ProjectDir and $AppName, of >> course... > > ****************************** > > I did a cd ~/Documents/Programming/Ruby/RubyToCocoa16/build/ > Development/RubyToCocoa1.app/Contents/MacOS > > and ran dsymutil -s RubyToCocoa1.app with the reply, error: unable > to open executable 'RubyToCocoa1.app' > > This was predictable; the icon on the application had a circle with > a line through it. The permissions on the app were 755. > > ************************* > >> >> Otherwise, it looks like your system is having trouble picking up >> the RubyCocoa framework. Previously on your G5 Mac, had you >> bundled the framework with the app, or were you using the standard >> system framework? If so, you will need to remove the bundled >> framework. > > ************************ > > As far as I know, I was using the standard system framework. > > ************************ > >> >> Another suggestion/question, what happens when you create a new >> RubyCocoa project on the Intel Mac? Does it work? What version of >> RubyCocoa is it using? (you can get this info by putting : > > ************************** > I think this is very illuminating: I created a new RubyCocoa > application in the same directory as my other ruby programs and > simply clicked on Build and Go and got the following response" > > Building target "test060708" of project "test060708" with > configuration "Release" - (1 error, 1 warning) > cd /Users/pnschatz/Documents/Programming/Ruby > /Developer/usr/bin/gcc-4.0 -o /Users/pnschatz/Documents/ > Programming/Ruby/build/test060708.build/Release/test060708.build/ > Objects-normal/i386/test060708 -L/Users/pnschatz/Documents/ > Programming/Ruby/build/Release -F/Users/pnschatz/Documents/ > Programming/Ruby/build/Release -filelist /Users/pnschatz/Documents/ > Programming/Ruby/build/test060708.build/Release/test060708.build/ > Objects-normal/i386/test060708.LinkFileList -framework Cocoa - > framework RubyCocoa -arch i386 -mmacosx-version-min=10.5 -isysroot / > Developer/SDKs/MacOSX10.5.sdk > ld: warning in /Developer/SDKs/MacOSX10.5.sdk/Library/Frameworks// > RubyCocoa.framework/RubyCocoa, file is not of required architecture > Undefined symbols: > "_RBApplicationMain", referenced from: > _main in main.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > ld: warning in /Developer/SDKs/MacOSX10.5.sdk/Library/Frameworks// > RubyCocoa.framework/RubyCocoa, file is not of required architecture > "_RBApplicationMain", referenced from: > _main in main.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > Build failed (1 error, 1 warning) " > ************************ > >> >> require 'osx/cocoa' >> >> puts OSX::RUBYCOCOA_VERSION >> >> at the top level in one of your ruby source files for the project. > > > *********************** > > I put in the command ruby -v, and got the response: > > ruby 1.8.6 (2007-09-24 patchlevel 111) [universal-darwin9.0] > > *********************** > >> >> Hopefully something above will help give you a better insight into >> what's happening on your system. If not, well, you can always tell >> us the results of the tests, and maybe we'll be able to come up >> with a better idea :-) >> >> Alli >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Rubycocoa-talk mailing list >> Rub...@li... >> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > > > -- > -- > Paul Schatz > Chem Dept > University of Virginia |
From: Paul N. S. <pn...@vi...> - 2008-06-07 19:25:33
|
Allison, many thanks for the help. I intersperse below replies to your various suggestions. I think the information will be helpful to you: At 1:10 AM -0700 6/6/08, Allison Newman wrote >Hi Paul, > >Hmmm, I assume that you've done a Clean All on the project? ***************** Yes, I did that. It made no difference. ************************ > >Have you tried runing dsymutil on the app executable? That might >give you some useful info. cd to >$ProjectDir/build/Debug/$AppName/$AppName.app/Contents/MacOS, and >then run the command > >dsymutil -s $AppName > >Substituting appropriate values for $ProjectDir and $AppName, of course... ****************************** I did a cd ~/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS and ran dsymutil -s RubyToCocoa1.app with the reply, error: unable to open executable 'RubyToCocoa1.app' This was predictable; the icon on the application had a circle with a line through it. The permissions on the app were 755. ************************* > >Otherwise, it looks like your system is having trouble picking up >the RubyCocoa framework. Previously on your G5 Mac, had you bundled >the framework with the app, or were you using the standard system >framework? If so, you will need to remove the bundled framework. ************************ As far as I know, I was using the standard system framework. ************************ > >Another suggestion/question, what happens when you create a new >RubyCocoa project on the Intel Mac? Does it work? What version of >RubyCocoa is it using? (you can get this info by putting : ************************** I think this is very illuminating: I created a new RubyCocoa application in the same directory as my other ruby programs and simply clicked on Build and Go and got the following response" Building target "test060708" of project "test060708" with configuration "Release" - (1 error, 1 warning) cd /Users/pnschatz/Documents/Programming/Ruby /Developer/usr/bin/gcc-4.0 -o /Users/pnschatz/Documents/Programming/Ruby/build/test060708.build/Release/test060708.build/Objects-normal/i386/test060708 -L/Users/pnschatz/Documents/Programming/Ruby/build/Release -F/Users/pnschatz/Documents/Programming/Ruby/build/Release -filelist /Users/pnschatz/Documents/Programming/Ruby/build/test060708.build/Release/test060708.build/Objects-normal/i386/test060708.LinkFileList -framework Cocoa -framework RubyCocoa -arch i386 -mmacosx-version-min=10.5 -isysroot /Developer/SDKs/MacOSX10.5.sdk ld: warning in /Developer/SDKs/MacOSX10.5.sdk/Library/Frameworks//RubyCocoa.framework/RubyCocoa, file is not of required architecture Undefined symbols: "_RBApplicationMain", referenced from: _main in main.o ld: symbol(s) not found collect2: ld returned 1 exit status ld: warning in /Developer/SDKs/MacOSX10.5.sdk/Library/Frameworks//RubyCocoa.framework/RubyCocoa, file is not of required architecture "_RBApplicationMain", referenced from: _main in main.o ld: symbol(s) not found collect2: ld returned 1 exit status Build failed (1 error, 1 warning) " ************************ > >require 'osx/cocoa' > >puts OSX::RUBYCOCOA_VERSION > >at the top level in one of your ruby source files for the project. *********************** I put in the command ruby -v, and got the response: ruby 1.8.6 (2007-09-24 patchlevel 111) [universal-darwin9.0] *********************** > >Hopefully something above will help give you a better insight into >what's happening on your system. If not, well, you can always tell >us the results of the tests, and maybe we'll be able to come up with >a better idea :-) > >Alli > >------------------------------------------------------------------------- >Check out the new SourceForge.net Marketplace. >It's the best place to buy or sell services for >just about anything Open Source. >http://sourceforge.net/services/buy/index.php >_______________________________________________ >Rubycocoa-talk mailing list >Rub...@li... >https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk -- -- Paul Schatz Chem Dept University of Virginia |
From: Allison N. <dem...@ma...> - 2008-06-06 08:10:37
|
Hi Paul, Hmmm, I assume that you've done a Clean All on the project? Have you tried runing dsymutil on the app executable? That might give you some useful info. cd to $ProjectDir/build/Debug/$AppName/$AppName.app/Contents/MacOS, and then run the command dsymutil -s $AppName Substituting appropriate values for $ProjectDir and $AppName, of course... Otherwise, it looks like your system is having trouble picking up the RubyCocoa framework. Previously on your G5 Mac, had you bundled the framework with the app, or were you using the standard system framework? If so, you will need to remove the bundled framework. Another suggestion/question, what happens when you create a new RubyCocoa project on the Intel Mac? Does it work? What version of RubyCocoa is it using? (you can get this info by putting : require 'osx/cocoa' puts OSX::RUBYCOCOA_VERSION at the top level in one of your ruby source files for the project. Hopefully something above will help give you a better insight into what's happening on your system. If not, well, you can always tell us the results of the tests, and maybe we'll be able to come up with a better idea :-) Alli |
From: Paul N. S. <pn...@vi...> - 2008-06-05 19:38:03
|
I am a beginner with RubyCocoa. I recently transitioned from a G5 (PowerPC) running OS 10.5 to an early 2008 Mac Pro (Intel) running OS 10.5.2. All of my pure Coca programs and all of my pure Ruby programs run fine with XCode 3.0 on the new machine. But all of my RubyCocoa programs fail with essentially the same 2 errors. I paste in a typical error report just below. I don't have a clue what to do and would appreciate any suggestions. Paul *************************** Building target "RubyToCocoa16" of project "RubyToCocoa16" with configuration "Development" - (2 errors) cd /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16 /Developer/Private/jam -d1 -j8 JAMBASE=/Developer/Makefiles/pbx_jamfiles/ProjectBuilderJambase JAMFILE=/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/RubyToCocoa16.build/Development/RubyToCocoa16.build/RubyToCocoa16.jam build ACTION=build _DEFAULT_GCC_VERSION=4.0 GCC_VERSION_IDENTIFIER=__0 CONFIGURATION=Development BUILD_STYLE=Development CPP_HEADERMAP_FILE=/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/RubyToCocoa16.build/Development/RubyToCocoa16.build/RubyToCocoa1.hmap SRCROOT=/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16 OBJROOT=/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build SYMROOT=/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build DSTROOT=/tmp/RubyToCocoa16.dst StandaloneExecutable /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... ...failed StandaloneExecutable.LinkUsingFileList /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 ... /Developer/usr/bin/gcc-4.0 -o /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development/RubyToCocoa1.app/Contents/MacOS/RubyToCocoa1 "-L/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development" "-F/Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/Development" -filelist /Users/pnschatz/Documents/Programming/Ruby/RubyToCocoa16/build/RubyToCocoa16.build/Development/RubyToCocoa16.build/Objects-normal/LinkFileList "-arch" "i386" "-Wl,-no_arch_warnings" "-framework" "Cocoa" "-framework" "RubyCocoa" Undefined symbols: "_RBApplicationMain", referenced from: _main in main.o ld: symbol(s) not found collect2: ld returned 1 exit status "_RBApplicationMain", referenced from: _main in main.o ld: symbol(s) not found collect2: ld returned 1 exit status Build failed (2 errors) -- -- Paul Schatz Chem Dept University of Virginia |
From: Patrick G. <pge...@wa...> - 2008-06-05 16:48:17
|
> Is the equivalent Ruby this? > > def transformedValueClass; NSNumber; end Yes. As Ruby's 'class' method shadows ObjC's, you can call the original ObjC method with the oc_ prefix and check equivalence with puts SomeClass == SomeClass.oc_class -> true > Is that true if the class is defined in Ruby. Like this, for example: > > class Whatever < OSX::NSObject > end Yes. -Patrick |
From: Allison N. <dem...@ma...> - 2008-06-05 07:44:10
|
Killing the timer is easy, just call invalidate.. @timer.invalidate. If you actually want to free the timer, you could also set @timer to nil after invalidating. For the rest, what loop are you talking about? You don't have any loops in the code that you have shown to the mailing list. I'm nevertheless going to try and guess what's going on. Elsewhere in your code, you have a loop, using @c as the index, with a max value of @file_count, right? And you run through this loop in Ruby code, but you want the timer to update the display whilst this loop executes, right? You're going to need threads to do that. Try putting your loop in a seperate Ruby thread. That may help. The code will look something like this: @timer = NSTimer .scheduledTimerWithTimeInterval_target_selector_userInfo_repeats(0.2, self, :update_run_count, nil, true) Thread.new do @c = 0 while @c < @file_count # do stuff here @c += 1 end @timer.invalidate end But multi-threading is a weakpoint for Ruby at the moment, so you may have other problems. Anyway, I hope that helps. Alli On Thursday, June 05, 2008, at 12:05AM, "Craig Williams" <cwi...@ma...> wrote: > >On Jun 4, 2008, at 2:18 AM, Axel M. Roest wrote: > >> At 15:19 -0600 03-06-2008, Craig Williams wrote: >>> I have a button that when clicked runs a process. I would like a >>> text field to show the value of where this process is >>> in it's iterations. It appears that one way to do this is to setup >>> a timer and have the time handle the operation. >>> >>> Here is the timer: >>> >>> timer = >>> NSTimer >>> .scheduledTimerWithTimeInterval_target_selector_userInfo_repeats_ >>> (0.2, self, 'update_run_count:', nil, YES) >> > >Thanks everyone. That fixed the crashing. > >The app still does not update the text field and nothing logs to the >console until after the loop has >finished. Then it is logging "Processing 10 of 9" ( if 9 elements >were processed in the loop. ) > >I am sure I just do not understand how the timer is implemented or how >to kill it when it is finished. > >Thanks, > >Craig > >------------------------------------------------------------------------- >Check out the new SourceForge.net Marketplace. >It's the best place to buy or sell services for >just about anything Open Source. >http://sourceforge.net/services/buy/index.php >_______________________________________________ >Rubycocoa-talk mailing list >Rub...@li... >https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > > |
From: Craig W. <cwi...@ma...> - 2008-06-04 22:05:26
|
On Jun 4, 2008, at 2:18 AM, Axel M. Roest wrote: > At 15:19 -0600 03-06-2008, Craig Williams wrote: >> I have a button that when clicked runs a process. I would like a >> text field to show the value of where this process is >> in it's iterations. It appears that one way to do this is to setup >> a timer and have the time handle the operation. >> >> Here is the timer: >> >> timer = >> NSTimer >> .scheduledTimerWithTimeInterval_target_selector_userInfo_repeats_ >> (0.2, self, 'update_run_count:', nil, YES) > Thanks everyone. That fixed the crashing. The app still does not update the text field and nothing logs to the console until after the loop has finished. Then it is logging "Processing 10 of 9" ( if 9 elements were processed in the loop. ) I am sure I just do not understand how the timer is implemented or how to kill it when it is finished. Thanks, Craig |
From: Brian M. <ma...@ex...> - 2008-06-04 18:33:19
|
Suppose I see objective-C documentation that says I need to define a method that returns a Class. Here's an Objective-C example: + (Class)transformedValueClass { return [NSNumber class]; } Is the equivalent Ruby this? def transformedValueClass; NSNumber; end Is that true if the class is defined in Ruby. Like this, for example: class Whatever < OSX::NSObject end Thanks. ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant www.exampler.com, www.exampler.com/blog, www.twitter.com/marick |
From: Motohiro T. <mo...@gm...> - 2008-06-04 13:11:29
|
oooooooooooooooooooook ! Thanks for replying. On Wed, Jun 4, 2008 at 1:55 AM, Patrick Geiller <pge...@wa...> wrote: > > NameError: uninitialized constant QCPlugin > > It's QCPlugIn, with a capital i. One of those treacherous names :) > > -Patrick > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk > |
From: Axel M. R. <rub...@ro...> - 2008-06-04 08:19:07
|
At 15:19 -0600 03-06-2008, Craig Williams wrote: >I have a button that when clicked runs a process. I would like a >text field to show the value of where this process is >in it's iterations. It appears that one way to do this is to setup a >timer and have the time handle the operation. > >Here is the timer: > >timer = >NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats_(0.2, >self, 'update_run_count:', nil, YES) What works for me, is ditch the : in the selector, and I use true instead of YES. Booleans are still vaguely converted in the bridge, IMHO of course NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats_(0.2, self, 'update_run_count', nil, true) Oh and another very important thing: in your code, the timer is destroyed after the function finishes. You have to use an instance variable with @, thus: @timer=NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats(0.2,self,"updateLog",nil,true) The above line comes from my code which is almost a verbatim copy of yours. Axel -- _________________________ Axel Roest axelloroestello@{AIM/MSN} - Skype:axellofono - XOIP: 084-8749988 |
From: Eloy D. <elo...@gm...> - 2008-06-04 07:59:59
|
Hi Craig, I would like to know what happens at line 34 of AppControler? As that seems to be where the problem occurs. Eloy > Here is the crash log. > 2008-06-03 15:17:38.203 ScriptWindow[7730:10b] AppControler#button: > SystemStackError: stack level too deep > /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ > objc/oc_import.rb:154:in `new' > /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ > objc/oc_import.rb:154:in `import_c_constant' > /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ > objc/oc_import.rb:154:in `const_missing' > /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ > objc/oc_import.rb:167:in `_osx_const_missing_prev' > /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ > objc/oc_import.rb:169:in `const_missing' > /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ > ScriptWindow.app/Contents/Resources/AppControler.rb:34:in `button' > /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ > ScriptWindow.app/Contents/Resources/rb_main.rb:23:in > `NSApplicationMain' > /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ > ScriptWindow.app/Contents/Resources/rb_main.rb:23 > /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ > objc/oc_import.rb:154:in `new': stack level too deep > (SystemStackError) > from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ > osx/objc/oc_import.rb:154:in `import_c_constant' > from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ > osx/objc/oc_import.rb:154:in `const_missing' > from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ > osx/objc/oc_import.rb:167:in `_osx_const_missing_prev' > from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ > osx/objc/oc_import.rb:169:in `const_missing' > from /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ > ScriptWindow.app/Contents/Resources/AppControler.rb:34:in `button' > from /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ > ScriptWindow.app/Contents/Resources/rb_main.rb:23:in > `NSApplicationMain' > from /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ > ScriptWindow.app/Contents/Resources/rb_main.rb:23 > > The Debugger has exited with status 1.The Debugger has exited with > status 1. > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php_______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |
From: Craig W. <cwi...@ma...> - 2008-06-03 21:19:16
|
I have a button that when clicked runs a process. I would like a text field to show the value of where this process is in it's iterations. It appears that one way to do this is to setup a timer and have the time handle the operation. Here is the timer: timer = NSTimer .scheduledTimerWithTimeInterval_target_selector_userInfo_repeats_(0.2, self, 'update_run_count:', nil, YES) Here is the called function. def update_run_count(timer) text = "Processing #{@c} of #{@file_count}" puts text @text_field.setStringValue(text) @text_field.setTextColor(NSColor.redColor) end Anyone see what I am missing? Thanks. This crashes the program as soon as I click the button. Here is the crash log. 2008-06-03 15:17:38.203 ScriptWindow[7730:10b] AppControler#button: SystemStackError: stack level too deep /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ objc/oc_import.rb:154:in `new' /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ objc/oc_import.rb:154:in `import_c_constant' /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ objc/oc_import.rb:154:in `const_missing' /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ objc/oc_import.rb:167:in `_osx_const_missing_prev' /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/ objc/oc_import.rb:169:in `const_missing' /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ ScriptWindow.app/Contents/Resources/AppControler.rb:34:in `button' /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ ScriptWindow.app/Contents/Resources/rb_main.rb:23:in `NSApplicationMain' /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ ScriptWindow.app/Contents/Resources/rb_main.rb:23 /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/osx/objc/ oc_import.rb:154:in `new': stack level too deep (SystemStackError) from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ osx/objc/oc_import.rb:154:in `import_c_constant' from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ osx/objc/oc_import.rb:154:in `const_missing' from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ osx/objc/oc_import.rb:167:in `_osx_const_missing_prev' from /System/Library/Frameworks/RubyCocoa.framework/Resources/ruby/ osx/objc/oc_import.rb:169:in `const_missing' from /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ ScriptWindow.app/Contents/Resources/AppControler.rb:34:in `button' from /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ ScriptWindow.app/Contents/Resources/rb_main.rb:23:in `NSApplicationMain' from /Users/craig/_Xcode_Proj/__Ruby__/ScriptWindow/build/Debug/ ScriptWindow.app/Contents/Resources/rb_main.rb:23 The Debugger has exited with status 1.The Debugger has exited with status 1. |
From: Patrick G. <pge...@wa...> - 2008-06-03 16:55:37
|
> NameError: uninitialized constant QCPlugin It's QCPlugIn, with a capital i. One of those treacherous names :) -Patrick |
From: Motohiro T. <mo...@gm...> - 2008-06-03 16:47:57
|
Hello, I'm trying to use QCPlugin interface from QuartzComposer framework, but cannot manage to do that. Does anybody have any suggestion? I follow this page: http://rubycocoa.sourceforge.net/RequireFramework and type following in irb session: % require 'osx/cocoa' => true % OSX.require_framework '/System/Library/Frameworks/Quartz.framework/Frameworks/QuartzComposer.framework' => true % OSX::QCPatch => OSX::QCPatch % OSX::QCPlugin NameError: uninitialized constant QCPlugin QCPlugin is defined in /System/Library/Frameworks/Quartz.framework/Frameworks/QuartzComposer.framework/Headers/QCPlugin.h . I don't know why that is not found. I'm using Leopard 10.5.3 and bundled RubyCocoa. Thanks reading, |