Expansion options - definative

This seems to be a big issue, so could we gather here?

Here is what we have,

a) Expansion is a popular topic, so it is a high priority.

b) If you choose to unexpand an item in a treemenu, Taxonomy Treemenu doesn't break. However, the result is not at all what people are after. The addressing is odd and the breadcrumbs are wrong here.

c) We've had two calls for node (and even term?) inheritance.

I'd like to point out the dangers of this. Taxonomy Treemenu is one powerhouse of a module. Imagine a treemenu over the whole of Ebay. Some admin decides to click on the menu root, with full node inheritance switched on. Bang, they try to page every node on Ebay. I've worked hard at avoiding this kind of admin disaster, so until I'm convinced we can avoid it, we go in little steps.

d) What you really want is an auto-expanding block menu, no?

I'm figuring, anyway. Like the Navigation menu? What you don't know (well, you do now) is that I have one, maybe two modules half-finished to do some very interesting block things. But I want the base right. Taxonomy Router is looking solid. Now le'ts sort out Taxonomy Treemenu.

My current plan is to push for Version 2 of Taxonomy Treemenu. It will override even a Version 1 release - it's got too many changes to be regarded as a simple progression towards stable release.

I want to leave that expansion option in - it's natural and we should be able to do something with it. If anyone wants to talk me out of it, as an irresponsible maintainer, just post comments.

Please don't expect me to fix expansion as top priority - it's not. But it is high priority.

Rob