Re: [Rubycocoa-talk] Core Data or not Core Data

[Jon B. <jo...@gm...>]

Also keep in mind:

CoreData is < sqlite3
AR you would need to supply native driver + > sqlite3

I personally think AR is alot less code (including validation  
techniques) + I like the auto alert generation for bad validation.   
Also migrations is a real key that you would not be able to do (I  
don't think) w/ model builder in Xcode.  Would be nice if you could  
take model file + auto build AR objects :-)

I have a few apps installed which use CoreData + run simple AR w/ the  
db and find it pleasing to be able to query Yojimbo from irb directly.

I think more and more apps will eventually do this (bypass .Mac) and  
w/ AR you can basically create "mashups" of your own applications.

http://www.webjimbo.com is a good example.  What I don't get is if  
RubyCocoa will be installed w/ 10.5 will this work also be included?   
Or is it kinda late?

- Jon

On Jun 19, 2007, at 12:50 PM, Eloy Duran wrote:

> Hey Tim,
> I'm glad you liked the screencast :)
> To clarify a few points:
> - CoreData is without a doubt (and without me even knowing this for  
> sure)
> way more mature and more integrated into cocoa. Document based apps  
> would be
> a good example of this, maybe it's not that hard to use it with a  
> document
> based app??
> - that being said, I know there are a lot of rubyists working on  
> macs that
> already know AR and might want to do a simple app so the  
> possibility of
> using AR is a nice feature to have.
> - AR supports way more db's, also networked. Again this might also  
> be the
> case with CoreData, but I don't know :)
> - eventually ARes support, which I think will be the biggest reason  
> for
> rails people to start creating (small) OSX apps, which of course is  
> a good
> thing... I mean more mac apps woohoo!
> - and there are also a whole lot of plugins readily available for AR
>
> So I guess like with any situation, you need to carefully decide  
> what it is
> you need.
> If you everything you need is in CoreData, and maybe you already know
> CoreData,
> then it might be best to just stick with that.
>
>
> Cheers,
> Eloy
>
> On 6/19/07, Tim Perrett <he...@ti...> wrote:
>>
>> Ok thats interesting.
>>
>> Would it be at all possible to send me the code for frictionless, as
>> I am not quite sure what you mean when you refer to "I found that I
>> had to write my accessors in ObjC for speed because crossing the
>> bridge to do "willAccessValueForKey" then pulling the value, then
>> calling "didAccessValueForKey" was too many bridge crossings."
>>
>> So the bottom line is that the same things can be achieved with both
>> AR and CoreData, its just that CoreData is an apple supplied more
>> mature way of doing things? Its just 'less ruby'?
>>
>> Cheers
>>
>> Tim
>>
>> --------------------------------------------------------------------- 
>> ----
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Rubycocoa-talk mailing list
>> Rub...@li...
>> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/ 
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk