After over four years of working with Drupal, I have finally reached one of the major goals that I have envisioned from the beginning. Today I released the first beta of Panels Everywhere, a new module that works with Panels and Page Manager that allows you to never use the block management system again.

Ahh, you gotta love IRC. Allow me to share a short edited snippet. IP addresses have been removed as well as some comments by people that are not really relevant to the conversation. The best part are the /whois results.

I'm not in any way upset about this. I think this is funny, and felt like sharing.


[20:01] *** kinesis (n=k@xx.xx.xx.xx) joined
[20:01] drupal vs joomla and why
[20:03] kinesis http://www.whitehouse.gov/
[20:03] This is an IRC chat, not google.
[20:03] thats nice

Heading to the airport to go to Paris shortly. DrupalCon is Sep 1-5 and it'll be fun to see a bit of Paris before that.

For the next two weeks expect no or next to no activity from me in any of my issue queues. For a week or two after we come back, don't expect much better. Post-trip trauma is always fun.

That's right. Panels 2 never managed to get a 2.0 release, it got caught up in rcs and brokenness that was unfixable. Panels 3, however, has managed to duck that curse, and it is now official. Panels 3 is released. It really needs CTools 1.0.

Panels 3.0: http://drupal.org/node/554226
CTools 1.0: http://drupal.org/node/554222

Panels 3 has seen radical changes since Panels 2, and is a great deal more powerful, easier to use and we think you will like it a lot.

Please understand that the upgrade from Panels 1 or 2 to Panels 3 is a little bumpy. Not everything upgrades perfectly. Some people have had to uninstall and reinstall to make it work. Some of the back and forth during the betas and rcs caused irreparably messed up data that does not carry forward properly. I apologize for this. BACK UP BEFORE YOU UPGRADE.. If you do not read these release notes, and do not back up, please do not post issues. =)

The best way to use Panels is to pair it with the Page Manager from the Chaos Tools Suite, and use its interface for creating panel pages. This completely replaces the Panels Pages module from Panels 2. If you used an earlier beta version, the Page Manager used to be known as delegator. If you are upgrading from Panels 2, and the CTools module is already in the tree but not enabled, it will be automatically enabled for you. This is the best way to upgrade from Panels 2. Please ensure that you are using CTools 1.0 alongside this, and not a beta version! Earlier versions of CTools will not work with Panels 3.0!

Page Manager introduces the concept of Variants which are different ways that a page can be displayed. For many uses, you will have only one variant. However, if you want a page to look different based upon the data being displayed (for example, you want story nodes displayed differently from article nodes), or permissions of the user (you may want an administrator to see something different from a regular user, or a logged in user to see something different from a logged out user) then you will add additional variants to a page. You will use the selection rules to determine which variant a user sees. Remember that the first variant that passes the selection rules will be used, so be sure to put the most specific rules first and the more general rules later. You can put a variant with no rules at all last and it will serve as a default.

There is a real need for tutorials, screencasts and documentation for this system to be written. It's at this point that I'm really looking to the community to provide help. My own motivation to write this stuff is fairly low, and I know there are writers out there who use this stuff who can help. Please participate! Documentation is a great way to give back to the community in return for software, and requires very little (sometimes no!) coding knowledge at all.

This is a call to translators. If you're interested in translating Panels and or CTools, I am going to do a full release by the middle of next week. Any translation work you want to go out with this release should be checked into CVS by then!

Panels has only one translation and it's very old, so it is probably more or less useless. CTools has no translations at all (and I am not surprised by this).

I spent the better part of a week doing nothing but this and sleep, but I think it's nearly ready. If you're brave, you can go get the current one out of CVS. I warn you, it'll be minorly annoying because I got rid of the delegator (What's that do?!) module and replaced it with the Page Manager (I bet you can guess what that does) module.

First, once you've got everything, if you go to admin/build/panels you'll see the Panels dashboard. It's really just an overlay over other stuff, because Panels itself doesn't really have a UI. But it gives UI to lots of other stuff.

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.

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.

Currently the Drupal pager system is an interesting look into some of the past decisions in Drupal design. The system is actually a very powerful paging system that can handle multiple pagers on the same page that act completely independently. However, it is also a kind of messy piece of code that stores a lot of its data in very obscure globals in formats that don't make sense. It is difficult to document and even more difficult to understand from the outside.

I'd like to compile a list of modules that use Views heavily (examples: Flag, Views Bulk Operations, Views Attach, Views Reference) with a blurb about each of them. The blurb would contain a neutral description of what they do, and then a non-neutral comment on the quality and maintenance level of the modules. Obviously the latter is a judgment call and I don't expect it to be completely dead on, but I would like to note projects that are well known to rarely get bugs fixed. Another comment might be known usage levels, some of which can be gleaned from the shiny new usage statistics.