cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathaniel Alfred" <Alfred.Nathan...@swx.com>
Subject RE: [RFE] Some enhancements to XSP
Date Tue, 24 May 2005 20:40:32 GMT
>-----Original Message-----
>From: Jochen Kuhnle [mailto:lists@kuhnle.net]
>Sent: Dienstag, 24. Mai 2005 13:45
>To: dev@cocoon.apache.org
>Subject: [RFE] Some enhancements to XSP
>
>
>Hi, I know XSPs are supposed to go away, but I still like 'em... I would 
>like to propose some enhancements, and if they're accepted also volunteer 
>to implement them (including documentation and examples :).
>
>1. A logicsheet for cache key control to have an easy way to override 
>"getKey". Something like:
>
><key>
>        <value><xsp:request-param name="userId"/></value>
>        <value><xsp:request-param name="companyId"/></value>
></key>
>
>2. A logicsheet to do the same for "getValidity", so you can do:
>
><validity>
>        <file src="/etc/configfile"/>
>        <expires seconds="3600"/>
></validity>
>
>Tags would be available for all classes in the distribution 
>that extend SourceValidity.

We are also heavy XSP users but up to now I never came around to try
caching.  Do just want to generate the getKey/Validity methods or did
you forsee to have some sort of chaining/overriding mechanism?

>3. A mechanism for expression replacement as in XSLT or JXTG, replacing 
>"{expression}" with a xsp:attribute element in attributes and with a 
>xsp:expr element in character data. This could be implemented in the 
>PreProcessFilter of XSPMarkupLanguage. The feature would be disabled by 
>default and enabled on a per-XSP-basis, maybe through a processing 
>instruction.
>
>Example:
>
><!-- Hey, this looks almost like JXTG :) -->
><img src="{source}" width="{width}" height="{height}"/>
><h1>Hello {username}</h1>
>
>is more readable and easier to use than
>
><img>
>        <xsp:attribute 
>name="src"><xsp:expr>source</xsp:expr></xsp:attribute>
>        <xsp:attribute 
>name="width"><xsp:expr>width</xsp:expr></xsp:attribute>
>        <xsp:attribute 
>name="height"><xsp:expr>height</xsp:expr></xsp:attribute>
></img>
><h1>Hello <xsp:expr>username</xsp:expr></h1>
>
>Any comments? (I hope this hasn't been proposed already, but I 
>didn't find anything about it)

Don't think in-text replacement is a good idea.  The preprocess would
need too much knowledge about xsp markup in order not to try expanding
curlies inside xsp:logic, xsp:expr etc.

Also for the src="{source}" shortcut I am sceptic.  It breaks when
you want to move your <img> content markup from XSP to logicsheet.

But I agree that the xsp:attribute markup is too verbose.  I'd rather
wish for the XSLT analogy:

  <xsp:attribute name="src" value="source"/>

>Regards,
>Jochen

Looking forward to hear more from you.
Cheers, Alfred.
 
 
This message is for the named person's use only. It may contain confidential, proprietary
or legally privileged information. No confidentiality or privilege is waived or lost by any
mistransmission. If you receive this message in error, please notify the sender urgently and
then immediately delete the message and any copies of it from your system. Please also immediately
destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail communications through their
networks. Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorised to state them to be the views of
the sender's company.

Mime
View raw message