[development] How could everyone win and get Views in Drupal 8?
cweagans at gmail.com
Wed Aug 12 06:12:58 UTC 2009
I didn't mean to say that it would not be useful. On the contrary, views
would be *useful* in core...I just don't think it would be a good idea to
put it there, especially with plugin manager making it so easily accessible
from the ui.
That said, I would support putting a views api in core and leaving the UI in
contrib, like what is done with cck right now (but only because it's obvious
that lots of people want views in core -- if it's gonna go in, that's the
way I'd wanna see it there)
Owner, Black Storms Studios, LLC
On Wed, Aug 12, 2009 at 12:04 AM, Earl Miles <merlin at logrus.com> wrote:
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development