I've been spending LOTS of time with Views trying to arrive a solution that addresses the following concerns:
- Help orient new users: Beginning users don't know what a View does, yet we start them off asking them to select a type and show them an empty default query - to which they are supposed to know what to do. Presently new modules are being cast to fix this problem rather than fixing the problem in the main module
- Reduce scrolling: Currently users click to add a field, scroll to fill out the field, scroll to see the preview, scroll to either edit or add more fields
- Utilize progress disclosure: Many users only use a subset of the features in views, yet have to absorb and learn about features they'll never use. Others use all of the features. The UI should be optimized for the 80%, but be capable of optimizing for the additional 20% if they chose to work that way
These designs are the first part of a series focusing on item 1 above. The design allows people to configure a View via a "Simple Views" like solution - negating the need to have both Views and Simple Views installed. The design allows users to choose to show blog posts, article posts, or elements from a different table, i.e., comments, users, etc., and all fields update accordingly. That is, if I choose to show blog posts, I can filter the view by taxonomy terms and reveal the posts as teasers, versus if I choose to show comments I can not sort by taxonomy terms and can only reveal the full comment or comment fields.