Seems to be working for me, and the UI of the search results looks very
nice. Congratulations on the app!
A few little bugs/notes:
- In the Preferences dialog you have a typo, "Googe Docs".
- When you open the Preferences dialog, and then switch out of the app (like
say to go find your credentia
On 2011-03-14, at 16:05, Laurent Sansonetti wrote:
> Hi Mark,
>
> As macrubyc's compilation logic is essentially spawning several command-line
> tools, I wonder if calling the logic directly from macruby_deploy is going to
> bring significant advantages, vs the complexity of splitting macrubyc
Xcode4 doesn't have any MacRuby templates yet and features that weren't
working in Xcode 3 still don't work in Xcode 4 (indexation, debugger
etc...).
However, everything else works fine. I would wait until we release 0.10 with
the Xcode 4 templates to switch tho (should be really soon now, Thibault
Hi:
Is MacRuby fully compatible with Xcode 4 or should I wait a while before
upgrading?
Thanks,
Bob Rice
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi Morgan,
Well in theory, you should NOT get a segfault when doing that.
When an exception isn't rescued inside a Thread, the correct behavior is that
the thread will quit, and that the exception will be silently ignored. Then,
once the Thread object is garbage collected, if the exception has
Hi Christian,
These tests should probably be removed, they are not used anymore (these were
used before we switched to RubySpec).
The correct thing to do is probably make a macruby spec (under the spec/macruby
directory).
How do you intend to change #framework exactly? Maybe you should work on
Hi Mark,
As macrubyc's compilation logic is essentially spawning several command-line
tools, I wonder if calling the logic directly from macruby_deploy is going to
bring significant advantages, vs the complexity of splitting macrubyc.
I think a better strategy would be to optimize what's slow i
On Mar 14, 2011, at 10:35 AM, Morgan Schweers wrote:
> Greetings,
>
> On Mon, Mar 14, 2011 at 6:57 AM, Matt Massicotte wrote:
> If you find this exception-shifting behavior troubling, please open a ticket.
>
> What bugs me about the behavior in this case is that if the exact same
> operation
Greetings,
On Mon, Mar 14, 2011 at 6:57 AM, Matt Massicotte wrote:
> If you find this exception-shifting behavior troubling, please open a
> ticket.
>
What bugs me about the behavior in this case is that if the exact same
operation is done on the main thread, it throws a very nice, normal Ruby
e
If you find this exception-shifting behavior troubling, please open a ticket.
Could you explain why introducing the begin/rescue pair that is good
programming practice?
Matt
On Mar 13, 2011, at 6:31 PM, Morgan Schweers wrote:
> Greetings,
> Today I Learned :) if a thread throws an exception th
Oh yes, I also had this problem, but forgot to mention it in my email to you.
I'm not sure if I got my password wrong at first, but I was unable to log in
even when I was sure I had the right credentials.
On 14 Mar 2011, at 12:21, Eloy Duran wrote:
> The app now works :) However, I had filled i
The app now works :) However, I had filled in the wrong google
credentials the first time, after which it was impossible for me to
get it to use the right ones. It seems that it keeps using the
password I had entered the first time. Basecamp search worked fine.
On Mon, Mar 14, 2011 at 12:04 AM, An
12 matches
Mail list logo
