On Friday, September 16, 2005 5:30 PM, Benji York wrote:

> Garrett Smith wrote:
>> On Friday, September 16, 2005 5:17 PM, Benji York wrote:
>>> Garret Smith wrote:
>>>> FWIW, we would not be able to use this new scheme exclusively as
>>>> some of our IHeadContent providers provide more than file
>>>> includes. E.g. we have a menu component that dynamically builds
>>>> JavaScript and includes it directly in the HEAD.
>>> That is a different, but related, problem that should probably be
>>> addressed separately.
>> How is this different?
> Resource library is about including references to (static,
> file system
> based) resources on an as-needed basis.  The use case you
> mentioned is
> about including dynamically generated JS each time a view is rendered.

I thought the use case was rich widgets. If the use case is the proposed 
solution, then the proposal is spot on ;-)

But enough of my whining :-) Let's just make sure this new thing doesn't impact 
publishing performance. Preferably this would be implemented as pluggable 
component and be optional.

 -- Garrett

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to