Received: by 10.52.88.174 with SMTP id bh14mr350776vdb.6.1340849655232;
        Wed, 27 Jun 2012 19:14:15 -0700 (PDT)
X-BeenThere: rubymotion@googlegroups.com
Received: by 10.52.66.242 with SMTP id i18ls1266238vdt.5.gmail; Wed, 27 Jun
 2012 19:14:14 -0700 (PDT)
Received: by 10.52.173.49 with SMTP id bh17mr14263vdc.2.1340849653980;
        Wed, 27 Jun 2012 19:14:13 -0700 (PDT)
Date: Wed, 27 Jun 2012 19:14:13 -0700 (PDT)
From: Jim Nanney <jnan...@gmail.com>
To: rubymotion@googlegroups.com
Message-Id: <1e8f7d46-61fd-484c-9f35-8f52b9ea929a@googlegroups.com>
In-Reply-To: <9e9eba3a-6171-4f22-81af-dcd44c212aa1@googlegroups.com>
References: <d81a59b5-262e-4f01-aed8-c357b8dc6170@googlegroups.com> <647b343e-d837-48f4-8974-b9c378dc7a30@googlegroups.com> <7E2E985A-06B3-4584-9191-02F74D318F64@gmail.com> <00da7a5d-bd93-469e-a564-4c254fe9a7ef@googlegroups.com> <7f32c079-da78-4645-bae7-dacebc34c6cd@googlegroups.com> <fc5c2a91-8895-46a4-9dab-f1d8aa222d8d@googlegroups.com> <f587007c-7e08-4de2-bac9-a8f63ca247ab@googlegroups.com>
 <F18A4A89-07C0-44FF-AA84-0AAE65B5A066@gmail.com>
 <9e9eba3a-6171-4f22-81af-dcd44c212aa1@googlegroups.com>
Subject: Re: [RubyMotion] CoreData relationships sample
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2023_21221220.1340849653472"

------=_Part_2023_21221220.1340849653472
Content-Type: multipart/alternative; 
	boundary="----=_Part_2024_14996694.1340849653472"

------=_Part_2024_14996694.1340849653472
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Fantastic! Other than not wanting to deal with Xcode, there is no good 
reason I can come up with.  But it feels great to use textmate, ruby motion 
and the simulator only. 

On Wednesday, June 27, 2012 8:36:18 AM UTC-5, Matt Green wrote:
>
> No.
>
> I've begun work on an XCode-less version of CoreData support that 
> generates .xcdatamodeld files via rake tasks. This creates a nice workflow 
> that is very similar to that of Rails:
>
> 1. Write models, put them in app/models
> 2. rake dm:migrate # scans models, generates xcdatamodeld, and compares to 
> existing one. If new, saves new version and activates it
> 3. rake
>
> Check it out at https://github.com/mattgreen/nitron/tree/0.3
>
> Is this what you're looking for?
>
> On Friday, June 22, 2012 7:16:01 PM UTC-4, Steve Ross wrote:
>>
>> I can understand some loathing for Xcode or a sense of dirtiness messing 
>> around with magic glue, but is there a technical aspect to the Nitron 
>> approach that will handicap migrations or otherwise inject noise/overhead 
>> into the app?
>>
>> Thanks
>>
>> On Jun 22, 2012, at 10:25 AM, Matt Green wrote:
>>
>> I feel the same way. 
>>
>> We're working toward text-based workflows while providing something that 
>> works in the interim. I'm keen on supporting iCloud and CoreData, and that 
>> requires lightweight migrations.
>>
>> On Friday, June 22, 2012 9:51:55 AM UTC-4, Jim Nanney wrote:
>>>
>>> Nitron is neat, but if I can help it,  I never want to open Xcode again.
>>>
>>> On Wednesday, June 20, 2012 9:44:15 PM UTC-5, Mac Fanatic wrote:
>>>>
>>>> Link - https://github.com/macfanatic/nitron
>>>
>>>
>> -- 
>>
>>
>>
------=_Part_2024_14996694.1340849653472
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Fantastic! Other than not wanting to deal with Xcode, there is no good reas=
on I can come up with. &nbsp;But it feels great to use textmate, ruby motio=
n and the simulator only.&nbsp;<br><br>On Wednesday, June 27, 2012 8:36:18 =
AM UTC-5, Matt Green wrote:<blockquote class=3D"gmail_quote" style=3D"margi=
n: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">No.=
<div><br></div><div>I've begun work on an XCode-less version of CoreData su=
pport that generates .xcdatamodeld files via rake tasks. This creates a nic=
e workflow that is very similar to that of Rails:</div><div><br></div><div>=
1. Write models, put them in app/models</div><div>2.&nbsp;rake dm:migrate #=
 scans models, generates xcdatamodeld, and compares to existing one. If new=
, saves new version and activates it</div><div>3. rake</div><div><br></div>=
<div>Check it out at <a href=3D"https://github.com/mattgreen/nitron/tree/0.=
3" target=3D"_blank">https://github.com/mattgreen/<wbr>nitron/tree/0.3</a><=
br></div><div><br></div><div>Is this what you're looking for?</div><div><br=
>On Friday, June 22, 2012 7:16:01 PM UTC-4, Steve Ross wrote:<blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>I can un=
derstand some loathing for Xcode or a sense of dirtiness messing around wit=
h magic glue, but is there a technical aspect to the Nitron approach that w=
ill handicap migrations or otherwise inject noise/overhead into the app?</d=
iv><div><br></div><div>Thanks</div><br><div><div>On Jun 22, 2012, at 10:25 =
AM, Matt Green wrote:</div><br><blockquote type=3D"cite">I feel the same wa=
y.&nbsp;<div><br></div><div>We're working toward text-based workflows while=
 providing something that works in the interim. I'm keen on supporting iClo=
ud and CoreData, and that requires lightweight migrations.<br><br>On Friday=
, June 22, 2012 9:51:55 AM UTC-4, Jim Nanney wrote:<blockquote class=3D"gma=
il_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">Nitron is neat, but if I can help it, &nbsp;I never want to=
 open Xcode again.<br><br>On Wednesday, June 20, 2012 9:44:15 PM UTC-5, Mac=
 Fanatic wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-l=
eft:0.8ex;border-left:1px #ccc solid;padding-left:1ex">Link - <a href=3D"ht=
tps://github.com/macfanatic/nitron" target=3D"_blank">https://github.com/ma=
cfanatic/<wbr>nitron</a></blockquote></blockquote></div><div><br></div>

-- <br>


</blockquote></div><br></div></blockquote></div></blockquote>
------=_Part_2024_14996694.1340849653472--

------=_Part_2023_21221220.1340849653472--