Hi Ryan,
On Sep 15, 2010, at 2:43 PM, Ryan Davis wrote:
> On Sep 15, 2010, at 10:56 , Iain Barnett wrote:
>> On 15 Sep 2010, at 18:48, Thibault Martin-Lagardette wrote:
>>>
>>> By default, macgem installs gems in
>>> /Library/Frameworks/MacRuby.framework/Versions/0.7/usr/lib/ruby/Gems/1.9.2/gems
Hi Iain,
This is really strange. Could you tell us what version of Mac OS X you run and
what version of Xcode and MacRuby you installed? Also, do you happen to run a
32-bit only Intel machine?
If you installed a new version of Xcode on top of a previous MacRuby
installation, you may want to re
On Sep 14, 2010, at 6:44 AM, Steven Parkes wrote:
>> Did you try renaming the sqlite3 macports library name, or toggle the
>> options passed to the linker when creating the library?
>
> I haven't yet. It was something I thought about, but there are a couple of
> things about dylibs on OS X that
On 2010-09-15, at 19:30 , Iain Barnett wrote:
>
> On 15 Sep 2010, at 22:43, Ryan Davis wrote:
>>
>> rubygems and/or macruby should probably be patched to include RUBY_ENGINE
>> somewhere in the gem path.
>
> That's a really good idea. Either that or just accept that macruby is a
> separate thi
how about just working nicely with rvm?
On 16/09/2010, at 1:58 PM, Ryan Davis wrote:
>
> On Sep 15, 2010, at 15:30 , Iain Barnett wrote:
>
>>
>> On 15 Sep 2010, at 22:43, Ryan Davis wrote:
>>
>>>
>>> rubygems and/or macruby should probably be patched to include RUBY_ENGINE
>>> somewhere in
On Sep 15, 2010, at 15:30 , Iain Barnett wrote:
>
> On 15 Sep 2010, at 22:43, Ryan Davis wrote:
>
>>
>> rubygems and/or macruby should probably be patched to include RUBY_ENGINE
>> somewhere in the gem path.
>
> That's a really good idea. Either that or just accept that macruby is a
> separ
On 15 Sep 2010, at 22:43, Ryan Davis wrote:
>
> rubygems and/or macruby should probably be patched to include RUBY_ENGINE
> somewhere in the gem path.
That's a really good idea. Either that or just accept that macruby is a
separate thing altogether and have MAC_GEM_PATH etc etc. Proliferation
On Sep 15, 2010, at 10:56 , Iain Barnett wrote:
>
> On 15 Sep 2010, at 18:48, Thibault Martin-Lagardette wrote:
>
>>
>> By default, macgem installs gems in
>> /Library/Frameworks/MacRuby.framework/Versions/0.7/usr/lib/ruby/Gems/1.9.2/gems
>
> Thanks. I'd ran `macgem env` and got the same out
On 15 Sep 2010, at 19:01, Thibault Martin-Lagardette wrote:
> Well, is the output EXACTLY the same? It's not for me:
>
Yep, it's exactly the same because I've a .gemrc and some env vars set in my
.profile too.
I'll install via macgems by adding the --install-dir option. Thanks for letting
m
Not knowing the release schedule for Xcode 4, is lack of support for
MacRuby in IB in Xcode 4 a blocking issue for the 0.7 release?
On Wed, Sep 15, 2010 at 12:09 PM, Felix Holmgren
wrote:
> Just out of curiosity: does this mean that the IB team are working
> independently to support MacRuby inter
Just out of curiosity: does this mean that the IB team are working
independently to support MacRuby intergration?
/F
2010/9/15 Thibault Martin-Lagardette :
> The current available version of Xcode 4 does not have MacRuby support (at
> least not in the Interface Builder part). This means IB in Xc
Well, is the output EXACTLY the same? It's not for me:
MacRuby:
- GEM PATHS:
- /Library/Frameworks/MacRuby.framework/Versions/0.7/usr/lib/ruby/Gems/1.9.2
- /Users/naixn/.gem/macruby/1.9.2
Ruby:
- GEM PATHS:
- /Library/Ruby/Gems/1.8
- /Users/naixn/.gem/ruby/1.8
-
/System/Lib
On 15 Sep 2010, at 18:48, Thibault Martin-Lagardette wrote:
>
> By default, macgem installs gems in
> /Library/Frameworks/MacRuby.framework/Versions/0.7/usr/lib/ruby/Gems/1.9.2/gems
Thanks. I'd ran `macgem env` and got the same output as `gem env` and got a bit
worried, but if you're sure it'
The current available version of Xcode 4 does not have MacRuby support (at
least not in the Interface Builder part). This means IB in Xcode 4 is not able
to find outlets or actions.
--
Thibault Martin-Lagardette
On Sep 15, 2010, at 10:09, Robert Rice wrote:
> Hi Felix:
>
> Does the new Xco
Hi!
By default, macgem installs gems in
/Library/Frameworks/MacRuby.framework/Versions/0.7/usr/lib/ruby/Gems/1.9.2/gems
You should not try to merge ruby gems and macruby gems (or make MacRuby install
/ use the ruby dir), because compiled extensions will not be compatible.
Some gems that compile
Hi Felix:
Does the new Xcode 4 have any issues with MacRuby or can we start using it as
soon as it's available?
Bob Rice
On Sep 15, 2010, at 1:02 PM, Felix Holmgren wrote:
> The link is not dead, but I had to try a bunch of times, over the
> course of a day, before I got the download to start
The link is not dead, but I had to try a bunch of times, over the
course of a day, before I got the download to start.
/F
2010/9/15 Iain Barnett :
>
> On 15 Sep 2010, at 17:35, Robert Rice wrote:
>
>> Hi Iain:
>>
>> As my app has grown IB became very, very slow to update my MacRuby class
>> info
On 15 Sep 2010, at 17:35, Robert Rice wrote:
> Hi Iain:
>
> As my app has grown IB became very, very slow to update my MacRuby class
> information. Because of that I tend to avoid using IB to link outlets.
> Instead I tag my subfields and search for then in my initialization scripts
> using v
Hi,
I see there's a `macgem` command, and I've noticed it picks up the same env as
`gem`. Is it going to screw things up if I install from both into the same
place, or should I give macgem its own special place?
Regards,
Iain
___
MacRuby-devel maili
Even if it is a known issue, which is very well may be, developer feedback is
still extremely important. Your bug could shed additional light on the
problem, could show that external developers are hitting it, or could even be
the first report anyone has seen. I know it's a pain, but external
Hi Matt:
No, I didn't. I assumed it would be a known issue.
Any idea when Xcode 4 will available for general use?
Thanks,
Bob Rice
On Sep 15, 2010, at 12:39 PM, Matt Massicotte wrote:
> Bob,
>
> Hopefully you've opened a bug on the IB performance you've observed. I'm
> sure the team would be
Bob,
Hopefully you've opened a bug on the IB performance you've observed. I'm sure
the team would be very interested in a perf problem that makes IB that unusable.
Matt
On Sep 15, 2010, at 9:35 AM, Robert Rice wrote:
> Hi Iain:
>
> As my app has grown IB became very, very slow to update my M
Hi Iain:
As my app has grown IB became very, very slow to update my MacRuby class
information. Because of that I tend to avoid using IB to link outlets. Instead
I tag my subfields and search for then in my initialization scripts using
view.viewWithTag and for my new MacRuby classes I paste in t
On 15 Sep 2010, at 17:15, Gabriel Gilder wrote:
> Have you recently updated your Xcode installation? I find that every time I
> install a new version of Xcode, I have to re-install MacRuby to get the IB
> integration to work again.
>
> -Gabriel
Woo hoo! That worked. Thanks, I did reinstall Xc
Have you recently updated your Xcode installation? I find that every time I
install a new version of Xcode, I have to re-install MacRuby to get the IB
integration to work again.
-Gabriel
On Wed, Sep 15, 2010 at 3:50 AM, Iain Barnett wrote:
> On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
>
>
On 15 Sep 2010, at 10:45, Felix Holmgren wrote:
> This might not be it, but IB is in generall pretty bad at picking up
> changes in code. Try Reload All Class Files from the File menu. When
> you're coding Objective-C you sometimes even have to do "Read All
> Class Files..." and manually point IB
This might not be it, but IB is in generall pretty bad at picking up
changes in code. Try Reload All Class Files from the File menu. When
you're coding Objective-C you sometimes even have to do "Read All
Class Files..." and manually point IB to the right header file. IB is
great in general, but thi
Hi,
Please forgive me if this is the wrong list for my questions. I'm just getting
started with MacRuby, and running through several examples (like the one here
http://www.macruby.org/documentation/tutorial.html) I've noticed that Interface
Builder doesn't always pick up stuff defined by MacRub
28 matches
Mail list logo
