Hi Joshua, It's always a good idea to name your resources and/or resource directories by your package, e.g. ++resource++my.package1 and ++resource++my.package2.
But if you want to have the same resource names for different parts of your application you might want to use different browser layers. So you can register one general resource 'static' and then register another one with the same name within your second package for a custom browser layer. This browser layer will then be registered for or injected at special locations within your application. HTH Thomas Sent from my iPhone On May 27, 2011, at 3:28 PM, Joshua Immanuel <[email protected]> wrote: > Hello, > > On Fri, 2011-05-27 at 14:35 +0200, Thierry Florac wrote: >> The main problem is just that resourceDirectory directives mainly >> defines resources which are accessed directly by an HTTP request and >> not by a page template. So there would be no way to make a distinction >> between these two directories if they have the same name. > > Thanks for the reply. So, I guess the resource name should be unique > across the entire application in order to isolate sub package specific > static contents? IMHO, this would be a problem if the application is > huge. Is there any other better way to do this? Are am I missing > something as trivial? > > Regards > -- > Joshua Immanuel > HiPro IT Solutions Private Limited > http://hipro.co.in > _______________________________________________ > bluebream mailing list > [email protected] > https://mail.zope.org/mailman/listinfo/bluebream _______________________________________________ bluebream mailing list [email protected] https://mail.zope.org/mailman/listinfo/bluebream
