Document FAQ about using views vs displays

Displays should be grouped together if they are fundamentally similar and are sharing lots of data. Grouping displays together that are mostly overrides is not efficient; it is both difficult to maintain and does add an extra burden to the system. Displays must be processed even if they aren't run. Having a couple of extra displays on a view is not a significant extra burden. Having twenty would be.

Changing this to a documentation task, as this question is asked often and clearly we need to document this better so more people understand.

Add tag

Added performance page and performance-views-vs-displays in Views' advanced help folder.

Looks fine

I have stalled on committed this because it feels to me like we're not really offering much in these pages. I think they're helpful but it feels like if we offer this we should go another step and offer a little bit more?

When I install this patch, it's trying to add information to the top of views.help.ini, which is breaking advanced help.

Page not found
warning: Error parsing ./sites/all/modules/views/help/views.help.ini on line 2 in C:\web\www\views3xtest\sites\all\modules\advanced_help\advanced_help.module on line 667.

Reassinging to myself to try on my new test environment, which should behave better.

Ok, the patch does work. It could likely use more fleshing out, but I think it's probably just as well to have *something* there instead of nothing :)

committed to 6.x-3.x