<snusnu>
the integration specs in both projects should give you a nice overview of the API
<snusnu>
and they're only 2 files ;)
<snusnu>
ramom's focus is to expose a set of external and internal, context aware relations that are completely composable
<snusnu>
external ones being accessible to clients (i.e. public methods client code can call), internal ones being used only for composing other relations (private methods)
<snusnu>
an app built with it (ours) typically defines *all* relations upfront, and in action code (read views for now) a reader is obtained for any of the external relations, which exposes only #one or #read (to extract one tuple, or to iterate over a relation)
<snusnu>
the motivation and design hugely stems from "relations as first class citizens" and the "out of the tarpit" paper
<snusnu>
anyways, i'd be curious to hear your thoughts about it, should you (or anyone else) find the time to look through the code
<snusnu>
eventually, i'll add a readme of course ...
<snusnu>
one more thing's worth mentioning: ramom can integrate smoothly with an app that uses DM1 (for migrations, plugins, and write ops)
<snusnu>
all base relations, keys and foreign keys can be inferred from DataMapper::Model.descendants
snusnu1 has joined #rom-rb
snusnu has quit [Ping timeout: 276 seconds]
snusnu1 has quit [Client Quit]
snusnu has joined #rom-rb
<dkubb>
cool, I'll check it out
snusnu1 has joined #rom-rb
<dkubb>
snusnu1: did you build an app with this?
<dkubb>
heh, when I read mom I thought it said "Martin's Object Mapper"