Hi Timo,
> a) Is it really THAT complicated to create an instance of MyEntity and set
> the attribute? I'm coming from the Rails/ActiveRecord world where this could
> easily be done with a single line of code (including saving the instantiated
> object): MyEntity.new(:attribute1 => "Test").save
Hi Timo,
I've found something more like ActiveRecord; it's a
framework https://github.com/magicalpanda/MagicalRecord!
everything is written in Objective-C, but you can use it with MacRuby! you
get syntax like:
person = Person...;
MRCoreDataAction.saveDataInBackgroundWithBlock -> localContext do
Hi,
Am 14.11.2011 um 09:47 schrieb Sven A. Schmidt:
>> a) Is it really THAT complicated to create an instance of MyEntity and set
>> the attribute? I'm coming from the Rails/ActiveRecord world where this could
>> easily be done with a single line of code (including saving the instantiated
>> ob
As a reminder you can get MacRuby to talk to JS in a webkit instance as
shown there:
https://github.com/mattetti/RubyConfX-code/blob/master/ps3controller/demo.rb#L16-18
On Mon, Nov 14, 2011 at 2:20 AM, Michael Pitra wrote:
>
> I have a similar approach in one of my applications: a WebKit view
>
Reading from many messages on this list, I get the impression that MacRuby
users are more often than not Ruby programmers coming to Mac programming.
I come from the opposite side: I am an experienced Cocoa developer and Ruby
newbie.
I came to MacRuby for one major reason (and perhaps a few seco
Very good point Jean Denis. You are totally right, it shouldn't be hard to
reload all the Ruby source while the code is running. One thing tho, you
might also have to reset the state of your application, including its
drawing state. But maybe we could leave that up to the developers.
What I'm think
On 14 Nov 2011, at 8:15 AM, Jean-Denis MUYS wrote:
> My vision of speeding up Mac development is basically to finally reach again
> what I had almost 20 years ago when I was programming in Macintosh Common
> Lisp on the Mac for the Mac: developing within a running application, without
> having
this would certainly be useful, but frankly i think that having proper
debugger-integration support in xcode (see
http://www.macruby.org/trac/ticket/1208 and issue 3037631 in
http://bugreporter.apple.com) would go dramatically farther towards making
macruby useful. edit-and-continue would be great,
I extracted an old demo I had made for RubyConf which shows how to use the
voice recognizer feature of OS X to implement an app which could be the
Siri equivalent for OS X:
https://github.com/mattetti/MacRuby-Siri
The code is straight forward, the app runs in the top menu. Don't forget to
turn on
On 14 nov. 2011, at 17:54,
mailto:macruby-devel-requ...@lists.macosforge.org>>
wrote:
Date: Mon, 14 Nov 2011 08:53:14 -0800
From: Nat Brown mailto:nat...@gmail.com>>
To: "MacRuby development discussions."
mailto:macruby-devel@lists.macosforge.org>>
Subject: Re: [MacRuby-devel] MacRuby promise
M
>
> I probably even could implement a rough bare bone version.
I'm currently traveling but I would be glad to assist you.
- Matt
On Mon, Nov 14, 2011 at 2:09 PM, Jean-Denis MUYS wrote:
>
> On 14 nov. 2011, at 17:54,
> wrote:
>
> Date: Mon, 14 Nov 2011 08:53:14 -0800
> From: Nat Brown
> T
you are right, of course -- these two issues are orthogonal, I simply never
pass up a chance to rant about lack of debug support on the off chance that
everybody will up-vote this issue and we'll see it get fixed before another
5 years pass.
if you implement your suggestion, i will certainly try it
On 15/11/2011, at 5:15 AM, Jean-Denis MUYS wrote:
> To me, this is the major MacRuby promise, and that promise is not kept yet.
>
> Am I out of my mind?
I don't recall anyone ever making this promise.
Henry
___
MacRuby-devel mailing list
MacRuby-de
On Nov 14, 2011, at 8:15 AM, Jean-Denis MUYS wrote:
> The workflow loop would then become:
>
> 1- test some app action
> 2- notice a bug. Don't quit. Switch to Xcode.
> 3- change the relevant Ruby file
> 4- save
> 5- there is no step 5
>
> I can't see any reason why this would not possible, and
our own version of Siri in MacRuby
> Message-ID:
>
> Content-Type: text/plain; charset="utf-8"
>
> I extracted an old demo I had made for RubyConf which shows how to use the
> voice recognizer feature of OS X to implement an app which could be the
> Siri e
nt discussions."
>>
>> Subject: [MacRuby-devel] Write your own version of Siri in MacRuby
>> Message-ID:
>>
>> Content-Type: text/plain; charset="utf-8"
>>
>> I extracted an old demo I had made for RubyConf which shows how to use the
&g
> >>
> >> Message: 1
> >> Date: Mon, 14 Nov 2011 13:57:10 -0300
> >> From: Matt Aimonetti
> >> To: "MacRuby development discussions."
> >>
> >> Subject: [MacRu
At 5:06 PM -0600 11/14/11, Sophie wrote:
> I am trying to automate OmniGraffle using MacRuby,
> and cannot figure out how to map Applescript to
> available MacRuby methods.
Here are some hints which may be useful...
-r
Many apps are not intrinsically cooperative with AppleScript
(eg, they don't
18 matches
Mail list logo
