Cameron Eagans wrote:
I think the argument of 'let's put views in core because it'll make
setting up sites easier' is kind of a bad one in this case. Views is
neither easy nor essential for -every- site out there.
The argument for having Views in core is that Views would then power a
whole ton of core:
tracker.module: Just a view.
blog.module: Just a view.
/node front page: Just a view.
/rss.xml: Just a view.
node content admin: Could be a view, with VBO.
user admin: Could be a view, with VBO.
recent comments block: Yep, a view.
recent blog posts block: Yep, a view.
active forum posts? Sho 'nuff.
Having a bunch of this stuff be Views natively, instead of hardcoded
queries and whatnot, would be a big step closer to separating the API
from the Application, and the Application would become *much* more
replaceable. And tweakable. Because once it's a view, then on your site
you can tweak it as much as you can tweak any view. And that's rather a lot.
