Here's a link to my presentation, http://goo.gl/WTlj9. Source code will be posted here shortly. Or you can search to see some outdated code from DrupalCon SF and DesignCamp Boston.
I've been having fun playing around with AIR's NativeProcess class. This app I'm writing in my very sparse free-time is an application to help you manage a Drupal website. Features are limited at the moment. The code/info is here: http://code.google.com/p/drushpal/
People are never satisfied with WYSIWYG plugins. One of the biggest frustrations, especially when working with an Administration theme, is that what appears in the editor is NOT the same as what appears on the website. And the "preview" button does no good either. For instance, if you've got custom spacing, list styles, or specific classes for typography, you're not going to see them in your WYSIWYG editor, and therefore, what you see is not what you get.
It's been a few months since I blogged. I've been busy. In addition to working on a few new websites, I've also been writing a new app.
In the next few weeks, I should have some alphas up for testing on Drupal.org. It's not a module... it's a desktop application that brings the power of Drush to the Window's, Mac, or Linux environments with a graphical user interface.
Attached is a module that styles the IMCE module to match the CKEditor module. This is based on the previous work that Mike the Coder and Danny Joris before him. I made it so that you don't have to modify your theme to get it working, and more specifically, two themes since I'm using admin theme. The only thing you have to do for it to work is to put the "sprites.png" from the CKEditor download into the "images" folder of the module.
WOW! PressFlow is amazingly fast. My question is, why would anyone NOT use it? I've got a pretty basic site running now, which should launch too, that's loading in 0.15 seconds. The site, previously running on ColdFusion and a CMS called FarCry averaged load times of 4 to 5 seconds. That means It's gotten about 30 times faster.
As I'm teaching some friends the basics of Drupal I see a common mistake, putting too much functionality into the theme. The real problem with this is simple: the site's look and feel may change with or without the site's functionality. If you're using a custom theme, it's tempting to throw functionality right into page.tpl.php and call it a day. But you're setting yourself up for headaches. Trust me, I know from experience.
