Nice! this will work for me. Thanks Vitaliy.
On Tue, Sep 2, 2008 at 1:43 PM, Vitaliy Podoba <[EMAIL PROTECTED]> wrote:
> David Bain <[EMAIL PROTECTED]> writes:
>
>>
>> All the examples I've seen of using templates as some kind of resource look
> like this: <plone:portletRenderer
> portlet="plone.portlet.collection.collection.ICollectionPortlet"
>> template="templates/collection.pt"
> layer=".interfaces.IThemeSpecific" />suppose I had a product
> called
> "mystuff.customtemplates" which
> contained:mystuff/customtemplates/browser/templates/myversionofcollection.pthow
> would I refer to that template from another product?I'm just not sure
>> <plone:portletRenderer
> portlet="plone.portlet.collection.collection.ICollectionPortlet"
> template="{magic incantation to call
> mystuff.customtemplates/browser}/templates/myversionofcollection.pt"
>> layer=".interfaces.IThemeSpecific" />I'm not sure
>> what
> should replace the "{ }" placeholder above.
>>
>
> Hi, David
>
> You can use nested 'configure' directive in your zcml file to register portlet
> renderer in context of another package, e.g.:
>
> <configure package="mystuff.customtemplates">
> <plone:portletRenderer
> portlet="plone.portlet.collection.collection.ICollectionPortlet"
> template="browser/templates/myversionofcollection.pt"
> layer=".interfaces.IThemeSpecific"
> />
> </configure>
>
> Thus, in this example all relative paths will be calculated in context of
> mystuff.customtemplates package. So perhaps you will have to write a full
> (absolute) dotted path to your layer interface in order to register renderer
> on
> interface that is outside mystuff.customtemplates package.
>
> Good luck,
> Vitaliy Podoba
>
>
>
> _______________________________________________
> Product-Developers mailing list
> [email protected]
> http://lists.plone.org/mailman/listinfo/product-developers
>
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
