Hi Paul, Maybe: <dtml-call "REQUEST.set('data', SESSION.getSessionData())"> This essentially makes 'data' a global (and I might be tempted to use a name other than 'data'). is what you're after? -steve On Thursday, August 16, 2001, at 05:54 AM, Paul Zwarts wrote:

Hi all,

Would it at all be possible that one were to fragment dtml code between objects? Say you always use a header and footer, could you not enforce a <dtml-let data="SESSION.getSessionData()"> </dtml-let>between the header and footer? My thought is not as the developer is the only one that knows the header and footer are always executed in a chain. Just thought maybe someone thought of it before and had some kind of product or a suggestion how to enforce the CoreSession presence without rewriting everypage to make the data param.

Thanks, Paz

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )

Hi Paul, --On Donnerstag, 16. August 2001 12:54 +0200 Paul Zwarts <paz@oratrix.com> wrote:

Hi all,

Would it at all be possible that one were to fragment dtml code between objects? Say you always use a header and footer, could you not enforce a <dtml-let data="SESSION.getSessionData()"> </dtml-let>between the header and footer? My thought is not as the developer is the only one that knows the header and footer are always executed in a chain. Just thought maybe someone thought of it before and had some kind of product or a suggestion how to enforce the CoreSession presence without rewriting everypage to make the data param.

This is the domain of ZPatterns I would say. You simply _use_ the values you want in the page and if they are not already loaded, they get loaded (see SkinScript) This is better imho instead of loading everything beforehand what is probably never used. Regards Tino