Panels 2.0, alpha 10

I added arguments to this one. There's a pretty sweeping change here, partly in that it's doing ajax outside of the main content area; partly in that I re-organized the file structure rather a lot; and partly in that I opened things up. A lot.

My brain is pretty wiped so I'm having trouble describing what I did, but in my mind it is totally full of awesome.

Remaining TODO list before I can call this a beta:

o finish argument for taxonomy
o finish content types for taxonomy
o argument for user

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.

I've got a nodequeue 2-rc about ready to go, and I just realized that I need the database stuff translated to pgsql. Anyone postgres friendly want to take a crack at patching the .install file?

No sooner do I release alpha 8 than do I discover I put in a critical bug making it difficult to enable/disable the panel pages module. Thus:

Panels 2 alpha 9 -- also it includes the ability to use % as a wildcard in URLs. This is similar to $arg in Views.

Also, for those new to Panels, be sure to turn on the panel pages module or it won't do much.

I've released Panels 2 Alpha 8.

This new release introduces Mini Panels and Panel styles for them. In the next release Panel pages and Panel nodes will also be able to support panel styles and Panels will come with a couple of simple ones, but for now, there are 2 out there that exist:

Carousel style and
Tabs style.

What does this do? See for yourself.

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

While I'm on the topic, these are the remaining TODO items before I am ready to call Panels 2 beta:

1. Pluggable context. This means letting the panels page have a context selector (think: argument in Views) that can validate the argument and load the context. I want to supply user, node, vocabulary and taxonomy term contexts, and it needs to be able to identify basic Views arguments to correlate how a View can automatically be promoted to function with this context.