Usage of generic.xsp for menu creation

[Christian Egli <ch...@wyona.com>]

Hi all 

In order to solve a problem with the removal of language versions I
would like to grey out the menu item "Remove language version" if the
document is only available in one language. This is can be achieved
relatively easy in config/menus/generic.xsp. 

However AFAIK it is not recommended to do this in generic.xsp possibly
for performance reasons. What are the alternatives? Don't tell me to
use a transformer (which I could do), since this doesn't solve the
performance problems.

-- 
Christian Egli       christian.egli@wyona.com   +41 1 272 9161
                     Wyona AG, Hardstrasse 219, CH-8005 Zurich
Open Source CMS      http://www.wyona.org http://www.wyona.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org

Re: Usage of generic.xsp for menu creation

[Andreas Hartmann <an...@apache.org>]

Christian Egli wrote:
> Hi all 
> 
> In order to solve a problem with the removal of language versions I
> would like to grey out the menu item "Remove language version" if the
> document is only available in one language. This is can be achieved
> relatively easy in config/menus/generic.xsp. 
> 
> However AFAIK it is not recommended to do this in generic.xsp possibly
> for performance reasons.

Why that? I would recommend to do such things (if they're publication
specific) in generic.xsp, it's easy and as fast as Java code can be.
The drawbacks are:

- the "contamination" of the menu definition with logic, but
   I'm afraid we can't avoid that

- it can't hard to reuse in other publications

Andreas



---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org