This is an interesting thread, and from my perspective being a designer of skins and containers (Did I ever mention how much I don't like containers???)  I put in all the actions in all my commercial work, UNLESS a client has asked me not to, but normally not the minimise/maximise options.

However, from a design perspective, sometimes they tend to required more time thinking about the layout, since often decorative elements get broken when you add these extra functions and you have to decided - where do you put it - because even if hidden, to get them looking right you need to put into a table, or you can use a div tag, but it often leaves an annoying space between the bottom of the container to the top of the next one, where sometimes you want to control it for the look overall.

Having said that - I think if worst comes to worst and you're going to break the design up - you could perhaps just create another set of containers and drop the functions into it down the bottom, the tags up the top and allow the end user to choose a *print* version of that container.  That's the only way I can think of working out a happy solution if the design is affected.

From a designer perspective.. I REALLY DISLIKE the print icon being set as default - I think minimise and print should NOT be default - so those who are using DotNetNuke can purposely turn it on.. I think it would change the mind of designers creating containers, since you find people who know very little just use the standard settings, and who wants an image or links to be printable - or EVERYTHING to have the print icon when it's easier to NOT have them. And by putting none of these actions into the container, you keep the integrity of the site in place.

Also, when it comes to RSS and such - not everything is rssable, so then what happens, people ask - why do some things have RSS and other don't, and then I would get asked, how to I turn off print - we don't want it.. and for beginners, they tend to get confused when you tell them...This is because they can change the settings in a single module to be default for everything else, eg: Turn of specific module functionality from one module and set to default in every other module, but that's only good if you catch them at the beginning of the design otherwise they have to go into many pages and make small changes to fix up what is overriding the default.

So, I suppose a really simple fix would be to by deafult have these elements turned OFF, and you tell people how to turn them on if they want them. And for container creators, duplicating the container set and simply adding the functions down the bottom would keep the container style intact.. and everyone would be happy.

That's my take on the matter.. since I really don't like containers anyway- and much of it is to do with the disruption in design that I feel it creates for the end user who feels they have to go in and turn everything off because by default it's always on.  But on the flip side - containers can make information display nicely as well when used in moderation.

Nina Meiers