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.

I've spent a lot of my 'between' time thinking about what I want to see for the next major revisions of Views, and I've finally decided to sit down and actually create a road map. Views 3 isn't like Views 2 in the sense that there will be a rewrite. On the contrary, I'm really happy with the foundation of Views 2 and I believe that we have a solid system for building on. What I'm unhappy with are features that got left out, or that I didn't even know we would need.

One thing panels does well is to put a bunch of unrelated or at least not directly related content in different areas on your page. One thing it doesn’t do well, by itself, is to stripe content across regions.

But what we can do is get Views to do that kind of thing for us. And because Views is not plugin driven, instead of telling the user “Oh you have to theme it” we can provide a plugin that does exactly that. In fact, I’ve decided to try and do away with the “Oh you have to theme it” answer, and created a new project on Drupal, called the Views Bonus Pack where I (and some other people who do a lot of Views work) can put plugins and default views to give the starting user a place to work from as well as a bunch of cool tricks.

An infrequent but relatively common issue I've run into with Views is that when showing teasers, a common number of posts per page is 10; but when showing the single lines from the summary, 25 is much more common. But Views doesn't let you change the page size in summary view mode.

Note: If you don't know what summary view mode is, this page is a summary (what happens when a view has an argument and the argument is not present), while this page is the view when an argument is present.

I'm pretty impressed at all the excitement coming out of the whole design4drupal initiative. Lots of people are talking, and the chatter is everywhere. Unfortunately, from my perspective, it's looking like it may actually turn out to be one of the most damaging things that can happen to Drupal, and this one is bothering me at a very deep level. And perhaps this is something that's been building up, because I have definitely noticed my enthusiasm waning over the last year, and things like this are really putting a bullet into the heart of it.

Recently it's come up that some members of the community don't actually understand the Drupal Association, or what it does, or even who it is. I think there are probably several reasons for this void of knowledge, including the fact that Association meetings happen largely behind closed doors, and that we in the Association don't do a great job communicating what is actually happening behind those doors at this time. I hope to help fill in some knowledge gaps and set some people straight on what the Association is, who the Association is, and what the Association does.

I've long been of the belief that Drupal's love/hate relationship with Object Oriented programming is kind of an odd situation. Most of the time it's not really a problem, but sometimes we come so close to using OO methodology that it seems like a waste that we're not simply OO. One of the places that really shows up is the Forms API.

The design of the Forms API is exceedingly OO; but we're not using OO at all. I spent a little time thinking about it, and I knocked off an idea of what the current Forms API might look like if it were OO.

A lot of people don't realize how useful Node Queue is as a module; in part because the name doesn't do a very good job of explaining what the module does. For one thing, it almost seems like it duplicates taxonomy, or maybe bookmarks. But it does something none of those modules do: It orders your nodes completely arbitarily.

One other valuable point: Queues have a maximum size. When the queue is 'full', if a new item is added, the the last item in the queue is automatically removed.

What is this good for?