This is a series of UI's showing lists of views - both user created and code based views.

The idea here is that most users will not think about code-based views versus user-created views. They think, pre-created views versus user created views. Pre-created is obviously a bad choice of terms. Really what we're talking about is an object that comes pre-populated - which in common language is a template. The other major point here is that it's presently strange to arrive at the list of Views for the first time and see a bunch of items. It's also intimidating since there's a lot to look at, all of which is not common language. New users out thinking... what is this feature called Views, why are all of these things here (i didn't create them), and what do these things do / why are they relevant to me? All of which can be mitigated by pushing code based views off to another page.

Comments

Noyz’s picture

Ugh, It's so frustrating how the image url underneath the attachment doesn't actually work if you're trying to do a preview. If someone has more rights than me, can you append "/issues" after "/files"

dawehner’s picture

"storage" => In database/in code ?

Technical: Are "template views" "default views" with disabled => TRUE?

Noyz’s picture

yes.

pwolanin’s picture

I still don't think the "template" terminology is correct, since one will still be able to revert a modified View to it's code representation? I'd consider a template a basis for making a working copy, not something that can be enabled and reverted.

Why not simply make the action link "Browse disabled Views"?

cbrookins’s picture

Subscribe

cbrookins’s picture

Subscribe

Noyz’s picture

"browse disabled views" could work. But many people will miss the advantage if we're to use that language. Said another way, "template" is a loaded word that means "give me this thing that's prebuilt so that I don't have to build it myself." That in and of itself is a really big win. Browse disabled views just doesn't have that kind of hook.

helior’s picture

"Browse views examples" with a link to "clone"?

LarsKramer’s picture

I agree that templates should be used as a basis for making modificactions. I think presently you need to duplicate the default view and make the modications there which is not very intuitive. If not, won't you loose the modifications when the module is updated to a newer version?

Regarding the interface of the list of views, I think it would be cool to have the possiblity as a user to customize it to your personal preference, ie. decide which columns to show, default sort order, default filters etc.

Another nice detail would be to have it integrated with http://drupal.org/project/views_hacks#views_filters_autosubmit so you don't ned to hit the 'filter' button after making a change.

bojanz’s picture

The new Ui has been committed to 7.x-3.x.
Mission accomplished.

bojanz’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.