I'm looking for some answers on best coding practices, particularly when it comes to object reuse.
In a data-centric application, where the Sitemap is used to navigate through your mapper entities, has anyone given much thought to the object dependencies this can create. In the case of page specific rendering with SiteMap, for example, where should the Menu entries go - in their own object, or should they stay with the MetaMappers. And what about the templates, which can have dependencies on snippets, which reside elsewhere. In other words, it seems to me that good design requires managing the chain of dependencies that an ordinary Menu entry may require. A consistent approach is always best, and I admit that I don't have one at present. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
