On Dec 12, 6:32 am, "Martin Gamsjaeger" <[email protected]> wrote:
> However, I would like to be able to use standard CSS3 id-selectors > inside my specs no matter if I decide to organize my models within > modules. I somehow think that the way I organize my ruby classes with > modules should have no influence on the CSS3 selectors I can use > inside my specs. > > Opinions? Can you explain to me the benefits of namespacing your models? I have been trying to figure it out for a long time now, and I can't see why you would need it. If a model is just a representation of a database table, it needs a unique name anyway. Unless merb treats a namespaced model as a separate repository (which it doesn't, but would be pretty cool), or namespacing serves some purpose for an ORM that I have never used, I really don't understand what benefits namespacing brings you. However, merb-gen generates a module around your model if you tell it you want it namespaced, so this must have at least been the desired behavior at some time. In which case your point is valid and the namespacing that you use in your models should be respected throughout your app. I just really want some clarification on this. > cheers > snusnu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
