By the way, I did a quick demo of HotCocoa for Matz and he was pretty
impressed. He even said: "I will have to play with that when I will buy a
Mac ;)"
First I was totally shocked(in a good way) to hear that Matz is considering
buying a Mac and then I was like wow, if Matz sees something in
Ho
I just did:
$ /opt/local/bin/ruby tool/compile_prelude.rb prelude.rb miniprelude.c.new
and nothing happens, nothing in the console either. I have Ruby 1.8.6
installed by macports, could that cause a problem?
-Matt
On Sun, Nov 9, 2008 at 2:54 PM, Laurent Sansonetti <[EMAIL PROTECTED]>wrote:
>
On Nov 9, 2008, at 8:57 PM, Benjamin Stiglitz wrote:
Rich, Laurent and I talked about this at length this weekend, and I
think we can safely say that we’d to improve upon Cocoa and Mac OS X
development in Ruby.
One example we cooked up was this:
play_sound do |t|
sin(440.0 * t * 2.0 * Ma
So, which is it, guys? A glorified macro pre-processor with enough
canned macros to illustrate how to use the same approach in your own
applications, or an attempt to simplify Cocoa programming where it
genuinely cries out for simplification, hopefully also in cases
which are commonly used
On Nov 9, 2008, at 3:10 PM, Jordan K. Hubbard wrote:
On Nov 9, 2008, at 2:50 PM, Laurent Sansonetti wrote:
Sure, when the app in question is a MacRuby app then we can do that
(there is AFAIK no need to start a new thread, the console can be
in the runloop.)
Ah, that's even better, yes.
On Nov 9, 2008, at 2:50 PM, Laurent Sansonetti wrote:
Sure, when the app in question is a MacRuby app then we can do that
(there is AFAIK no need to start a new thread, the console can be in
the runloop.)
Ah, that's even better, yes.
But here Daniel was referring to using MacRuby inside a
#142: Infinite loop creating new Monitor object
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: major
On Nov 9, 2008, at 2:41 PM, Jordan K. Hubbard wrote:
On Nov 9, 2008, at 11:57 AM, Laurent Sansonetti wrote:
This could potentially be possible, if the objc code runs in the GC
environment. You could load MacRuby.framework from GDB (using
NSBundle), then initialize the runtime ([MacRuby sha
#74: DTrace / Instruments.app Support
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: blocker|Mile
#75: 64-bit Support
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: closed
Priority: blocker|Milestone: MacRuby 0.
#144: require of hotcocoa fails on case sensitive file system
---+
Reporter: [EMAIL PROTECTED] |Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: trivial
On Nov 9, 2008, at 11:57 AM, Laurent Sansonetti wrote:
This could potentially be possible, if the objc code runs in the GC
environment. You could load MacRuby.framework from GDB (using
NSBundle), then initialize the runtime ([MacRuby sharedRuntime])
then start an IRB session, by evaluating
On Nov 9, 2008, at 7:13 AM, Eloy Duran wrote:
I like the idea of HotCocoa, but it should not go too far, and this
is maybe taking it one step too far imo.
The problem is that at some point you _will_ have to use real Cocoa,
because HotCocoa can't wrap everything.
If you are frightened by the
How would that work to open a local file?
-Matt
Sent from my iPhone
On Nov 9, 2008, at 14:53, Laurent Sansonetti <[EMAIL PROTECTED]>
wrote:
While I agree that HotCocoa should not aspire to wrap all APIs, I
think that providing a mapping file for NSWorkspace is nevertheless
a good idea.
This could potentially be possible, if the objc code runs in the GC
environment. You could load MacRuby.framework from GDB (using
NSBundle), then initialize the runtime ([MacRuby sharedRuntime]) then
start an IRB session, by evaluating the right expression (-
[evaluateString:]).
Otherwise
Mmh I suspect it is the broken strscan.bundle problem again.
What does happen if you type the following from the source directory?
$ /usr/bin/ruby tool/compile_prelude.rb prelude.rb miniprelude.c.new
If you get a segmentation fault, could you attach the crash log from
Console.app?
Thanks,
L
While I agree that HotCocoa should not aspire to wrap all APIs, I
think that providing a mapping file for NSWorkspace is nevertheless a
good idea.
#workspace could return the shared workspace by default (I'm not even
sure if you can get a different workspace instance) then we could
create
Hi Eloy,
I think that what Matt is talking about here is that when you do
macrake from a HotCocoa project directory the application would not be
open(1)'ed but directly ran from the terminal session, so that if
there is a runtime exception you would see the Ruby backtrace in the
terminal.
Hello List,
Not sure about the feasibility of this, but wouldn't it be great to
break out into an embedded macirb session from inside GDB? Exploring
the state of a running application this way could really help with
debugging objc code.
If anyone has insights on how this could be accomplished I'
Have you tried building it without using RubyGems?
- Eloy
On 9 nov 2008, at 16:14, Matt Aimonetti wrote:
DM uses DO which uses C extensions and C drivers. I'm not sure how
to get DM working with MacRuby yet :(
-Matt
On Sun, Nov 9, 2008 at 10:09 AM, Eloy Duran
<[EMAIL PROTECTED]> wrote:
I
On 9 nov 2008, at 16:19, Matt Aimonetti wrote:
hmm I guess I disagree but since I just got started with MacRuby and
don't know Cocoa I might be totally wrong.
Yes, this is what I thought too when first starting with Cocoa in
RubyCocoa, but I was very wrong.
Most helpful docs/references are
[EMAIL PROTECTED] trunk]$ rake --trace
(in /Users/mattetti/src/MacRuby/trunk)
** Invoke default (first_time)
** Invoke all (first_time)
** Invoke macruby (first_time)
** Invoke macruby:build (first_time)
** Invoke macruby:dylib (first_time)
** Invoke rbconfig (first_time)
** Invoke miniruby (first_
hmm I guess I disagree but since I just got started with MacRuby and don't
know Cocoa I might be totally wrong.
My hope is to have all the common cocoa methods available in Ruby so I can
quickly create simple apps without always having to dig into the cocoa
documentation and create this kind of su
DM uses DO which uses C extensions and C drivers. I'm not sure how to get DM
working with MacRuby yet :(
-Matt
On Sun, Nov 9, 2008 at 10:09 AM, Eloy Duran <[EMAIL PROTECTED]> wrote:
> I wonder if it really would add much benefit to add a CoreData DM adapter…
> I would just use DM with sqlite, wi
Hi,
I like the idea of HotCocoa, but it should not go too far, and this is
maybe taking it one step too far imo.
The problem is that at some point you _will_ have to use real Cocoa,
because HotCocoa can't wrap everything.
If you are frightened by the verbosity of this line of code, well than
I wonder if it really would add much benefit to add a CoreData DM
adapter…
I would just use DM with sqlite, without CoreData adding an extra
layer of abstraction.
This works in RubyCocoa, so except for maybe some incompatibilities
with 1.9/MacRuby
it should work great as well.
Eloy
On 9 no
Hi Matt,
This is a crash report submit plugin I wrote.
It currently only supports RubyCocoa, but I guess it would be trivial
to get it to run on MacRuby.
Maybe Laurent already ported it, because it's used by LimeChat as well:
http://rucola.rubyforge.org/svn/extras/plugins/SACrashReporter/
Ch
Here is what I had to do after Laurent showed me how to open an URL in the
browser:
NSWorkspace.sharedWorkspace.openURL(NSURL.URLWithString("http://google.com";)
I wish this would be wrapped in a simpler way.
open_url_in_browser("http://google.com";)
open_file_in_browser("./resources/schedule.ht
I need to be able to store and retrieve data between app runs. Having a
simple API to access Core Data or creating a Core Data DataMapper adapter
would be awesome.
I guess the alternative would be to package a sqlite3 ruby gem compiled for
OSX.
-Matt
__
Hi,
It would be great to be able to see a full stack trace/log when running a
macruby app. It would also be nice to be able to output to the log directly
from Ruby.
I guess, it would be even better if you could decide to choose how to log
(STDOUT or a file) so you could debug deployed apps by ask
30 matches
Mail list logo