Improve sections "admin" interface.

http://drupal.org/node/51969: Based on aliases, or alias patterns.

Let's make an update on this issue and discuss what will be implemented next, please.

* Taxonomy sections (a section per taxo) http://drupal.org/node/12981
http://drupal.org/project/taxonomy_theme already implements this. Should we integrate this, too? I saw you said you don't like this until blocks have this... i don't know why we should wait for something that possibly never get's implemented in core!? Aside this module have many features sections implements. Only thing currently not working in taxonomy_theme are the wildcard's - "sections" stands for.

* Role based sections (a section based on user roles)
Should be easy to implement, but i currently don't know who will use it and why!? I'm asking myself why someone should change a layout, let's say from 2 columns to 3 columns only if a specific role is active!? If i think about block visibility (for e.g. "who is online") this could already be done in the blocks configuration.

* User based sections (based on user patterns)
What type of patterns? If a user name starts with "A*" we switch from 2 column to 3 column?

* Node-type based sections
This is a good idea and should be easy to implement. I'd like to use this, too. This setting should have a higher default priority then the rule/path based theme.

Additional i'd like to extends this list with:
* Node-specific sections to allow a theme per node. This setting should have the highest default priority over all. If such a node will be added to a section "examples*" (theme "example_standard") i must be able to change the node theme for "example/test1" to theme "example_standard_test1".

* Role based sections (a section based on user roles) is a new feature from 6.x-1.1+

* Node-specific sections to allow a theme per node is a new feature from 6.x-1.3+