Still makes sense to add it because Horde::menu() is sometimes called 
outside the application. Make sure you require Horde_Core 1.3.0 if you 
want to use this in Ulaform.

Changes have been made in Git for this ticket:

Add method to set a menu mask.
Request: 10078
Signed-off-by: Jan Schneider <jan@horde.org>

  1 files changed, 10 insertions(+), 0 deletions(-)
http://git.horde.org/horde-git/-/commit/3710e91d1c1f7c819acbf8276ae51f2e0f3880f6

Horde::menu() takes an optional 'mask' parameter that you can use:
Horde::menu(array('mask' => ..))

Ping?

Now that Ulaform is commited you can see how I used it here:

http://git.horde.org/co.php/ulaform/lib/Application.php?rt=horde-git&ws=1&r=836db350ef8cea4900a0b29a15ebe63b8431bb1e

I did not found any other way how to set masking cleanly. The only 
solution would be to construct the menu in every controller script 
like here:

http://git.horde.org/diff.php/passwd/templates/main/main.inc?rt=horde-git&ws=1&r1=caa9c90cec2ac47b89d089316818071295786424

Given that Ulaform has more menu buttons and you must include things 
like sidebar, etc. in every script this looked not right. But maybe 
it's just me?

At least in almost all released applications menu various menu 
parameters are set in -*_Application::menu() and then called with 
simple Horde::menu() in controller scripts. So I thought that setting 
a mask there should be cleaner.

No, menus are generated with Horde::menu() which takes the mask too. 
*_Application::menu() is for generating application menus from 
*outside* of the application, e.g. preference screens.

Maybe it's just me, but I did not found a way to pass a mask in 
application's Application.php menu() method. I'm assuming this is a 
standard way to create a menu now, right?

For which purpose? You can already set the mask in the constructor.

Patch adds method to set a menu mask.