Besides, it sounds like you want to expose this UI Level editor to end users. That I would never allow. This should be configurable *only* by the server admin, and never by site admins.

I agree that there are probably better ways to spend your time. I don't really want it to be accessible to end users. Currently, I don't know where I can view a list of what gets enabled as the UI Level increases. Is there a single place where this is configured or is it implemented throughout the codebase?

William

----
Knowmad Technologies
http://www.knowmad.com

This is seems very elegant. Now it's not impossible to add tabs to the admin bar, I've done that before. I've never tried to add or remove things (for every group) to the admin console, but I would guess that is not possible now.

From the examples, I understand it makes assets pluggable, but shouldn't be defined somehow what is an asset and what is an operation and perhaps what is a URL handler for example? Or is this deduced from the object that is named and can a url be used instead of an object?

I'm very happy the current functionality on a per-asset level is preserved. I suppose you can still define a higher user level e.g. 10 than can be assigned to a user to hide the functionality altogether for every user?

How are labels and categories internationalised in the config?

I have difficulty to see if and how this influences the ability to hide a standard-asset from the admin tab and show several prototypes that are dirived from it.

Kind regards,

Arjan Widlak

United Knowledge
Internet for the public sector

www.unitedknowledge.nl