Oops, thanks for the fix :)
On 28 jun 2011, at 18:21, Robert Lowe wrote:
> Value must be a pointer when passed
>
> value_to_pointer = Pointer.new(:object)
> value_to_pointer.assign(value)
>
> Regards,
> - Rob
>
> On 2011-06-28, at 12:08 PM, Eloy Duran wrote:
>
>> I have no experience with Co
Value must be a pointer when passed
value_to_pointer = Pointer.new(:object)
value_to_pointer.assign(value)
Regards,
- Rob
On 2011-06-28, at 12:08 PM, Eloy Duran wrote:
I have no experience with Core Data, but if you are looking to make
repetitive work easy then don't forget about the metapr
That’s untested code btw.
On Tue, Jun 28, 2011 at 6:08 PM, Eloy Duran wrote:
> I have no experience with Core Data, but if you are looking to make
> repetitive work easy then don't forget about the metaprogramming
> possibilities with Ruby. Taking your example, you could create class
> method lik
I have no experience with Core Data, but if you are looking to make
repetitive work easy then don't forget about the metaprogramming
possibilities with Ruby. Taking your example, you could create class
method like the following:
class Model
def self.core_data_accessor(name)
class_eval(%{
On 2011-06-28, at 11:55 AM, Shannon Love wrote:
> I'm not to the point of wiring up the UI yet. I will employ bindings when I
> do so but at the moment I am creating a complex data model using
> NSManagedObject subclasses with lots of customized behaviors. I do this all
> the time in Objective-
I'm not to the point of wiring up the UI yet. I will employ bindings when I do
so but at the moment I am creating a complex data model using NSManagedObject
subclasses with lots of customized behaviors. I do this all the time in
Objective-c but I am uncertain how to go about doing so in MacRuby.
