Ara As you say, what we need is a clear interface that Hobo expects from its model objects. Then, as this interface would probably differ from the AR interface, we'd need a thin wrapper around AR objects that would satisfy this interface.
We've actually already started this. For example we used to access some_assocaition.proxy_owner all over the place, and now we use some_associatin.origin. But as you've found out, there's all sorts of places where this breaks down. Just one more thing on the to-do list : ) It would be very helpful if you could compile a list of places where (and how) we assume the model object is an AR object. Maybe start a page on the wiki for this? Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
