Should the signup module require the views module?

For some background, see #582986: Make views a required dependency and ditch non-views code?.

According to the update_status usage data, 91.5% of D6 sites using signup already have views installed (not too surprising).

There's a fair bit of code and UI complexity to provide various fallback options when views isn't installed. I'm strongly tempted to ditch all that and tell the other 8.5% of signup users: "Install Views2 already, fools, you're missing out!". ;)

Thoughts?

Thanks!
-Derek

Ok, that's easy to agree with.

The only argument I've heard for not depending on views has been small sites that want image galleries.
I think if you're using signup, your site counts as big enough.
Simplifying the module and also adding flexibility -- a +1 from me.

The one thing I didn't mention in my original comment here was the issue of Views Bulk Operations (VBO). There are only a handful of sites using both signup and VBO (~9%). If I rip out the non-views fallback code, folks will experience a loss of functionality (e.g. they won't be able to select some signups at node/N/signups/admin and cancel them all) unless they install VBO...

Another thing someone mentioned was what about porting to D7 before views D7 is released? It's likely that D7 views won't be out immediately. However, that also means that 91% of the sites using signup won't be able to upgrade to D7, either... ;)

Anyway, more food for thought...

I think making signup.module dependent of both the Views and VBO modules would make sense. This gives the user the most useful features and eliminates the need and confusion of the fallback options.