> > BTW, just to make it clear: despite its name, OOOR doesn't depend on Rails, > it just works well with Rails and mimics its API. We currently override a few > methods from the ActiveResource gem which is a very small Rails component, > but I'm not sure we will always do that, especially when we will start > implementing the Rails 3 ActiveModel interface (the contract of the Rails 3 > ORM if you like). So in any case it's more about enforcing a standard API > rather than a dependency. Of course, that would be plain stupid to make OOOP > depend on Django either ;-)
Nice to read this. :-) I created a group in google just now. The address is http://groups.google.es/group/openerp-ooop?hl=es Everyone is welcome. P.D.: last version of OOOP has a big improvement to retrieve initial information using all() and search() in models. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=59074#59074 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
