On 10/22/07, Martijn Faassen <[EMAIL PROTECTED]> wrote: > In at least 3 places we express dependency information. For different > *purposes* in each case, but we still state something like: > > 1. "we use dependency X, and please download and install it" > 2. "we use dependency X, please configure it" > 3. "we use dependency X, please import the following from it" > > It'd be nice if I only had to say "I want to import from dependency X, > please make sure it's there and available." Actually this is a little > bit like zc.resourcelibrary can make resources appear on your page > headers when you write code that needs it. > > Of course this is sometimes not possible, as there's not enough > information available, or there are multiple separate ways to > configure it.
In the end I guess this all is just more arguments for separating the functions and the views into separate eggs. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )