I probably shouldn't be adding to the massive amount of issues, but I don't want to forget this. This will also help the maintainer plan accordingly.

For starters, Views is a great module, and has been accepted by the Drupal community as if it was part of core. After all, it is the most used module available.

Browsing the issue queue, I've seen many scenarios where Views will come in really handy. Rather than having one standard list of Scoops, why not allow Views to manage the displaying. This way, it can be customized by the site developers.

It will help with changing:

VotingAPI already supports Views, so it shouldn't be very difficult to have Drigg use it to display scoops.

Comments

philbar’s picture

philbar commented

It should make this issue possible: #339262: User configurable category filter for Drigg

mercmobily’s picture

mercmobily commented
Status: Active » Closed (won't fix)

Hi Philbar,

The short story is that you basically can't do this with views.
I've done this before, but I will do it again.
Here are a few unsolvable issues -- but I am sure it's not even comprehensive:

* Smart links Right now, if you noticed, if you click on a Category -- say "Motorbike" -- you will see the published stories in the "Motorbike" section. Then you click on "Upcoming" -- and you will stay in the "Motorbike" section, but you wil see the upcoming stories in that section. That you can change the order -- say "Most popular" -- and there you go, The Most Popular Upcoming stories in the Motorbike section. Then you click on Cars, and -- this is fancy -- you get the Most Popular Upcoming stories in the Motorbike section. This is done through a very complex mechanism that analises the URL and recognises what you're looking at. It's very complex code, that I kept as readable as possible and is yet really quite tricky. This is _essential_ in a drigg site, and there is _no_ way to do this if you use proper Drupal menus rather than Categories (which is why I had to basically reinvent the menus, which was painful) and Views.

* There are others, but I frankly can't remember. The one above was the big one, and it's really quite important

Of course, I might be wrong. But I doubt it. We can go on about using Views forever, but the point is, in a Drigg site using Views makes things much more complicated and -- worse -- not as functional.

Bye,

Merc.

philbar’s picture

philbar commented
Status: Closed (won't fix) » Postponed

Sounds like arguments could be used to quite easily provide the "smart link" functionality.

When you first investigated this, did you happen to look at Views1? Views2 is a huge improvement.

Marking as postponed. When I get a chance, I will to investigate using Views in place of Drigg_UI and Drigg_RSS. If someone else beats me to it, that will be great also.

You don't need to worry about this Merc.

philbar’s picture

philbar commented

Why use Views? Why not write your own queries?

mercmobily’s picture

mercmobily commented

Hi,

I know Views quite well. In fact, I wrote a whole lot of integration code between Views 2 and Friendlist when I wrote Friendlist...
I don't think views arguments will be of much help.

But, as usual, I might well be wrong. Leaving this as postponed for 6 months, let's see if you manage to dislodge Drigg_ui .

Thanks,

Merc.