The views issue queue is officially Huge. It might even be *(&)ing huge at this point, but I'm not sure where the cutoff between huge and *(&)ing huge actually is. Either way, it's way, way, way beyond my control. It's like a giant yard that, no matter how much you trim, the grass always grows faster than you can grow it.

It's not like I totally ignore the queue, but to be fair, it takes a lot of time to go through some of this stuff. I just went through some 50 issues and really I've barely dented the thing.

Views 2 is proceeding apace, mostly on the weekends. With the baby I'm just not having the time throughout the week to actually work on it, which is unfortunate. But I thought I'd share with the world at large some of the things that are going on under the hood. This might be especially interesting to people who have utilized the Views API in the past; I decided to go for Drastic Changes.

From chx's blog:

Alas, this post is not about announcing such an awesomeness. But i would like to draw attention to the new, open-to-other-modules subscriptions 5.x-2.x branch and what a fantastic piece would be a small module that ties views and subscriptions together. According to Earl Miles, the creator of views:

you could grab the view, add a nid filter to the view (or argument), run the view and get the result. If there's a match, it's in the view.

If you are up to code this module, contact me and I will help with the subscriptions parts, the API is not yet documented because it's a bit in a flux.

Somebody give 'im a hand, eh? =)

In this issue in the Views' issue queue:

How can I fail to understand you haven't even bothered to give a good
reason against? Duh. Oh and this isn't /your/ issue queue; you don't
/own/ Views (and this issue isn't even assigned to anyone anyway).

(Yes, that's to me).

I already told the guy I wasn't responding to him anymore.

If so see this: http://drupal.org/node/104848

These are my high level design goals for Views 2.

Views 2 will be the Drupal 6 port. Views 1 will not be ported to Drupal 6; this is so we can make wholesale changes to the API at the same time there are other changes, reducing the number of complex upgrades required.

At long last, I have decided to end Views 1.6 beta status. I've fixed the bugs I considered critical. (Not that there aren't still bugs; some annoying and hard to fix, some edge cases, some I just don't understand). But the last one that was really giving me fits is fixed.

PLEASE PLEASE PLEASE back up your databases before upgrading!!!!!!!

Views 5.x-1.6
Views 4.7.x-1.6

I get asked a LOT about making a view into a form -- the primary use is to make a bunch of checkboxes with a submit button, but there are many other forms too.

Mark Frederickson has been working for quite some time on a patch to Views to do this, and I think he's been getting pretty close to something. I haven't looked at it much myself because I am completely overwhelmed with Views issues, but I urge people to check this out and help him with his development:

http://drupal.org/node/103171

So yes, this is beta3. With luck there will not be a beta4, just a 1.6 that follows it; but I’ve already had 3 critical bugs come up. Mostly because the long gap between 1.5 and 1.6 saw a LOT of code changes/improvements and, naturally, I didn’t test them well enough. (This is why I called it a beta. I knew I didn’t test it well enough).

Feel free to give it a try:

For Drupal 5

For Drupal 4.7