The idea is to provide some information as to the purpose about the view type for the developer. It's not visible output content. It takes Full HTML. It appears somewhere around the view columns.

You can click and edit it.

Would this be useful? I think if a view is very complex, it would make it easier to understand if one goes away for awhile, comes back and forgets what the view does.

Comments

merlinofchaos’s picture

I agree, this could be useful.

This would go well alongside a 'human readable' name for a View, which is something that Views have never had and have always needed.

Patches will be considered.

dawehner’s picture

So as i think its basically splitted into two parts:
- human readable name for a view
- note/description for every display handler

dawehner’s picture

Status: Active » Needs review
StatusFileSize
new5.31 KB

Here it comes.

dagmar’s picture

Status: Needs review » Needs work

We should allow users define this values when creates a new view.

It is similar to this patch but with changes in the function views_ui_add_form(&$form_state) {}

dawehner’s picture

Status: Needs work » Needs review
StatusFileSize
new6.28 KB

Yes i missed this. Thanks for giving me the function name :)

dagmar’s picture

Status: Needs review » Needs work

The patch doesn't apply anymore. admin.inc have changed a lot since last commit.

I would like to see this Readable name in a more visible place, something like:

Last featured messages: This views displays in fashion way the last ten nodes that have been flagged as featured.

Maybe we can add this legend in top of the view display, just below of Views name. Or maybe popup with a ? icon.

I don't know, but thats is the idea...

dagmar’s picture

merlinofchaos’s picture

Status: Needs work » Needs review
StatusFileSize
new6.23 KB

After converting line endings, this patch now applies again.

(This patch is exactly the same, just has line endings converted).

merlinofchaos’s picture

We aren't allowed to modify views_schema_1() -- see my comments on #635336: Remove unused fields from the view

dawehner’s picture

New version, resolved conflicts in display.inc

merlinofchaos’s picture

Status: Needs review » Needs work

This needs to be updated now that the .install file fixes have been committed. WE do need to make sure that both fresh install and updates work, so just putting it in an update function is not enough.

dawehner’s picture

Status: Needs work » Needs review
StatusFileSize
new5.97 KB

Update

merlinofchaos’s picture

Hm. This has display description as defaultable? Why would that be? The display name isn't, certainly the description should be unique to the display.

dawehner’s picture

Changed the defaultable and changed the update-id to 6009

dawehner’s picture

OH nice patch name. Here is a rerole

dawehner’s picture

Here is a updated version.

I'm wondering whether the tag should still be used as the admin-title, see screeshot. The description/human-readable name is not there.

dawehner’s picture

StatusFileSize
new22.8 KB

Here is the screenshot

merlinofchaos’s picture

Yes, I think these should be broken out into separate line items on the main form.

dawehner’s picture

Here is the new patch.

merlinofchaos’s picture

Version: 6.x-3.x-dev » 7.x-3.x-dev
Status: Needs review » Patch (to be ported)

Doesn't quite apply to D7.

dawehner’s picture

Here is a first patch.

dawehner’s picture

Status: Patch (to be ported) » Fixed

Ported. It's working fine, when you clear the menu cache :)

Commited to the 7.x-3.x branch.

Status: Fixed » Closed (fixed)

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