[Nitro] [ANN] Nitro/Og 0.31.0

[gabriele renzi]

Daniel DeLorme ha scritto:

That's a cute example, but it leaves me with one big question:
how the hell does Og know that Content maps to the database and
that Demo does not?

because Demo does not use model objects' methods, such as the enhanced
attr_* or belongs_to.
You have the chance to fine tune this, anyway, in case that Og is not
smart enough to find the classes correctly (it usually works fine, anyway)

 

[Benjohn Barnes]

Benjohn Barnes ha scritto:


That's somthing you can find in facets, the method Kernel#autoreload
http://facets.rubyforge.org/api/core/classes/Kernel.html#M000450

! That's very cool. *cough* I've not actually used facets at all.

Okay, I've had a look, and it looks very full of interesting stuff.
Is there some kind of map / table of contents for the collection?
Some kind of rough break down in to areas of functionality?

 

[George Moschovitis]

That's a cute example, but it leaves me with one big question:

how the hell does Og know that Content maps to the database and
that Demo does not?

Og manages classes that define serializable attributes. A serializable
attribute is an attribute with a class annotation. This works great
for 95% of the cases. For the rest, you can use Og features like the
following to customize the behaviour, including:

class XXX
is Unmanageabke
end

or

class XXX
attr_accessor :test, String, :serializable => false
end

etc, etc.

regards,
George.