I like your idea of a streamlined Calendar interface. But without the color key, how will users differentiate the various types of events, except by memorizing the colors? The color key is necessary, but it certainly doesn't need to take up 1/3 of the block.
Getting back to your suggestion, removing the bottom portion of the Calendar block would also remove the hide/show controls. I don't see this as a problem because the hide/show controls also appear on the Detailed month view page.
You say that by removing the bottom portion of the Calendar block, users would lose the ability to create user events. Why? The events that a user can create are determined by the contents of the pull-down menu on the Detailed month view page.
Getting back to hide/show, I don't understand the rationale for this feature as it is currently implemented. Specifically, I don't understood why Calendar gives every user the ability to hide any type of event. For example, it lets students hide course events. I can't think of a single use case for this (unless it is to give students an excuse for not knowing that a course event was scheduled
Shouldn't the ability to hide/show events be capability-based? Then the default roles could be defined such that
- every user can hide/show his own user events
- teachers can hide/show course and group events
- admins can hide/show global events.
Calendar certainly has an idiosyncratic interface, that has always puzzled me. It is easy to imagine a more Moodle-like interface, i.e., one with an Editing calendar page launched by an Edit icon.