From: Eloy D. <elo...@gm...> - 2008-05-30 07:24:38
|
Happens to the best of us :) Cheers, Eloy On 30 mei 2008, at 06:32, Allison Newman wrote: > Hi Eloy, > > Thanks for the tips included here for managing frameworks - I know > it's not really RubyCocoa, but then, the whole point of RubyCocoa is > to bring non-Mac ruby programmers into the mac development community, > so I guess I won't be the only person coming here that doesn't know > that :-) > > On a more general note, I update my RC to 0.13.2, but it didn't fix > the problem. So, I back-tracked a little further and discovered that > the problem was occurring before the OutlineView was ever called - > specifically, the problem is in YAML - when I read an array back in > from file, the array is initialised, and has the right size, but any > attempt to access a member of the array fails. I got fooled, because > the one time I tested the initialisation of the array, I had deleted > the file, so I created the array from defaults, not from a YAML > serialisation. Sorry to have wasted everyone's time :-/ I guess I > might end up using Cocoa archiving in the end after all... > > Alli > > > Le 29 mai 08 à 17:28, Eloy Duran a écrit : > >> Simply change the location of the RubyCocoa.framework that your >> project links against, >> by selecting it cmd+i and change the path. >> >> Also there's no problem at all with including the framework with your >> build, your users will never know! :) >> >> I have no idea what the Apple software updater does... >> >> Eloy >> >> On May 29, 2008, at 5:15 PM, Allison Newman wrote: >> >>> Yup, bizarrely, I'm running Leopard 10.5.2, so in principal at >>> least, I should have 0.13.1 >>> >>> I don't really want to take the latest build - I want to be able to >>> distribute this app as a binary, so I'm trying to always build >>> against the standard Leopard install. That said, apparently >>> something isn't right in my setup, as I haven't picked up the latest >>> version distributed with Leopard. Très bizarre! >>> >>> OK, I'm going to try installing the latest version manually, to see >>> what that gives... >>> >>> Actually, does anyone know what the Apple Software Updater does when >>> it upgrades RubyCocoa? Does it destroy the old installed version? >>> Are the two systems installed together (mine in /usr/local/bin or >>> something like that, and Apple's in /bin)? If I'm using my own >>> version in /usr/local/bin, how do I make sure that XCode picks up >>> the right version? >>> >>> I know these are not really RubyCocoa questions, but people here >>> must already know the answers, so... anyone???(hopeful look)... >>> >>> Alli >>> >>> On Thursday, May 29, 2008, at 04:37PM, "Eloy Duran" <e....@su... >>>> wrote: >>>> Ai... That's old. I was planning on discussing a new release for >>>> the >>>> next update on the dev. list tonight. >>>> But you will need to install a newer version of RC to have all the >>>> ducktyping code on NSCFArray. >>>> >>>> Eloy >>>> >>>> On May 29, 2008, at 4:33 PM, Allison Newman wrote: >>>> >>>>> 0.13.0 >>>>> >>>>> >>>>> On Thursday, May 29, 2008, at 04:15PM, "Eloy Duran" <e....@su... >>>>>> wrote: >>>>>> I know a fair bit about RC and it should do it :) >>>>>> Which version of RC are you using? >>>>>> >>>>>> You can check in the terminal: >>>>>> $ ruby -rosx/cocoa -e "p OSX::RUBYCOCOA_VERSION" >>>>>> >>>>>> Eloy >>>>>> >>>>>> On May 29, 2008, at 3:59 PM, Allison Newman wrote: >>>>>> >>>>>>> Hi Eloy, >>>>>>> >>>>>>> Yes, I have seen it :-/ >>>>>>> >>>>>>> My own code uses a standard ruby array as you have suggested, >>>>>>> but >>>>>>> when it comes back out of the view in outlineView_child_ofItem >>>>>>> (where the item is the array in question), when I try to do >>>>>>> item[index], my code blows up in the bridge (rbobj_get_ocid: >>>>>>> see my >>>>>>> original post). Interestingly enough, item.size still works >>>>>>> correctly. >>>>>>> >>>>>>> One things is sure - if I add methods to my array before handing >>>>>>> it >>>>>>> to the NSOutlineView, when I get it back those methods are no >>>>>>> longer >>>>>>> available. From that I gather that the object is modified >>>>>>> whilst >>>>>>> crossing the bridge. Maybe this is a bug, or maybe it's just >>>>>>> simply >>>>>>> that the RubyCocoa bridge was never intended to support this >>>>>>> kind of >>>>>>> use. Who knows the bridge well enough to decide? >>>>>>> >>>>>>> Anyway, as always, thanks for the reply. >>>>>>> >>>>>>> Alli >>>>>>> >>>>>>> On Thursday, May 29, 2008, at 02:51PM, "Eloy Duran" <elo...@gm... >>>>>>>> wrote: >>>>>>>> Hi Allison, >>>>>>>> >>>>>>>> Have you looked at /Developer/Examples/RubyCocoa/PDFKitViewer ? >>>>>>>> It has code for an outline view in MyPDFDocument.rb, >>>>>>>> >>>>>>>> it does use a NSMutableArray afaik, but it should be >>>>>>>> ducktypable by >>>>>>>> now. >>>>>>>> So ary.childAtIndex(index) could be written as arr[index]. >>>>>>>> So I wouldn't worry about that too much. Also if you send a >>>>>>>> plain >>>>>>>> ruby >>>>>>>> array through the bridge >>>>>>>> it will automatiucally be converted to a NSMutableArray. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Eloy >>>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------- >>>>>>> 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 >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------- >>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> 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 >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> 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 >>>> >>>> >>> >>> ------------------------------------------------------------------------- >>> 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 >> >> >> ------------------------------------------------------------------------- >> 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 > > > ------------------------------------------------------------------------- > 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 |