Planet MVC

We're incredibly pleased to announce the release of Django 0.96!

The primary goal for 0.96 was a cleanup and stabilization of the features introduced in 0.95. The release notes cover the few backwards-incompatible changes, but for most people the upgrade process should be simple.

One particular change affects users of MySQL on older servers: If you get an error about Django requiring a newer version of MySQLdb, you'll need to either upgrade MySQLdb to 1.2.1p2 or later, or switch your DATABASE_ENGINE setting to "mysql_old". You can read more about this change in the release notes.

Though the main focus of 0.96 is stability and maturity, it also includes some juicy new features to help you write even better code. Of particular note:

• Django now ships with a comprehensive set of testing tools. You can write tests based on doctest or unittest, test your views with a simple test harness, and load initial data ("fixtures") automatically.

  If testing is indeed like flossing, think of these new tools as super-comfortable, deliciously flavored, top-of-the-line thread.

• Django 0.96 also ships with a brand new forms library, django.newforms. This is a replacement for django.forms, the old forms/manipulator/validation framework. Both APIs are available in 0.96, but over the next two releases we're going to switch completely to this awesome new system.

Read the release notes for more details on these and other changes.

We can't possible thank our amazing development community enough. This release contains the work of over 200 different people. To put this in perspective: when we released 0.95 we thanked "the dozens of Django contributors"; this time, it would be more appropriate to thank hundreds of contributors. In other words, this release wouldn't have happened without this amazing community.

To everyone who's reported a bug, submitted a patch, participated on our mailing lists, hung out in our IRC channel: our most heartfelt thanks. As always, We try (but inevitably fail) to list everybody in the AUTHORS file.

So, what are you waiting for? Go download 0.96, and let us know what you think!

If you are using CakePHP 1.2 you probably noticed the folders /app/tests and /cake/tests. They are part of the official CakePHP test suite which comes with Cake.

Before you can use it, you have to download SimpleTest, the testing framework used by the test suite. Extract the package to your vendors folder and you are ready to execute tests. (If you have an advanced setup you also have to change the value of CAKE_CORE_INCLUDE_PATH in app/webroot/test.php)

To execute tests you have to go to example.com/test.php and you will see the following page:

There you can select whether you want to execute the core tests or your own application-specific tests. These application-specific tests must be placed in the respective folders in app/tests/cases resp. in app/tests/groups if they are group tests. The file names of the tests must end with “.test.php” (e.g. “user.test.php” for the user model test) respectively “.group.php” (e.g. “helpers.group.php” for a group test of all helpers). It’s imho a bit illogical, as everywhere else in the framework an underscore is used to separate the name parts. As usual in Cake, the class names are camel-cased, so the class names will be “UserTest” and “HelpersGroup”. Apart from those conventions the tests are “normal” SimpleTest tests, there is no magic (yet). You can find many real-world examples of such tests in /cake/tests.

Personally, I still prefer my own test suite, even though it requires a bit more configuration work.

Happy testing :)

On IBM’s developerWorks the third part of the series “Create an interactive production wiki with PHP” has been published. This part deals with file uploads and access control (no, it doesn’t cover ACL).

Read the article online (registration needed) or download it as a PDF.

Previous parts:
Part 1 as PDF
Part 2 as PDF

PS1: CraZyLeGs’ blog has a new virtual home: http://www.devmoz.com/blog.
Ps2: I did a little redesign on my blog and switched back to a two-column layout. I hope it is now I bit less cluttered ;-)

It’s been five days since I posted my initial review of Highrise, that shiny new application by our friends at 37signals. I’ve been getting adjusted to my new process of managing contacts and have had to remind myself a few times that there is a brand new tool that aims to make my life a little easier.

I haven’t heard about a Highrise API available yet, but I will definitely be looking into tighter integration once that is available.

It seems that Highrise isn’t going to allow direct emails to be sent to it, they need to come from an existing contact in your account. For example, our contact form sends an email to our customer service mailing list. At one point, we had it connected to the Basecamp API to submit each new contact request as a new message in a designated project, but it didn’t really give me what I was looking for. Since each user in Highrise has a custom dropbox email address, I thought that I would try to link up the contact form to submit directly to Highrise.

I got the following response back from Highrise. ;-)

Hi Robby- An email was sent to your Highrise dropbox from john@cusackforpresident.com. This address does not correspond to any address that you have recorded for yourself in your Highrise account, and so the email was discarded.

So, in the meantime, I’m following this process with new contact requests as well as the other people at PA who are responsible for responding to Contact Requests.

So… let’s say that John Cusack (one of my favorite actors while growing up) is having a weird dream and wants to get a website built for the record store that he ran in High Fidelity.

He fills out the form and submits it, which our application than stores and also sends over his contact information to our customer service email address.

A few minutes later…

Here I am in Mail.app and doing a double-take… “is that the real John Cusack?” (no, it’s just test data).

I then ask myself the following questions…

• Can I answer this in less than 2 minutes?
  • If yes, respond immediately (forward to Highrise, if contact info will be needed again)
  • If no, forward to Highrise

Okay, so I’ve decided to forward this contact to Highrise as I decided to go ahead and speak with John over the phone, since he was kind enough to leave his phone number.

As I mentioned in my last post, I’m using Act-On for forwarding emails to Highrise.

(back-tic h)

...and off the email goes.

I’m now logged into Highrise and looking at my dashboard. As you can see, John Cusack is now at the top of my dashboad and waiting for me to decide if I want to do something with it.

As I mentioned, I spoke with John over the phone and promised him that I’d send him a follow up email with a proposed date/time for a meeting next week.

...and that’s one way that I’m now using Highrise to getting all my contacts organized.

Well, after five days of using Highrise, I’m still impressed with it. Our Administrative Assistant began using it last Friday and is using it to schedule follow up tasks for me. This definitely beats the old process of leaving post-it notes on my desk with names and phone numbers. :-)

We also upgraded to a paying account and paid for invoice #4.... and I plan to hit contact #200 later today within our account.

A few bugs:

• Forwarding email from Thunderbird doesn’t currently work (as of last Friday)
• A few forwarded emails from Mail.app didn’t work right (garbled… html emails perhaps?)

Also… it appears that 37signals has opened the doors to the public earlier today.

Have fun!

If you missed PHP Quebec, here are some more conferences with symfony talks. Dustin Whittle, from Yahoo!, will talk about symfony a lot this year:

• Ajax World Expo - NYC, NY
• Web 2.0 Expo - San Francisco, California
• USENIX Conference - Santa Clara, California
• International PHP Conference 2007 - Stuttgart, Germany

Last week, I attended the PHP Quebec conference. It was my first conference as a speaker and PHP Quebec 2007 turned out to be a really good conference.

I spoke on the first day about symfony in french. I also spoke on the second day about symfony, but in english this time. I reworked my slides between those 2 talks, so english slides are slightly better (with less typos/errors).

The slides are available here:

• Slides in english
• Slides in french

As all the talks were recorded, I will also try to synchronize slides and voice later this month.

We released symfony 1.0.0 just a month ago. Time for another release. symfony 1.0.1 is a bug fix only release. The symfony 1.0 branch only contains bug fixes (no new features).

Here are all bugs fixed in this release:

• r3624: fixed security.yml case sensitivity
• r3599: fixed sfYaml::load() not returning correct values
• r3598: removed unneeded usage of JavaScript helpers in the web debug toolbar
• r3597: fixed sfConsoleRequest::initialize() signature
• r3541: fixed typo in the cache classes when logging

The major bug fix concerns the security.yml configuration file and actions case sensitivity (see r3624 changeset and symfony mailing-list for more information of the issue).

So, if your application contains some secured modules, this is a recommended upgrade. As for every 1.0.X release, you can upgrade to 1.0.1, clear the cache and you're done.

Up to now if you used the HTML or the form helper, you did it in the following way:

$form->input('User/password');

With changeset 4630 this approach has been deprecated in CakePHP 1.2 (but it will still work, of course). The new approach uses a dot notation:

$form->input('User.password');

Javascript was one of those things I tried to avoid up to now. I don’t know why, but somehow I disliked it (probably because it was a pain to use it in the early days of Javascript) ;-) Sure, I used a bit of Ajax here and there, but thanks to the CakePHP Ajax helper I didn’t had to touch the Javascript.

Lately, I decided to do an Ajax application and so I had to learn Javascript. To make my life easier, I decided to use the JQuery framework. I have chosen JQuery over Prototype because I heard many good things about JQuery, and the API documentation was (and still is) more intuitive.

Of course, my first attempt ended in a total mess. The result looked more like spaghetti than code ;-) That’s when I recalled an article (in German) about a Javascript MVC framework called Jamal, developed by Timo Derstappen. From the Jamal website:

The MVC concept is easy to adopt for javascript

• Controller: Interaction with the user interface (events)
• Model: Business Logic and AJAX calls
• View: DOM, CSS modifications

That makes sense. So I had a closer look at Jamal. It looked nice, but it bothered me that you would have to use a CSS class “jamal” in the HTML code to make it work. So I wrote my own implementation called “jscake” which avoids that. You can find the first version in the downloads section.

Let’s create a simple “Hello world” example with jscake. Our example (CakePHP) view will contain a link and a div to show the messages:

<a href="">click</a>
<div id="messages"></div>

First we create our model. All models are in the “$m” namespace (please correct me if that is the wrong term), which is a shortcut for “jscake.models”. So our model is called “$m.Example”. The model contains one function to return the text which should be displayed:

// app/webroot/js/models/example.js
$m.Example = {

    getText: function() {
        return "hello world";
    }
};

The view is similar to the model, it contains only one function, too. In the function the element with the id “messages” is located and the text appended to that element. Similar to the models the views are in the “$v” namespace.

// app/webroot/js/views/examples.js
$v.Examples = {

    showMessage: function(message) {
        $('#messages').append(message);
    }
};

Last, but not least, we have to create the controller. The index function is automatically called when the JQuery ready event occurs. In this function we simply say that when someone clicks on the link, the other function of the controller (sayHelloWorld) should be executed.

//app/webroot/js/controllers/examples_controller.js
$c.ExamplesController = {

    index: function() {
        $('a').click(this.sayHelloWorld);
    },

    sayHelloWorld: function() {
        $v.Examples.showMessage($m.Example.getText());

        return false;
    }
};

To make our example work we have to include all needed Javascript files in our view, with CakePHP 1.2 it looks like:

<?php $javascript->link(array('jquery-1.1.2', 'jscake', 'controllers/examples_controller',
'models/example', 'views/examples', 'start'), false); ?>
<a href="">click</a>
<div id="messages"></div>

Have fun with jscake! Feedback is welcome :)

So, today I got what I’ll call a platinum ticket from one of our pals at 37signals for their upcoming new application, Highrise, which is what they’d call a “shared contact manager.” The rest of you can keep hoping that you’ll win a golden ticket this weekend. ;-)

For the past year and a half, I’ve been wanting to build some sort of contact and task management tool for organizing all of the contact requests that PLANET ARGON receives about our Design and Development and Rails Hosting services. If I go away for a week, I come back to a huge backlog of people who may be waiting a response from me. Having a tool to allow others at PA to see what is in my queue and in some cases, respond on my behalf… has been needed. When I first heard about Highrise long ago, I got excited and have tried several different tools and each of those tools has left me feeling uneasy. Perhaps I’ll post some reviews of the other tools one day.

The signup process looks familiar… :-)

Well, it definitely looks and feels like a 37signals application. There might have been a time when I thought that would be silly… but really, when you look at other product suites, consistency is extremely important to the user experience. While they are definitely going to attract people to Highrise who have never used any of their other products, I’d also expect a huge majority of their initial customers will be users of their other products. It’s obvious that Highrise was in response to a void in the market that people (likely customers) were asking for in other products like Basecamp.

Highrise has all the Ajaxy goodness that you’d expect in a brand new modern web application. Most of it seems very intuitive, but I found myself getting caught up on the extra tabs across the top of the screen. When new tabs appear, my natural response was to try to close them when I was finished looking at the page. Perhaps this is just a design decision that I’ll learn to really like. At the moment, I’m still not quite sure because I expect the tabs to change quite frequently.

(few minutes later)

Actually… I wonder if the interface designers at 37signals did this to help their users avoid having several tabs open in their web browser. I use Safari for Basecamp and generally have 5-8 tabs open throughout the day for different projects that our team is working on because the Dashboard view doesn’t really give me a good feel for what is happening throughout the day on our various internal and client projects. I’ll try to pay attention to my usage habits to see if I’m opening less browser tabs in Highrise.

So far, this is the one thing that I’m not quite sure about (yet).

Once I saw that you could forward emails to Highrise and it’d auto-magically create a contact and store it, I jumped for joy (not literally… but I got an evil grin). I have been using (more like heavily relying on) Mail Act-On for what seems a really long time. I’m constantly forwarding emails off to my colleagues to keep things from sitting stagnant for too long. So, guess what I did?

This is working beautifully and allowed me to move about 20 contact requests to Highrise in just a few minutes.

With this new ability, I can remove that one project in Basecamp that I was using to collect contact request information. That information now has a proper home!

I’m taking more screenshots and going to continue putting more of our contacts into Highrise… so… consider this part one of a short series of posts.

To be continued…

Hey folks,

it's been a while since my last post on JS (and in general) and I apologize for that. There is just way too much stuff for me to do right now (client work, my own web app, school finals, etc.) but most of that will be over at some point and then I'll have a thousand interesting things to blog about as well as the time for it. Meanwhile here comes some fun JS stuff I'm using in the web app I'm working on right now and I hope you'll enjoy it. When you see the '$' sign in the code then it's the jQuery library I'm absolutely in love with and not the evil prototype one ; ). All code I'll post now can be written without it, but I don't have the time to present alternative solutions right now.

Alright let's get started. First of all I advocate the usage of a namespace for the functions I'll present since that makes it less likely to run into conflicts with 3rd party scripts as well as allowing for the code base to stay more maintainable. I'm assuming you are using CakePHP so please create a file called 'common.js' in /app/webroot/js/. The other file you put in there is the latest 'jquery.js' that you downloaded from jquery.com. In your html layout you include jquery.js first and common.js second.

The first thing I got for you is a function capable of determining the base url where your application is installed. This is very useful when doing lot's of ajax requests and you want to be able to always use '/controller/action' style url references like you do in CakePHP internally. It's also nice to know image files will always be located in '/img/...'. The way I do it is inspired by the script.aculo.us lib and looks like this:

The code should be pretty straight forward. After defining the Common object (used as a namespace) we call it's setBaseUrl function without parameters. This causes a jQuery selector to find the script element of our common.js file and use it's src attribute to determine the baseUrl. From that point on we can do calls like this in our other JS files:

Alright this is useful (at least I hope so), but there is more stuff to come. One thing I found myself working a lot with was collections of objects of the same type that need to exchange messages through events with one another. For example you have a class called 'Task' and all of them are managed by another object called 'TaskList'. Now let's say the User is able to click on each Task in your TaskList which causes this particular Task to get the focus (a couple of DOM elements getting an 'active' class). When one Task get's focused, naturally all other tasks need to loose their focus. Here is some code similar to what I'm using in my application right now which will make this become very easy and fail-safe:

A new generic broadcastEvent function for our Common namespace. It basically loops through all listeners (array of JS objects) and sees if they have listeners for the particular task defined and call those up. It also set's the context of the listener function to the object that is listening and uses whatever additional parameters are passed to broadcastEvent for calling it:

And here comes the TaskList that object that manages all Task's on the screen. It basically uses a table (element) as it's construct parameter, loops through all rows with a 'td' in them (those that are not part of the table header) and passes the table row elements as an initialization parameter to the Task object that is created for each one of it and added to a list of tasks. TaskList.broadcastEvent uses Common.broadcastEvent to allow the tasks inside the TaskList to communicate with one another easily which you'll see in the Task class.

And here comes the Task class that triggers the event broadcasting and listens to events. It's constructor takes two arguments. The first one is a reference to the parent TaskList object and the second on is the table row (tr) element that hold the DOM representation of this Task. When the name of the task ('a.name') is clicked then it causes that Task to get the focus and all others to be blured (as they receive the focus event and react on it):

Alright that's it. The code above is of course just meant for educational purposes and not the complete code I'm using in my web app which is a little more complex and would only distract from demonstrating the Common.broadcastEvent function. So if it doesn't run it's probably because I didn't test the simplified version presented here.

So let's come to my last little trick, sorting elements in JS. Javascript has a very cool function build into the Array class named sort that is very useful for doing all kinds of sorting as it allows you to define a callback for comparing the array elements yourself. It basically works like this:

The following code uses jQuery to get all list items inside of a unorder list and then sorts the array using the anchor text (for simplicity, innerHTML).

But since we don't only want to sort them inside the array but also in the DOM, we need to get a little more tricky. In the simplest case this means to remove all li elements from our unordered list before sorting and them put them back into our list after we sorted them:

If you don't like the train-wreck style you'd write the above like this:

So of course if you work with large lists of items you might want to actually swap elements using the Array.sort callback instead of re-populating the entire list, but for this example I wanted to keep it simple. Also here is a live demo where you can check out how the method presented here works on a small list. You basically can not tell that all elements where removed and then added again.

Alright, I hope you find some of the above stuff useful and if you have any questions feel free to ask them in the comments.

-- Felixd

Remember that blog named Typo, the one that was really active under development and a lot of us got our start with when rails first became known as the hip framework that it is? Well, they’ve been plugging away for six months or so in the back of seedy bars and diners on their laptops to finally release their 4.1 version with talk of 4.2 soonafter. I even have to upgrade myself for the ruby on rails blog which is still running typo for those of you curios enough to ask…

Here’s the scoop on what’s new:

The changelog is quite impressive, but I’ll only deal with the visible part of the iceberg :

* Ruby on Rails 1.2 support.
* Complete functionnal revamping of the back office, and partial ergonomic rebuild.
* Internationalization and localization support using localization plugin. The application now runs in French.
* Comment and trackback default moderation.
* Lots of bugfixes and code improvement.
* RSS support for tags and categories.
* Plugins now use Rails plugin engine. We’re gonna release packed plugins soon.

Typo 4.2 is due in 2 months, and the roadmap is quite impressive :

* Support of a publishing workflow and users roles.
* Multiple blogs support with a single Typo instance.
* Switch from Localization to Globalization.
* Integrate proposed patchs as plugins.
* Finish the admin revamping.
* Support more languages.
* Stop doing stupid things like starting to support localization the day before the planned release date.

The project is looking for translators a designer to work with me on the admin while I’m doing the ergonomic stuffs.

You can download the source or install Typo via the gem :

laptop # gem install -y typo laptop # typo install /some/path

[edit] There’s a bug in the migration process if you come from the 4.0 version. Before doing the migration, edit db/migrate/056createnotifications.rb and comment the following line : drop_table :notifications

If you have already started the migration, comment both lines : renametable :notifications, :oldnotifications drop_table :notifications

The Ruby on Rails team is at it again with another update to… you guessed it, Ruby on Rails. According to the administration, this release irons out the few wrinkles there was between Ruby 1.8.6 and Rails 1.2.2. Not a critical upgrade for most but a useful one for all of us using Ruby 1.8.6.

On another note, why stop at upgrading rails.

Check out the latest version of mongrel as well. That fine piece of software has really gone a distance. That isn’t to say I haven’t had some unexplainable issues lately with session freezes but that could be config issues on my part. I’ll actually be posting about it once Tommy or I figure it out.

To upgrade both of them, simply do: gem update rails mongrel -y

And there you have it! Have fun and try not to lose your wrench!

Some time ago I wrote a post titled “Referencing Javascript files” in which I explained how you can reference Javascript files.

Now I noticed that the same approach also can be used for CSS files. For this purpose an additional parameter was added to the css() function in the HtmlHelper in CakePHP 1.2. So to load a page-specific CSS file you can add the following code to your view (notice the fourth parameter):

$html->css('page_specific', null, null, false);

Or if you want to load multiple CSS files:

$html->css(array('first', 'second'), null, null, false);

To make those snippets work you must have the variable $scripts_for_layout in your layout:

<head>
    <?php echo $scripts_for_layout; ?>
</head>

It is the same variable used in the approach to reference Javascript files.

If you are a regular visitor of the symfony community page, you probably noticed that it radically changed recently. Instead of a simple hub page leading to the forums, mailing-lists and wiki, the community page is now an aggregation of content from all these sources, as well as an overview of the latest posts mentioning symfony in the blogosphere.

If you want your weblog to be included in the list of sites visited by our aggregator, please add it to the list of symfony bloggers in the wiki. You will receive a visit once a day from our server, so it shouldn't change your weblog stats too much...

The new community page makes a heavy use of two new symfony plugins, sfWebBrowser and sfFeed2. The first is a lightweight HTTP client, RESTful and similar in syntax to the sfTestBrowser. The second is a refactoring of the original sfFeedPlugin, which you probably heard of when following the askeet tutorial. What's new in sfFeed2 is that not only does it publish RSS and Atom feeds based on an array of objects, it also reads feeds fetched from the Internet and allow their manipulation and aggregation.

These two plugins are just a sample of the fantastic plugin activity since the 1.0 release. Several new plugins are released every week, and the list of available plugins now shows more than fifty plugins, and counting. I mention only a few ones here, just as an appetizer:

• sfDoctrine: A full-featured model layer, providing integration of the phpDoctrine ORM. Comes with admin generator, schema.yml, i18n, fixtures loading, etc.

• sfPokaYokePlugin: A client-side validation in JavaScript, using the rules defined in your YAML validation files.

• sfPropelActAsNestedSetBehaviorPlugin: An implementation of nested sets for Propel, packaged as a behavior.

• sfUJSPlugin: A replacement for Prototype, aiming at unobtrusiveness and ease of use. Currently uses jQuery instead of Prototype.

Plugin authors are advised to publish a post in the users mailing-list whenever they release a new plugin or an important upgrade. As for the developers, they already know how to spot new plugins by following the trac timeline.

We strongly advise you to watch the plugins page and test the newly released plugins - developers love feedback, and who knows, a plugin may save your day. If you feel like contributing a piece of code that you find particularly useful, you now have plenty of examples on how to package it into a reusable plugin.

So write about symfony and contribute new plugins, the symfony community will thank you!

InformationWeek has a short story titled, Poor Communications, Unrealistic Scheduling Lead To IT Project Failure.

“Communications failures top the list of reasons IT projects fail, according to poll results from the Computing Technology Industry Association.

About 28% of 1,000 respondents identified poor communications as the main cause of project failure, according to CompTIA, which offers project management training.”

So, while we’re all spending so much of our time focused on improving our technical skills, are we also investing our time into becoming communication superstars?

If you look back at the following posts, you’ll see some links to some excellent books on this topic.

• Project Enlightenment with d3
• The Technology of Dialogue
• Those that Tend the Store need Dialogue

After kicking myself all weekend for not heading to SXSW... was getting ready to head to sleep last night and saw a post by Michael Buffington announcing that Stikkit won an award for Best Technical Achievement.

Congrats to Rael, Michael, and the rest of the Stikkit team!

As mentioned a few weeks ago, I’ll be up in the Seattle area in a few weeks. I took the invitation to head to the 2007 Microsoft Technology Summit in Redmond, WA. When I received the invitation… my immediate response was, “Why me?”

Their response?

“The event is specifically for people other than Microsoft fanboys… they want to have a dialogue with influential members of the developer community outside of their comfort zone to see what we can learn from each other..”

Fair enough. Perhaps they’ll convince me to switch our entire team to Microsoft products… but I highly doubt my team would be cool with that. ;-)

It looks like Michael Koziarski (of Rails Core fame) will also be at the event. Supposedly, there will only be 50-60 people… so if you’re also going to be there, let me know.

I’m not sure what to expect yet from the event and they don’t have a web page dedicated to it. The most that I could find was a few blog posts from attendees of previous years. I plan to do some blogging during the event to share my experiences (good and bad).

p.s. thanks to those who invited me to have drinks/dinner while I’m staying in Bellevue. I’ll be responding to your emails in the next week. if you’re interested in meeting up, drop me a line.

The Selenium IDE (a plug-in for Firefox) allows you to record tests. A guy called “wishcow” published now a format which makes it possible to export those tests for the Selenium helper. Based on his format I wrote a format for creating test cases for the Selenium test suite. You can find it (plus the helper and the test suite) in the downloads section,

The installation is simple (you can find a graphical installation guide on “wishcow”’s blog):

• Open the Selenium IDE
• Select “Options”/”Options…”
• Switch to “Formats”
• Choose “Add”
• Define a name and copy&paste the format in the text area
• Click on “Ok” to save it

Happy testing :)

Even though I am not a design/usability specialist I will discuss the design process for a rather minor detail in an application.

I have one of those lists you will find in almost every application which lists the items the user entered. Now it should be possible to move these items to two different categories. How could this be solved?

The easiest solution would be to add two links to the end of each row. But how do you name those links? “Move to Category A” and “Move to Category B”? Hm, that takes too much space and it looks ugly if you have to repeat it on all rows.

The next idea is to use icons instead of text. But this causes a similar problem as above. How should the icons look so people understand them?

Another idea is to put a checkbox in front of each row and to have a select box with the possible actions at the top and/or the bottom of the list. The problem here is that the user has to click at least three times to move an item.

What about a drag and drop solution? Well, drag and drop is not very intuitive, and it is difficult to visualize that an object is draggable.

Maybe we could add a select box to the end of each row? Well, it is still two clicks for the user. Can we reduce it somehow to a one-click action?

We could add a link to the end of each row and then on a mouse over event we show the possible actions. So with only one click the user can move a list item to the desired category. With that I have found the solution for the problem described at the beginning of this post. Here the visualization of this idea which I called “expandable link”:

The first image shows simply a link, and the second shows what happens on a mouse over event on this link.

Up to now I didn’t test this solution in the wild so I cannot say how it will be accepted by the users, but if they are like me, they will find it cool ;-)

It appears that Seth Godin is catching on to the concept of Dialogue.

Seth writes, “Some organizations are good at listening. Some are good at talking. A few are even good at both.”

I’ve been spending a lot of time thinking about how I listen to clients, employees, friends, and family. All of our relationships are a series of conversations. Sometimes we can have healthy dialogue, sometimes we just fall victim to debate. (see Dialogue vs Debate)

If you’re really interested in Dialogue, I’d encourage you to review the technology of Dialogue... and check out the Dialogue-Driven Development project and introduce yourself.

There’s story in Primo Levi’s The Periodic Table (via, via) about a recipe for varnish that included a raw onion. Nobody at the varnish plant where he worked knew what its purpose was. It turned out that it had originally been used as a thermometer: if the onion fries, things were hot enough. Now, they had (and used) better thermometers, but they kept on throwing the onion in because that’s just what you did.

I think that web frameworks have a lot of onions in them. A lot of the design decisions that are unconsicously adopted by modern frameworks like Rails or Django were made 10 or 15 years ago. They were probably good decisions at the time, but we need to re-evaluate them now that we have new and better tools available to us.

That’s the thesis behind the Applied Web Heresies tutorial I’m giving at ETech later this month. It’s a follow up to the Web Heresies talk I gave at OSCON last July. Both of these talks are about Seaside, but they’re not about how or why you should run out and use Seaside yourself - there just aren’t that many prospective Smalltalkers out there. Instead, you might say they’re about Seaside’s recipe, and what new ingredients it gets to use after taking the bold step of chucking the onion into the compost pile. In the tutorial, I’m hoping that we’ll build some mini Seaside-style frameworks in Ruby, Python, and other dynamic languages. I don’t know how far we’ll get, but at least whatever we make will be onion-free.

As an appetizer, here are some things I think are onions: template systems, hidden fields, meaningful query parameters, and sessions stored in databases. Why? Because we have, but aren’t fully appreciating, these thermometers: CSS, RSS, fast CPUs with gigs of RAM, and smart load balancers. What new ingredients do we get to use? By far the spiciest of these is closures or blocks: it’s amazing how much pain they can take away once you’re committed to using them pervasively at the framework level.

I think it’ll be a fun tutorial, and I’m really looking forward to it. See you in San Diego.

10:41 <@mst> marcus: 
    $obj->result_source
        ->resultset
        ->search($obj->ident_condition)
        ->update({ id => $new_id })

On IBM’s developerWorks the second part of the series “Create an interactive production wiki using PHP” has been published. It deals with user registration and custom markup rendering.

I am not so happy with this part. First, it uses functions of the HTML helper which are deprecated since version 0.9.2 of CakePHP, like passwordTag() and submitTag() (you should use password() resp. submit() instead). And second, I think the rendering of the markup shouldn’t be done in the controller. It should be done in a component or a helper (depends on whether you look at it as business logic or presentation logic). The advantages:

• the code would be easier to test
• the controller would be easier to read
• the markup rendering could be reused

Anyway, here the links to the article: article (registration needed), PDF

Part 1

Since yesterday’s product toss went so quickly¹, how about another shot?

In the photo above you can see the my final project from my letterpress class (printed last night).

I designed this as a fake concert ad where most of the band names include some kind of typographical term². The first three people to correctly identify at least 8 of the 9 will receive a coupon for an episode of PeepCode and a PeepCode t-shirt shipped to their house at my expense (anywhere in the world).

Void where prohibited. The Topfunky Corp is not responsible for lost, misdirected, or SPAM-tagged email. Employees of the Topfunky Corp not eligible. Entries by people with either “Jacob” or “Harris” in their name will be checked twice to verify accuracy.

UPDATE! Congrats to Michele Finotto, Keith Frost, and Luke Redpath for being quick on the trigger and also having correct answers. They will be receiving a PeepCode t-shirt in the mail soon.

bastarda

A gothic script from France and Germany used in the 14th and 15th centuries. Was used for documents of minor value or importance.

beardline

The lower extent of descenders in letters like g, p, or y.

mutton

A measurement equal to the width of the letter “m.” Also called an “em space.”

nut

A measurement equal to the width of the letter “n.” Also called an “en space.”

hedera

A decorative character in the shape of an ivy leaf.

slug

A piece of lead or other metal used to make space between lines of text.

pilcrow

The paragraph sign. ¶

full bleed

The technique of printing past the edge of a page, or printing out to an area and then cutting the paper to a smaller dimension.

neitherhanded

Not technically a typographical term, but refers to typefaces that do not lean to the right or the left. Early typefaces were made to look as if they had been drawn by a right-handed person, but others abandon this and have a more upright appearance (for example, bodoni).

Thanks to everyone who entered, including Jacob Harris!

¹ Ten coupons in about 15 minutes. Honestly, I’m a little worried that people are stalking my blog so frequently that they notice within one minute of a new blog post.

² Most of the people in the class didn’t find this funny, which baffles me. How is “The Rusty Slug” not funny?

Programmers love to see benchmarks and statistics. Admit it! You love it as much as I do. Show us a table of figures or a chart and we go ga-ga.

Who cares that these “authoritative” benchmarks often measure incomplete implementations or fail to re-measure their data when presented with red flags such as the idea that Rails 1.2 is 2-4 times slower than 1.1.6. Or that most omit one of the most basic of statistical measurements.

Many of these are presented innocently and without the intent to deceive but they aren’t models for meaningful benchmarking. Most of the time you’re not looking for big numbers and shocking statistics, you just need to find out which implementation is faster.

If I fragment cache my tag cloud, will it really make the site any faster? Are memcached sessions across the network really any faster than ActiveRecord sessions?

Most of the time this means benchmarking your entire Rails stack: webserver, app server, Rails, database, filesystem. One of the best tools for benchmarking a full stack is httperf. It has a pretty good set of features and it gives you statistically useful information.

I’ve spent the last few weeks picking Zed Shaw’s brain and learning all I can about httperf. I’ve put all that information into the latest PeepCode. It starts with an episode on Page, Action, and Fragment Caching, but if you are already familiar with caching you can jump straight to the main course and view the httperf episode.

More and more I’m finding that the best way I can communicate is through a screencast, but here are a few tips that have helped me:

• You can’t do benchmarking without knowing some basic statistics. And no, understanding the concept of “average” isn’t enough! Learn about what standard deviation is and what it says about the data you pulled from your benchmarking run. No server performs at exactly 32.746 requests per second…there’s a range of error and if you don’t express your benchmark along with that range then you haven’t communicated anything. It isn’t very hard to understand and the benefit to your powers of evaluation will be huge. If nothing else, you’ll be able to properly criticize poorly executed benchmarks on other blogs! See also Zed’s rant.

• Learn how to read the output of your benchmarking tool of choice. Even ab gives you some results with standard deviation, but it’s not often used. For httperf, it’s the “Reply rate” line. Here are a few from separate runs against the same server running two kinds of software:

Reply rate [replies/s]: min 100.6 avg 101.0 max 101.4 stddev 0.6 (2 samples)
Reply rate [replies/s]: min 100.6 avg 100.7 max 100.8 stddev 0.1 (2 samples)
Reply rate [replies/s]: min 94.0 avg 96.4 max 98.8 stddev 3.4 (2 samples)
Reply rate [replies/s]: min 103.8 avg 104.4 max 105.0 stddev 0.9 (2 samples)

• Be a scientist. Running a benchmark should be done with the same care that a chemist measures a blood sample for a trace of a fatal disease. Quit all the other programs you have running. Use two separate computers so your benchmarking tool doesn’t compete with your web application for the CPU.

Here’s a script that will parse a text file full of “Reply rate” lines and give you a Gruff graph as seen above.

I’m traveling a bit in March. If you’re at any of these places in the next few weeks, find me and I’ll give you a PeepCode t-shirt (limited to availability):

• March 10-13: SXSW in Austin, Texas
• March 13: Seattle.rb lectures at the Northwest Film Forum at 7pm
• March 18-26: Kauai, Hawaii (Is there a Ruby brigade in Kauai?)
• March 27-29: Philly Emerging Tech Conference

If not, you can buy a PeepCode t-shirt at my Shopify store (USA only for the first set).

• Gregg Pollack on Page Caching
• PeepCode: Page, Action, and Fragment Caching
• PeepCode: Benchmarking with httperf

And a free episode for the first 10 people to figure out how to use this coupon code: PEEP-NUBY

(The coupons were fetched up snappily in about 15 minutes.)

Do you remember the domain model from a previous post? No? No problem, here it is again:

The next logical step on the way from the domain model to the Cake models would be to refine the domain model to a database diagram. I say “would be” as it is something I almost never do, especially not for small projects. For me it isn’t worth the additional effort as a database diagram doesn’t add much value if you know some basic rules (Cake conventions). And well, I don’t have found a free tool for this task which convinced me ;-)

So I will go on and create the tables manually. For this purpose I will create a create.sql file in app/config/sql.

The first rule is that table names are plural. So we can write the SQL statement for the table for the “User” class (I omit the other classes as it is the same for them):

CREATE TABLE users (
);

The second rule is that each table has a primary key field with the name “id”. So we can modify the script from above to:

CREATE TABLE users (
    id INT(11) NOT NULL AUTO_INCREMENT,
    PRIMARY KEY (id)
);

The third rule is optional, but you can add the fields “created” and “modified” to the table, which are later automatically populated by CakePHP:

CREATE TABLE users (
    id INT(11) NOT NULL AUTO_INCREMENT,
    created DATETIME,
    modified DATETIME,
    PRIMARY KEY (id)
);

The fourth rule affects 1:n relations: The “n” table must contain a field named “singular name of ‘1′ table” + “_id”. In our domain model the relation between User and Project is such a 1:n relation: one User can have many Projects. So we have to add the field “user_id” to the “projects” table:

CREATE TABLE projects (
    id INT(11) NOT NULL AUTO_INCREMENT,
    user_id INT(11) NOT NULL,
    created DATETIME,
    modified DATETIME,
    PRIMARY KEY (id)
);

The fifth rule affects n:n relations. Such relations cannot be mapped directly to the database, we have to introduce a join table. The name of this join table is “plural name of first ‘n’ table” + “_” + “plural name of second ‘n’ table” whereby the names are sorted alphabetically. In our domain model we have only one n:n relation, between User and Project. So the table name is “projects_users”. We also have to apply the fourth rule, as the relations between “projects” and “projects_users” resp. between “users” and “projects_users” are 1:n relations. And so we get:

CREATE TABLE projects_users (
    project_id INT(11) NOT NULL,
    user_id INT(11) NOT NULL
);

Now we can add the attributes from the conceptual classes as fields to the respective tables and write the drop statements. And we get:

CREATE TABLE users (
    id INT(11) NOT NULL AUTO_INCREMENT,
    created DATETIME,
	modified DATETIME,
    PRIMARY KEY (id)
);

CREATE TABLE projects (
    id INT(11) NOT NULL AUTO_INCREMENT,
    user_id INT(11) NOT NULL,
    created DATETIME,
    modified DATETIME,
    PRIMARY KEY (id)
);

CREATE TABLE messages (
    id INT(11) NOT NULL AUTO_INCREMENT,
    project_id INT(11) NOT NULL,
    title VARCHAR(255) NOT NULL,
    content TEXT NOT NULL,
    created DATETIME,
    modified DATETIME,
    PRIMARY KEY (id)
);

CREATE TABLE feeds (
    id INT(11) NOT NULL AUTO_INCREMENT,
    user_id INT(11) NOT NULL,
    url VARCHAR(255) NOT NULL,
    created DATETIME,
    modified DATETIME,
    PRIMARY KEY (id)
);

CREATE TABLE projects_users (
    project_id INT(11) NOT NULL,
    user_id INT(11) NOT NULL
);

And in app/config/sql/drop.sql:

DROP TABLE IF EXISTS users;
DROP TABLE IF EXISTS projects;
DROP TABLE IF EXISTS messages;
DROP TABLE IF EXISTS feeds;
DROP TABLE IF EXISTS projects_users;

To execute these SQL scripts I use a simple Ant script (app/config/sql/build.xml):

<?xml version="1.0"?>
<project name="n" default="default">
    <property name="driver" value="com.mysql.jdbc.Driver"></property>
    <property name="url" value="jdbc:mysql://localhost/n?characterEncoding=UTF-8"></property>
    <property name="user" value="root"></property>
    <property name="password" value=""></property>

    <target name="default">
        <sql driver="${driver}" password="${password}" url="${url}" userid="${user}" src="drop.sql" encoding="UTF-8"></sql>
        <sql driver="${driver}" password="${password}" url="${url}" userid="${user}" src="create.sql" encoding="UTF-8"></sql>
    </target>
</project>

After executing the Ant script, we are ready to bake the models. I will use the bake script (available in cake/scripts) to generate the User model, as I was asked to show how bake.php is used. I think it should be self-explanatory:

This will create the following model in app/models/user.php:

<?php
class User extends AppModel {
    var $name = 'User';

    //The Associations below have been created with all possible keys, those that are not needed can be removed
    var $hasMany = array(
        'Feed' => array('className' => 'Feed',
            'foreignKey' => 'user_id',
            'conditions' => '',
            'fields' => '',
            'order' => '',
            'limit' => '',
            'offset' => '',
            'dependent' => '',
            'exclusive' => '',
            'finderQuery' => '',
            'counterQuery' => ''),
        'Project' => array('className' => 'Project',
            'foreignKey' => 'user_id',
            'conditions' => '',
            'fields' => '',
            'order' => '',
            'limit' => '',
            'offset' => '',
            'dependent' => '',
            'exclusive' => '',
            'finderQuery' => '',
            'counterQuery' => ''),
    );

    var $hasAndBelongsToMany = array(
        'Project' => array('className' => 'Project',
            'joinTable' => 'projects_users',
            'foreignKey' => 'user_id',
            'associationForeignKey' => 'project_id',
            'conditions' => '',
            'fields' => '',
            'order' => '',
            'limit' => '',
            'offset' => '',
            'unique' => '',
            'finderQuery' => '',
            'deleteQuery' => '',
            'insertQuery' => ''),
    );
}
?>

It generates also a test case for the model in app/tests/cases/models/user.test.php:

<?php 

loadModel('User');

class UserTestCase extends UnitTestCase {
    var $object = null;

    function setUp() {
        $this->object = new User();
    }

    function tearDown() {
        unset($this->object);
    }

    /*
    function testMe() {
        $result = $this->object->doSomething();
        $expected = 1;
        $this->assertEqual($result, $expected);
    }
    */
}
?>

As you see, when using the bake script you have to answer many questions. That’s a bit of a pain when you want to bake multiple models. And if you don’t want to write tests you have to remove them (that’s at least what I do with files which are not used). These are the reasons I prefer to write the models manually.

Here are the other models (please notice that I omit the $name variable as I am a) using PHP5 and b) lazy):

// app/models/feed.php
<?php

class Feed extends AppModel {
    var $belongsTo = array('User');
}
?>

// app/models/project.php
<?php

class Project extends AppModel {
    var $hasMany = array('Message');
    var $hasAndBelongsToMany = array('User');
}
?>

// app/models/message.php
<?php

class Message extends AppModel {
    var $belongsTo = array('Project');
}
?>

To test whether we defined the associations correctly, we can create for all models the corresponding controllers. Here the UsersController (the other controllers are similar):

// app/controllers/users_controller.php
<?php

class UsersController extends AppController {
    var $scaffold;
}
?>

With that, we have something to play, we can add, edit, and remove records. But it isn’t very useful yet ;-)

That’s it for today.

(other articles from this series)

While reviewing some articles related to small business management, I came across the following post… titled, Note From Boss to Employees, by Michael Wade. As a young business owner, who only 16 months ago was working in his attic… to now trying to figure out how to run a company with over ten employees (and growing), posts like this remind me that we all have so much to learn. :-)

Here are a few that I appreciated…

“I may not have been given a huge amount of training before being named to a supervisory position. As a result, I’ve had to learn through trial and error. That’s not always bad. Many of my responsibilities can only be learned through practice.”

Yep… that’s me! The only difference is that I promoted myself instead of being promoted by someone else. I’m still not sure what I got myself into sometimes. ;-)

“I will make mistakes. Please give me the same understanding that you’d like me to give you when you blunder.”

This reminded me of a blog post from last year, titled, Avoiding the most common software development goofs, which points out that things like ignorance and stress are often to blame for mistakes in development. I feel like these are reasons for goofs in just about any environment, especially business. Let’s face it. We’re not perfect and we’re going to make a lot of mistakes. Once we’ve agreed on this, let’s take the next step and see what happens.

“If I do something dumb or am on the verge of doing so, please tell me. Don’t hint. Tell me.”

Perhaps this is a common problem for most small business owners. Are employees afraid to tell me that I’m doing something dumb?

“If either of us has a problem with the other’s performance, let’s talk about it.”

As they say, real friends will be honest with you about your faults. Not because they want to make you look bad, but because they care.

Each of the points that I have listed here are pointing to is… healthier Dialogue, which is always a challenge to accomplish… in any relationship… whether with clients, coworkers, bosses, or employees.

I’d like to add a few to this list.

• It’s easier to ask for forgiveness, than to ask for permission.
• I’m still trying to get the hang of this GTD stuff, so.. you might remind me if I forgot something.
• Ask yourself on a regular basis, “Am I having fun?” If not, make time for some.
• Please make fun of the boss! :-)

Months ago I implemented DBIx::Class::Storage::Statistics with the intent of making some sort of profiling tool. I finally got off my ass and did it. DBIx::Class::QueryLog should be on CPAN this weekend.

At $work we are replacing a legacy system with one based on Catalyst. One of the deliverables for this year is a new order entry application. Since our customer service folks are used to working in a terminal based system speed is of great concern to us.

So I installed DBIx::Class::QueryLog as the debugobj as described in it’s documentation, dropped it in the stash and added some code to our wrapper.tmpl:

[% IF querylog %]
      <div class="featurebox">
        <h3>Query Log Report</h3>
        [% SET total = querylog.time_elapsed | format('%0.6f') %]
        <div>Total SQL Time: [% total | format('%0.6f') %] seconds</div>
        [% SET qcount = querylog.count %]
        <div>Total Queries: [% qcount %]</div>
        [% IF qcount %]
        <div>Avg Statement Time: [% (querylog.time_elapsed / qcount) | format('%0.6f') %] seconds.</div>
        <div>
         <table class="table1">
          <thead>
           <tr>
            <th colspan="3">5 Slowest Queries</th>
           </tr>
          <

The first run yielded this:

Well. That select from users could use an index on username, eh?

Weee! That one disappeared. What are all these role selections? We use Catalyst::Plugin::Authorization::Roles but this looks fishy. We might could use an index on the role name but there are only 6 rows in that table. A bit more investigation finds a loop in our Root controller that iterates over a set of roles calling check_user_roles() to try and find out where we should redirect the user. So lets swap that out for creating an array of roles and using grep…

Kick ass! We are down to two measly queries. We reduced the number of queries by about 75% and decreased the time spent executing SQL by about 75% as well. These queries were being executed on every page load.

UPDATE:Yeah, the average statement time was broken during that. Oops.

If you use the form helper from CakePHP 1.2 to generate an input field, it automatically creates a label for the input field. So this snippet:

echo $form->input('Project/name');

will generate the following HTML code:

<div class="input">
    <label for="ProjectName">Name</label>
    <input name="data[Project][name]" type="text" value="" id="ProjectName" />
</div>

But sometimes you don’t want a label. How can you accomplish that? My first two attempts failed, the label “Name” was still shown:

// first attempt
echo $form->input('Project/name', array('label' => ''));
// second attempt
echo $form->input('Project/name', array('label' => null));

With the third attempt I was then successful, and the label disappeared:

echo $form->input('Project/name', array('label' => false));

In retrospect the solution is logical, but sometimes you don’t see the obvious solution ;-)

“Showing up on time …with a smile on your face is almost always more important than what you actually say or do.”—Seth Godin

overhead here...

OpenID allows you to use your own domain as OpenID and to delegate it for authentication purposes to an OpenID server by adding two link tags to the head section of a HTML page. In my case I use http://openid.42dh.com as OpenID and in the head section you will find:

<link rel="openid.server" href="http://www.myopenid.com/server" />
<link rel="openid.delegate" href="http://dh.myopenid.com" />

This approach comes with two potential problems:

• I cannot authenticate myself if my domain is down,
• and the same applies if the OpenID server is down

To the first problem I don’t have a solution yet, but for the second problem the solution is easy. Modify the snippet above and you can still authenticate with your OpenID by using a different OpenID server. It is just a bit cumbersome to login to your server and to do that change manually. So I wrote a very simple CakePHP application which allows you to switch the used OpenID server on-the-fly. It is one of those “15 minutes” projects where it is almost overkill to use CakePHP ;-)

You can find the application in the downloads section. The installation is simple, the zip contains a complete app folder (no database needed). You may have to modify app/webroot/index.php and to make the tmp folder writable, and, of course, you have to add the OpenID servers and delegates you want to use. They are defined in app/models/delegate.php. Now, to change the OpenID server you simply call example.com/change and a different OpenID server will be used.

That’s it.

OpenID will have to co-exist with regular user names and passwords for some time to come in most cases. So as developers we have to come up with good conventions on how to deal with this duality. To do that, it would help greatly if we were able to distinguish an OpenID from a regular user name.

Consider this flow:

With OpenID distinguishable from regular user names, you don't have to use an additional field to complicate the login or signup screen further.

It seems that there is already some support for the notion of specifying OpenIDs as complete URLs and not just their host names. Both Zoomr and Jyte explicitly encourage/require usage of complete URLs:

But there are definitely other cases where just the host name is used. So neither approach seems to have taken hold as a defacto standard. I'd recommend that we move in the direction of full URLs. And if your site only takes OpenID, then you could still reinforce that idea by having login be something like http:// [input field].

...overheard on an internal forum…

“My my passion for nifty server tricks will blow peoples minds”—Daniel Johnson

Hey folks,

here comes an example of my favorite "bug" that drives me insane on occasion:

It just got me again and caused me to debug Model::hasField, finally implementing my own version of it until I realized what an idiot I am ... ; ). What's your favourite?

-- Felix Geisendörfer aka the_undefined

Okay, this is a little overdue… but better late than never! ;-)

We’ve had several new people start with PLANET ARGON over the past few months. Some of them are blogging about their experience of working with Ruby on Rails and being a part of our team. I wanted to quickly introduce you to a few of them and their blogs, which I hope that you consider subscribing to.

For quite some time, we’ve been needing more design assistance, so late last year… we hired Chris Griffin, who moved here last year from Florida. He’s our new User Interface Designer and gets to work within the Rails environment everyday with the rest of us. It seems that Brian and Chris worked over the weekend to get his new blog up. Chris is self-proclaimed genius. I suggest that you keep an eye on his blog… because I’m sure it’s going to be a pretty active one. Chris joining our team marks a pivotal point in our teams evolution as we continue to place more emphasis in our Design and Development process on the User Experience.

• http://chriszgriffin.com/

Our newest hire is Graeme Nelson, who recently moved to Portland from Seattle. He just joined our Design and Development team and if you’ve been reading the Rails-related blogs, you might have seen his blog already. He’s been blogging a lot about using RSpec with Rails and other fun things. He’s been contracting with us since the start of the year and I’m really excited that he’s accepted a job offer and joined the team!

• http://blog.imperialdune.com/

Last… but not least is Gary Blessington. I believe that I first offered Gary a job with PLANET ARGON about 2 1/2 years ago when we were still focused on PHP/PostgreSQL…. but PHP apparently wasn’t enough of a catalyst. Gary and I previously worked together at Imark Communications several years ago, when I first started doing web development. He was the senior developer on the team and was an important mentor during my early days of developing in a professional environment. Late last year, he hung up his .NET tool belt to become our Design and Development Director. He started blogging earlier this year and is sharing his experience of switching from .NET to Ruby on Rails.

• http://garyblessington.us/.

I’ll introduce the others as they start blogging and such. :-)

The query() function of the model is sometimes very practical as it allows you to execute any SQL statement you want. But to me it seems it is often used in a “wrong” way (I have to include myself *g*), in a way which works but is not that clean. I am talking about calling query() from the controller:

$this->MyModel->query('Here comes the SQL statement');

Sure, following the Cake conventions this is a valid usage of query(), as the function is public. But it introduces database-related code to the controller, which is a violation of the MVC pattern.

I think a cleaner solution is to move the SQL statement to the model. So the snippet from above can be refactored to:

// in the model
function doSomething() {
    $this->query('Here comes the SQL statement');
}

// in the controller
$this->MyModel->doSomething();

Ok, this solution needs more code, but it comes with some additional advantages:

• it is easier to test
• it is more readable (at least if you give the function a better name than I did)
• the query can be re-used without copy & paste in other actions/controllers

What do you think about this approach?

Hey folks,

this is just a quick announcement that a completely new Drake has has been released by Mariano Iglesias. For those of you who don't remember: I used to have some fun with integrating CakePHP with other PHP applications around such as drupal which in term created a project called Drake. I only released a couple versions and by looking at Mariano documentation for Drakes none of them were as easy to set up.

Here is his announcement from the google group:

My fellow bakers,

After my experience with Jake, and thanks to Felix’s goodwill in giving the catchy name Drake for me to use, I’m pleased to announce the first beta release of Drake, a Drupal module that lets you execute your CakePHP applications inside Drupal.

Project home page: http://dev.sypad.com/projects/drake

Documentation: http://dev.sypad.com/projects/drake/documentation

Download: http://drupal.org/project/drake

Demo (Cheesecake Photoblog on Drupal 5.1): http://dev.sypad.com/projects/drake/demo/drake

Bake on, with Drake

-MI

So if you like to work with an existing system such as Drupal go ahead and give it a try!

-- Felix Geisendörfer aka the_undefined

I'm going to London with Mary for a long weekend in the beginning of March. We've both been there a couple of times and consumed the usual suspects of turismo. Skipping those, where should we go? Which restaurants must we dine? What plays, performances, or exhibitions must we see? Thanks, lazy web. You're the best.

I've loved the idea of OpenID ever since I sat down with the boys from Verisign and East Media to hear them talk about PiP and the Rails integration, but I never really got around to playing with it. "How big of a deal is having multiple logins really?", went the thinking. For a lot of people the answer is still "not a lot". But I'm starting to see the light.

Over a few hours today, I read up on and implemented OpenID logins for Highrise. That opened my eyes. Both to how easy it is to get working as an alternate login solution and, more importantly, how decent the flow actually is.

Yes, there's redirection to another site involved, but once you've saved the login for a certain site in your OpenID and you're logged into your provider, you don't even see the redirection. At first that might seem a little scary. Logging into a site without even entering a password? But then again, that's pretty much how I authenticate with my application servers around the world through SSHKeychain and on all sites that gives you Remember me?

There are certainly still concerns to be addressed. Chief among which is probably the phishing issue. But smart men are hard at work and I'm sure we'll be able to come up with something clever. I don't think this or any of the other current uncertainties are reason enough to hold back.

What we need is adoption. Luckily, OpenID seems to have already gotten the attention of plenty of enterprising startups and big behemoths. Most prominent in the latter category is AOL, which with a swing of its wand granted everyone with an AIM account an OpenID. It's as simple as http://openid.aol.com/<screenname>. The simplicity of that solution was part of what got me started today. There's a lot of power in not even having to signup for anything new. At least for getting off the ground.

Making it as easy as not to
So we got millions of people with an OpenID by virtue of their AIM account. Great. Now they just need a place or two to actually use it. That's where the technology comes in. The toolkits. The "making it as easy as not to". While there's already a fair number of generators out there for Rails on the subject, I'm generally not a big fan of generators as anything but learning tools or for setting up conventions. I'd much rather try to find a clever API that's so simple there's no need for boiler plating.

A very first stab at that with Rails that I came up with today is as follows (which I'll wrap up as a plugin shortly):

class SessionController  ApplicationController
  include OpenIdAuthentication
 
  def create
    if open_id?(params[:name])
      open_id_authentication(params[:name])
    else
      password_authentication(params[:name], params[:password])
    end
  end
 
 
  private
    def password_authentication(name, password)
      if @current_user =
          @account.users.find_by_name_and_password(name, password)
        successful_authentication
      else
        failed_authentication "Sorry, that username/password doesn't work"
      end
    end
 
    def open_id_authentication(identity_url)
      authenticate_with_open_id(identity_url) do |status, identity_url|
        case status
        when :missing
          failed_authentication "Sorry, the OpenID server couldn't be found"
 
        when :canceled
          failed_authentication "OpenID verification was canceled"
 
        when :failed
          failed_authentication "Sorry, the OpenID verification failed"
 
        when :successful
          if @current_user =
              @account.users.find_by_identity_url(identity_url)
            successful_authentication
          else
            failed_authentication "Sorry, no user by that identity URL exists"
          end
        end
      end
    end
end

The only extra pieces you need is to implement successful_authentication, which creates the session and redirects into the application, and failed_authentication, which redirects back to the login screen with an error flash message. params[:name] doubles as both a regular user name and as an OpenID. I distinguish between the two by whether it looks like a URL or not (starts with http). The underlying mechanics are delegated to the ruby-openid library.

It's most certainly still half-baked. It only works for the authentication part, not for the create the initial account and get additional attributes part. But it's a start and I'm excited.

I truly believe that OpenID stands a great shot at becoming real and useful even to people who would start yawning at the mere mention of the word "authentication". It won't happen overnight and it certainly won't happen unless we all dig in and make it happen. What's here today is more than good enough to get started. So less excuses, more implementions.

If that pitch still hasn't infected you with OpenID fevor, I recommend watching Scott Kveton's quick pitch. Then digesting Simon Willison's talk on OpenID and his Six cool things you can build with OpenID.

Then consider the fact that Firefox 3 will ship with native support for OpenID and that Microsoft is getting on board as well. Suddenly a future of OpenID everywhere starts looking mighty plausible.

In the past few years I’ve installed Rails applications on a few different hosts. I won’t recommend any single host for all situations, but here are the ones I’m currently using and what I think they are best at.

DISCLAIMER: This is not an attempt to get hosting referral money…I’ve already done that and ended up putting $1,500 toward a special event for the Seattle.rb. But most of these places have referral plans if you want to mention Topfunky when you signup.

• Ruby on Rails Podcast
• GeoffreyGrosenbach.com
• Topfunky.com (static)
• Many images, audio, and video files

I had a Dreamhost account before I learned Rails, so it seemed like the natural place to start installing apps. My first app took a few days to get up and running (but that was before Capistrano).

Dreamhost gives a huge amount of bandwidth. If you’re hosting a podcast or vidcast, this is the way to go (even just for the files). Their cheapest plan gives you 174 GB disk space and 1.74 TB of bandwidth.

However, I rarely login without seeing the load under 5 and it’s often over 15. Shared hosts are finely tuned to serve static files and PHP, but not Rails. At one point I had 5 different sites hosted there, but after a few months of flakiness I moved my blog elsewhere.

The Rails Podcast is still hosted there. It works well because the whole thing is page cached, which lets a shared host do what it does best…serve static files. If you’re running on a shared host I highly recommend using a third-party service like FeedBurner to serve your RSS or ATOM feed since that will constitute the majority of the hits to your site.

Here’s the .htaccess rewrite rule I use:

RewriteCond %{HTTP_USER_AGENT} !FeedBurner
RewriteRule ^podcast\.xml$ http://feeds.feedburner.com/rubyonrailspodcast [R,L]

• Topfunky.net Subversion repository

I jumped at the opportunity to get a lifetime account for only $400. I thought, “I’ll be set for the rest of my life and will never need to buy hosting again!”

Unfortunately, seemingly frequent server crashes and stringent resource enforcement made it quite hard to run a Rails app reliably. Yes, the app I deployed was using RMagick and probably had a higher-than-average memory usage. I eventually moved all my Rails sites back to Dreamhost (and later to virtual hosts).

I tried running lighttpd under proxy, but that was even worse. TextDrive bots kill any process that goes over a memory or CPU threshold, which will kill your lighttpd server. And, you are restricted from running applications that monitor processes and restart them.

I haven’t tried to run a Rails app there in the past year, so things may have improved.

It works well for Subversion hosting, which is probably all the benefit I will get out of my $400 lifetime account.

• Nuby on Rails blog
• The Online CEO
• Mint stats engine for a few other sites (runs under PHP)

I moved my blog to Rimuhosting after a few months of frustration at Dreamhost. It took a few days to install everything using Ezra’s instructions. I’ve since done a lot of tweaking to fine-tune everything.

It has been very reliable. Although customer support has been helpful and responsive, I haven’t had to use it much. It’s a virtual server, so you have root access but also need to be able to do basic sysadmin tasks: install software, monitor processes, setup log rotation, configure webservers.

A few months ago I installed Apache 2 and Mongrel, but the memory usage was a lot higher than lighty. I reverted to lighty and it has been running great ever since. For the most efficient memory usage, I’ve heard that lighty, FastCGI, and Postgres are the best (but nginx might be a good lightweight option, too).

I also run a few instances of PHP-fastcgi for Mint. This gives me a central place to run PHP without needing to install it on my other Rails-only servers.

The Production Log Analyzer tells me that my blog is serving between 40 and 80 requests per second. The load is usually under 0.1.

• PeepCode Screencasts

RailsMachine is the best Rails-specific host that I’ve used. The railsmachine gem does all the setup in a few easy commands. It took me a total of one hour from the time I got my SSH login info to the time that I loaded the first page of my fully-functional site. Even better, I know that everything is setup properly with startup scripts, svn, and room for more Rails apps.

Knowing that my site is running on a RAID 10 storage system helps me sleep better at night. Support staff are very quick to respond and have intimate knowledge of Rails. The founder wrote the mongrel_cluster gem.

RailsMachine has been super reliable. You can find lower prices elsewhere, but the quality is definitely worth the price, in my opinion. If you have a site with any kind of revenue, I would recommend hosting it at a high-quality, reliable host like RailsMachine.

My only criticism is that I like Debian flavors of Linux (including Ubuntu), but only CentOS is offered. However, this isn’t too much of a problem.

• Ruby on Rails Workshops

A few weeks ago I was frustrated with the flakiness of the Ruby on Rails Workshops Calendar which was running on Dreamhost. Although I could have stuffed it into one of my existing servers, I wanted to try out the inexpensive Slicehost with a non-critical site.

I used the deprec gem to install Apache, Ruby, Rails, Mongrel, and MySQL in only 45 minutes (screencast). I also wanted to have an extra non-critical server to experiment on (with nginx or other deployment strategies).

I was about to write this article last week, but the entire host was down for about an hour. Fortunately the support staff was very responsive and things were back up quickly.

If you are a full-time Rails developer, I think you owe it to yourself to learn how to operate a server. Spending $20/month on your own education will be worthwhile and will help you make mistakes on your own before making them on a paying client project. Slicehost would be a great environment for that kind of self-education.

• Capistrano Concepts
• Install Rails on Ubuntu (free)
• Page, Action, and Fragment Caching

Hey folks,

I was just taking a little trip through the CakePHP core code trying to wrap my head around Acl, Model behaviors and all sorts of stuff. While doing so I saw that the core code starts to be using the Set class more and more that was added a while ago. So far this has been a little dark spot for me in the core and from my previous quick looks at the class I've never been quite able to figure out what it's exact purpose was. Until now all I knew was "well it's probably some fancy array manipulation code that is somewhat obfuscated and undocumented". Oh boy, I wish I had spent more time on this earlier. It's probably one of coolest new features in 1.2 and nobody realizes it ; ).

So before starting to drool over it too much ahead of time, let's take a look at a simple example. You have an array of $users as it could have been returned from a findAll call to your User model:

What you really want however, is just a simple array containing all user 'name's: array('Felix', 'Bob', 'Jim'). Hmm. Up until today I'd probably have written some code like this to do it:

Simple enough, right? Not any more! Using the new Set class we can achieve the exact same outcome like this:

Doesn't blow you away yet? Well, let's look at another example. Let's say our User model as a hasMany associations to an Item model. Then we would get an array like this:

Now here is how I would have traditionally turned this into a 'User.name' => 'User.items' array:

But using the new Set class this is still pretty much a simple one-liner (split up in multiple lines so you don't have to scroll):

Both methods will output:

"But doesn't it cost more performance to loop through the array twice in the Set example?" I hear some of you cry. Yes it does. And? Have you built your application yet? Does it implement all features you are dreaming of? And most importantly: Do your web stats indicate you are going to have 1 million hits / day soon? If so go back into your code and remove the Set example with the less succinct foreach alternative. If not, listen to Chris Hartjes who's motto for 2007 is Just Build It, Damnit!.

Anyway, here comes my last fun thing to do with Set::extract - parsing an RSS feed for all post titles. For my example I'll use the new XML class in Cake 1.2. Right now Set::extract only supports arrays but hopefully it will either natively support Xml objects at some point, or the Xml class get it's own extract function. For now I've written a little function that can turn an Xml instance into an array that looks like this:

So now let's assume we would want to extract all post titles from my feed: http://feeds.feedburner.com/thinkingphp we could leverage the Set class to make our code as succinct as:

Which will give you a $postTitles array like this:

Now that's beauty right there and a good way to end this post ; ). Take a look at the Set classes source to find out about some other cool methods it has, but to me this is by far the coolest.

-- Felix Geisendörfer aka the_undefined

Two upcoming events may be of great interest for symfony fans.

The French PHP User association (AFUP) organizes a conference about symfony 1.0 in Paris. The event will take place on March 6 at 8pm at Espace FIAP - 30 rue Cabanis - 75014 Paris. Fabien Potencier will be the speaker, and he'll expose the benefits of using symfony in a professional context.

Also, the PHP Quebec Conference features two sessions about symfony, one in English and one in French. Once again, you'll have the pleasure to appreciate Fabien's English accent and learn to build maintainable and upgradeable PHP applications with symfony.

I stumbled upon a link to a fellow doing "full motion video" on an old 8088 (the link is probably about a year old, but, whatever). I watched the video and thought it looked an awful lot like ANSIMation. There was related link to another fellow that reversed engineered the file format.

Each cell is represented by an attribute byte (defines foreground color, background color, and flashing) and the actual extended ASCII character (0..255).

This is exactly how an XBin (which basically a fancy ANSI-like format) is stored.

I peeked at his code to get an idea of the palette, and some of the details on frame size. I came up with the following "frame grabber" code. It takes a data file as the first input (extract the data file from the original 8088 Corruption package), and a frame number (0 being the first frame) as the second parameter (it'll pick a random frame if ommitted). It's a little long since i've embedded the 8x8 font at the bottom of the script. It uses GD to spit out a png image.

Here's a sample of the output of perl grab.pl 8088_COR.DAT 1085 > frame_1085.png

use strict;
use warnings;

use GD;
use IO::File;
use File::Temp ();
use MIME::Base64 ();

my $VIDEO_FRAME_WIDTH  = 40;
my $VIDEO_FRAME_HEIGHT = 25;
my $VIDEO_FRAME_SIZE   = $VIDEO_FRAME_WIDTH * $VIDEO_FRAME_HEIGHT * 2;
my $AUDIO_FRAME_SIZE   = 735;
my $TOTAL_FRAME_SIZE   = $VIDEO_FRAME_SIZE + $AUDIO_FRAME_SIZE;

my @palette = (
    0x000000, 0x0000AA, 0x00AA00, 0x00AAAA,
    0xAA0000, 0xAA00AA, 0xAA5500, 0xAAAAAA,
    0x555555, 0x5555FF, 0x55FF55, 0x55FFFF,
    0xFF5555, 0xFF55FF, 0xFFFF55, 0xFFFFFF
);

my $dat = $ARGV[ 0 ] || die 'No data file specified';
die 'File not found' unless -e $dat;

my $filesize = -s $dat;
die 'Invalid file size' unless $filesize % $TOTAL_FRAME_SIZE == 0;

my $frames = $filesize / $TOTAL_FRAME_SIZE;
my $image  = GD::Image->new( $VIDEO_FRAME_WIDTH * 8, $VIDEO_FRAME_HEIGHT * 8 );
my @colors = map { $image->colorAllocate( ( $_ & 0xFF0000 ) >> 16, ( $_ & 0x00FF00 ) >> 8, $_ & 0x0000FF ) } @palette;
my $font   = get_gd_font();

my $frame = $ARGV[ 1 ] || int( rand( $frames ) );
my $file  = IO::File->new( $dat );
my( $buffer );

$file->binmode;
$file->seek( $frame * $TOTAL_FRAME_SIZE, 0 );
$file->read( $buffer, $VIDEO_FRAME_SIZE );
$file->close;

render_frame( $buffer );

sub render_frame {
    my( $buffer ) = @_;
    my @frame     = unpack( 'C*', $buffer );
    my $frame_idx = 0;

    for my $y ( 0..$VIDEO_FRAME_HEIGHT - 1 ) {
        for my $x ( 0..$VIDEO_FRAME_WIDTH - 1 ) {
            my( $idx, $attr ) = @frame[ $frame_idx++..$frame_idx++ ];

            my $scale_x = $x * 8;
            my $scale_y = $y * 8;
            $image->filledRectangle( $scale_x, $scale_y, $scale_x + 8, $scale_y + 8, $colors[ $attr >> 4 ] );
            $image->string( $font, $scale_x, $scale_y, chr( $idx ), $colors[ $attr & 0x0F ] );
        }
    }

    print $image->png;
}

sub get_gd_font {
    my $data = MIME::Base64::decode_base64( do { local $/; <DATA> } );
    my $temp = File::Temp->new;

    binmode( $temp );
    print $temp $data;
    close $temp;

    return GD::Font->load( $temp->filename );
}

__DATA__
AAEAAAAAAAAIAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEBAQEBAAEAAAAAAAABAQABAAABAAE BAAAAAAAAAQEA
AQEBAQABAQAAAQEAAAEBAAAAAAAAAQABAQEBAQEAAAEBAQEBAQABAQEBAQEBAQEBA AEBAAEBAQEB
AQEBAQEBAQAAAAABAQEBAQAAAQEBAQEBAQEBAQEAAQEBAQEBAAABAQABAQAAAQEBAQE BAQABAQEB
AQEBAAEBAQEBAQEAAAEBAQEBAAAAAAEBAQAAAAAAAAEAAAAAAAAAAAAAAAAAAAABAAAAA AAAAQEB
AAAAAAEBAQEBAAABAQEBAQEBAAABAQEBAQAAAAABAQEAAAAAAAABAAAAAAAAAAAAAAAAAAA BAQEA
AAAAAQEBAQEAAAAAAQEBAAAAAQEBAQEBAQABAQEBAQEBAAEBAAEAAQEAAAAAAQAAAAAAAAEBA QAA
AAAAAAEAAAAAAAABAQEAAAAAAQEBAQEAAAEBAQEBAQEAAQEBAQEBAQAAAQEBAQEAAAAAAAEAAAA A
AAABAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEAAAAAAAEBAQEAAAAAAQEBAQAAAAAAAQEAAAAA
AAAAAAAAAAAAAAAAAAAAAQEBAQEBAQEBAQEBAQEBAQEBAQAAAQEBAQEAAAAAAQEBAQAAAAABAQEB
A QAAAQEBAQEBAQEBAQEBAQEBAQEBAQAAAAAAAAAAAAABAQEBAAAAAQEAAAEBAAABAAAAAAEAAAEA
AAA AAQAAAQEAAAEBAAAAAQEBAQAAAAAAAAAAAAABAQEBAQEBAQEBAAAAAAEBAQAAAQEAAAEBAAEB
AQEAA QEAAQEBAQABAQAAAQEAAAEBAQAAAAABAQEBAQEBAQEBAAAAAAEBAQEAAAAAAAEBAQAAAAAB
AQEBAAE BAQEBAAEBAQAAAQEAAAEBAAABAQAAAQEAAAEBAAAAAQEBAQAAAAAAAQEBAQAAAAEBAAAB
AQAAAQEAA AEBAAABAQAAAQEAAAABAQEBAAAAAAABAQAAAAABAQEBAQEAAAAAAQEAAAAAAAEBAQEB
AQAAAQEAAAE BAAABAQEBAQEAAAEBAAAAAAAAAQEAAAAAAAEBAQAAAAABAQEBAAAAAAEBAQAAAAAA
AAEBAQEBAQEAA QEAAAABAQABAQEBAQEBAAEBAAAAAQEAAQEAAAABAQABAQAAAQEBAQEBAAABAQAB
AQAAAAAAAAAAAAE BAAAAAQEAAQEAAQEAAAEBAQEAAAEBAQAAAQEBAQEBAAABAQEAAAEBAQEAAAEB
AAEBAAEBAAAAAQEAA AABAAAAAAAAAAEBAQAAAAAAAQEBAQEAAAABAQEBAQEBAAEBAQEBAAAAAQEB
AAAAAAABAAAAAAAAAAA AAAAAAAAAAAAAAAAAAQAAAAAAAQEBAAAAAQEBAQEAAQEBAQEBAQAAAAEB
AQEBAAAAAAABAQEAAAAAA AAAAQAAAAAAAAAAAAAAAAEBAAAAAAABAQEBAAAAAQEBAQEBAAAAAAEB
AAAAAAAAAQEAAAAAAQEBAQE BAAAAAQEBAQAAAAAAAQEAAAAAAQEAAAEBAAABAQAAAQEAAAEBAAAB
AQAAAQEAAAEBAAABAQAAAQEAA AAAAAAAAAAAAQEAAAEBAAAAAAAAAAAAAAEBAQEBAQEBAQABAQAB
AQEBAAEBAAEBAAEBAQEAAQEAAAA BAQABAQAAAAEBAAEBAAAAAQEAAQEAAAAAAAAAAAAAAQEBAQEA
AAEBAAAAAAEAAAEBAQEAAAABAQAAA QEAAAEBAAABAQAAAAEBAQEAAAEAAAAAAQEAAAEBAQEBAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAABAQEBAQEAAAEBAQEBAQAAAQEBAQEBAAAA
AAAAAAAAAAAAAQEAAAAAAAEBAQEAAAABA QEBAQEAAAAAAQEAAAAAAQEBAQEBAAAAAQEBAQAAAAAA
AQEAAAABAQEBAQEBAQAAAAEBAAAAAAABAQE BAAAAAQEBAQEBAAAAAAEBAAAAAAAAAQEAAAAAAAAB
AQAAAAAAAAEBAAAAAAAAAAAAAAAAAAABAQAAA AAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAABAQEB
AQEAAAABAQEBAAAAAAABAQAAAAAAAAAAAAAAAAA AAAAAAAAAAAABAQAAAAAAAAABAQAAAQEBAQEB
AQAAAAAAAQEAAAAAAAEBAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAABAQAAAAAAAQEAAAAA
AAEBAQEBAQEAAAEBAAAAAAAAAAEBAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEBAQEBAQAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAEAAAEAAAABAQAAAQEAAQEBAQEBAQEAAQEAAAEBAAAAAQA AAQAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAQEAAAAAAAEBAQEAAAABAQEBAQEAAQEBAQEBA QEBAQEBAQEBAQAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAEBAQEBAQEBAQEBAQEBAQEAAQEBAQEBAAA AAQEBAQAAAAAAAQEAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAAAAAAABAQEBAAAAAAEBAQE AAAAAAAEBAAAAAAAAAQEA
AAAAAAAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAQEAAAEBAAABAQAAAQEAA AABAAABAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAAEBAAAAAQE AAQEAAAEBAQEBAQEA
AAEBAAEBAAABAQEBAQEBAAABAQABAQAAAAEBAAEBAAAAAAAAAAAAAAAAAAEBA AAAAAABAQEBAQAA
AQEAAAAAAAAAAQEBAQAAAAAAAAABAQAAAQEBAQEAAAAAAAEBAAAAAAAAAAAAAAA AAAAAAAAAAAEB
AAAAAQEAAQEAAAEBAAAAAAABAQAAAAAAAQEAAAAAAAEBAAABAQABAQAAAAEBAAAAA AAAAAAAAAAB
AQEAAAAAAQEAAQEAAAAAAQEBAAAAAAEBAQABAQABAQABAQEAAAEBAAABAQAAAAEBAQA BAQAAAAAA
AAAAAAAAAAEBAAAAAAAAAQEAAAAAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAA
AAAAAAAAAAAAAAAAAAAAAQEAAAAAAAEBAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAA AAQEA
AAAAAAAAAQEAAAAAAAAAAAAAAAABAQAAAAAAAAABAQAAAAAAAAABAQAAAAAAAAEBAAAAAAAAA QEA
AAAAAAEBAAAAAAABAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAAABAQAAAAEBAQEAAAEBAQEBAQE B
AAABAQEBAAAAAQEAAAEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAAAAAAAAAQEAAAAA
AQEBAQEBAAAAAAEBAAAAAAAAAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
A AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAAAAAAAAAQEAAAAAAAEBAAAAAAAAAAAAAAAAAAAA
AAA AAAAAAAAAAAAAAAABAQEBAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEAAAAAAAABAQAAAAAAAAAA
AAAAAAA AAAABAQAAAAAAAQEAAAAAAAEBAAAAAAABAQAAAAAAAQEAAAAAAAEBAAAAAAAAAQAAAAAA
AAAAAAAAA AAAAAAAAQEBAAAAAAEBAAEBAAABAQAAAAEBAAEBAAEAAQEAAQEAAAABAQAAAQEAAQEA
AAAAAQEBAAA AAAAAAAAAAAAAAAABAQAAAAAAAQEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAA
AAAAAQEAAAAAA QEBAQEBAAAAAAAAAAAAAAEBAQEBAAABAQAAAAEBAAAAAAAAAQEAAAAAAQEBAAAA
AAEBAAAAAAABAQA AAQEAAQEBAQEBAQAAAAAAAAAAAAABAQEBAQAAAQEAAAABAQAAAAAAAAEBAAAA
AQEBAQAAAAAAAAABA QABAQAAAAEBAAABAQEBAQAAAAAAAAAAAAAAAAABAQEAAAAAAQEBAQAAAAEB
AAEBAAABAQAAAQEAAAE BAQEBAQEAAAAAAAEBAAAAAAABAQEBAAAAAAAAAAAAAQEBAQEBAQABAQAA
AAAAAAEBAAAAAAAAAQEBA QEBAAAAAAAAAAEBAAEBAAAAAQEAAAEBAQEBAAAAAAAAAAAAAAAAAQEB
AAAAAAEBAAAAAAABAQAAAAA AAAEBAQEBAQAAAQEAAAABAQABAQAAAAEBAAABAQEBAQAAAAAAAAAA
AAABAQEBAQEBAAEBAAAAAQEAA AAAAAEBAAAAAAABAQAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAA
AAAAAAAAAAAAAAEBAQEBAAABAQA AAAEBAAEBAAAAAQEAAAEBAQEBAAABAQAAAAEBAAEBAAAAAQEA
AAEBAQEBAAAAAAAAAAAAAAABAQEBA QAAAQEAAAABAQABAQAAAAEBAAABAQEBAQEAAAAAAAABAQAA
AAAAAQEAAAABAQEBAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAEBAAAAAAAAAQEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAQEAAAAAAAABAQAAAAAAA AAAAAAAAAAAAAAAAAAAAAABAQAAAAAAAAEBAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAEBAAAAAAAAAQE AAAAAAAEBAAAAAAAAAAAAAQEAAAAAAAEBAAAAAAAB
AQAAAAAAAQEAAAAAAAAAAQEAAAAAAAAAAQEAA AAAAAAAAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAEBAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAE BAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAEBAAAA
AAAAAAEBAAAAAAAAAAEBAAAAAAAAAAEBAAAAAAABA QAAAAAAAQEAAAAAAAEBAAAAAAAAAAAAAAAA
AAABAQEBAQAAAQEAAAABAQAAAAAAAQEAAAAAAAEBAAA AAAAAAQEAAAAAAAAAAAAAAAAAAAEBAAAA
AAAAAAAAAAAAAQEBAQEAAAEBAAAAAQEAAQEAAQEBAQABA QABAQEBAAEBAAEBAQEAAQEAAAAAAAAA
AQEBAQAAAAAAAAAAAAAAAAABAQEAAAAAAQEAAQEAAAEBAAA AAQEAAQEBAQEBAQABAQAAAAEBAAEB
AAAAAQEAAQEAAAABAQAAAAAAAAAAAAEBAQEBAQAAAAEBAAABA QAAAQEAAAEBAAABAQEBAQAAAAEB
AAABAQAAAQEAAAEBAAEBAQEBAQAAAAAAAAAAAAAAAAEBAQEAAAA BAQAAAQEAAQEAAAAAAAABAQAA
AAAAAAEBAAAAAAAAAAEBAAABAQAAAAEBAQEAAAAAAAAAAAAAAQEBA QEAAAAAAQEAAQEAAAABAQAA
AQEAAAEBAAABAQAAAQEAAAEBAAABAQABAQAAAQEBAQEAAAAAAAAAAAA AAAEBAQEBAQEAAAEBAAAA
AQAAAQEAAQAAAAABAQEBAAAAAAEBAAEAAAAAAQEAAAABAAEBAQEBAQEAA AAAAAAAAAABAQEBAQEB
AAABAQAAAAEAAAEBAAEAAAAAAQEBAQAAAAABAQABAAAAAAEBAAAAAAABAQE BAAAAAAAAAAAAAAAA
AAABAQEBAAAAAQEAAAEBAAEBAAAAAAAAAQEAAAAAAAABAQAAAQEBAAABAQAAA QEAAAABAQEAAQAA
AAAAAAAAAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAQEBAQEAAQEAAAABAQA BAQAAAAEBAAEB
AAAAAQEAAAAAAAAAAAAAAAEBAQEAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAA AEBAAAAAAAA
AQEAAAAAAAEBAQEAAAAAAAAAAAAAAAAAAQEBAQAAAAAAAQEAAAAAAAABAQAAAAAAAAE BAAABAQAA
AQEAAAEBAAABAQAAAAEBAQEAAAAAAAAAAAAAAAEBAQAAAQEAAAEBAAABAQAAAQEAAQEAA AABAQEB
AAAAAAEBAAEBAAAAAQEAAAEBAAEBAQAAAQEAAAAAAAAAAAABAQEBAAAAAAABAQAAAAAAAAE BAAAA
AAAAAQEAAAAAAAABAQAAAAEAAAEBAAABAQABAQEBAQEBAAAAAAAAAAAAAQEAAAABAQABAQEAA QEB
AAEBAQEBAQEAAQEBAQEBAQABAQABAAEBAAEBAAAAAQEAAQEAAAABAQAAAAAAAAAAAAEBAAAAAQE A
AQEBAAABAQABAQEBAAEBAAEBAAEBAQEAAQEAAAEBAQABAQAAAAEBAAEBAAAAAQEAAAAAAAAAAAAA
AQEBAQEAAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQAAAQEBAQEAAAAA
A AAAAAAAAQEBAQEBAAAAAQEAAAEBAAABAQAAAQEAAAEBAQEBAAAAAQEAAAAAAAABAQAAAAAAAQEB
AQA AAAAAAAAAAAAAAAABAQEBAQAAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAA
AQEBA AABAQEBAQAAAAAAAAEBAQABAQEBAQEAAAABAQAAAQEAAAEBAAABAQAAAQEBAQEAAAABAQAB
AQAAAAE BAAABAQABAQEAAAEBAAAAAAAAAAAAAAABAQEBAAAAAQEAAAEBAAAAAQEAAAAAAAAAAQEA
AAAAAAAAA QEAAAABAQAAAQEAAAABAQEBAAAAAAAAAAAAAAABAQEBAQEAAAEBAQEBAQAAAQABAQAB
AAAAAAEBAAA AAAAAAQEAAAAAAAABAQAAAAAAAQEBAQAAAAAAAAAAAAABAQAAAAEBAAEBAAAAAQEA
AQEAAAABAQABA QAAAAEBAAEBAAAAAQEAAQEAAAABAQAAAQEBAQEAAAAAAAAAAAAAAQEAAAABAQAB
AQAAAAEBAAEBAAA AAQEAAQEAAAABAQABAQAAAAEBAAABAQABAQAAAAABAQEAAAAAAAAAAAAAAAEB
AAAAAQEAAQEAAAABA QABAQAAAAEBAAEBAAEAAQEAAQEAAQABAQABAQEBAQEBAAABAQABAQAAAAAA
AAAAAAABAQAAAAEBAAE BAAAAAQEAAAEBAAEBAAAAAAEBAQAAAAABAQABAQAAAQEAAAABAQABAQAA
AAEBAAAAAAAAAAAAAAEBA AABAQAAAQEAAAEBAAABAQAAAQEAAAABAQEBAAAAAAABAQAAAAAAAAEB
AAAAAAABAQEBAAAAAAAAAAA AAAEBAQEBAQEAAQEAAAABAQABAAAAAQEAAAAAAAEBAAAAAAABAQAA
AQAAAQEAAAEBAAEBAQEBAQEAA AAAAAAAAAAAAAEBAQEAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAA
AAAAAQEAAAAAAAABAQAAAAAAAAE BAQEAAAAAAAAAAAAAAQEAAAAAAAAAAQEAAAAAAAAAAQEAAAAA
AAAAAQEAAAAAAAAAAQEAAAAAAAAAA QEAAAAAAAAAAQAAAAAAAAAAAAAAAQEBAQAAAAAAAAEBAAAA
AAAAAQEAAAAAAAABAQAAAAAAAAEBAAA AAAAAAQEAAAAAAQEBAQAAAAAAAAAAAAAAAAABAAAAAAAA
AQEBAAAAAAEBAAEBAAABAQAAAAEBAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQEB
AQEBAQAAAQEAAAAAAAAAAQEAAAAAAAAAAQEAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAE BAQEAAAAAAAAAAQEAAAABAQEBAQAAAQEAAAEB
AAAAAQEBAAEBAAAAAAAAAAAAAQEBAAAAAAAAAQEAA AAAAAABAQEBAQAAAAEBAAABAQAAAQEAAAEB
AAABAQAAAQEAAQEAAQEBAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAQEBAQEAAAEBAAAAAQEA
AQEAAAAAAAABAQAAAAEBAAABAQEBAQAAAAAAAAAAAAAAA AABAQEAAAAAAAABAQAAAAEBAQEBAAAB
AQAAAQEAAAEBAAABAQAAAQEAAAEBAAAAAQEBAAEBAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAB
AQEBAQAAAQEAAAABAQABAQEBAQEBAAEBAAAAAAAAAAEBAQEBA AAAAAAAAAAAAAAAAQEBAQAAAAEB
AAABAQAAAQEAAAAAAAEBAQEBAAAAAAEBAAAAAAAAAQEAAAAAAAE BAQEAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAEBAQABAQABAQAAAQEAAAEBAAABAQAAAAEBA QEBAAAAAAAAAQEAAAEBAQEB
AAAAAQEBAAAAAAAAAQEAAAAAAAABAQABAQAAAAEBAQABAQAAAQEAAAE BAAABAQAAAQEAAQEBAAAB
AQAAAAAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAEBAQAAAAAAAAEBAAAAA AAAAQEAAAAAAAABAQAA
AAAAAQEBAQAAAAAAAAAAAAAAAAAAAAEBAAAAAAAAAAAAAAAAAAABAQAAAAA AAAEBAAAAAAAAAQEA
AAEBAAABAQAAAQEAAAEBAAAAAQEBAQAAAQEBAAAAAAAAAQEAAAAAAAABAQAAA QEAAAEBAAEBAAAA
AQEBAQAAAAABAQABAQAAAQEBAAABAQAAAAAAAAAAAAAAAQEBAAAAAAAAAQEAAAA AAAABAQAAAAAA
AAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAQEB
AAEBAAABAQEBAQEBAAEBAAEAAQEAAQEAAQABAQABAQABAAEBAAAAAAAAAAAAAAAAAAA AAAAAAAAA
AAAAAAEBAAEBAQAAAAEBAAABAQAAAQEAAAEBAAABAQAAAQEAAAEBAAABAQAAAAAAAAAAA AAAAAAA
AAAAAAAAAAAAAAAAAQEBAQEAAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAABAQEBAQAAAAA AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAQEAAQEBAAAAAQEAAAEBAAABAQAAAQEAAAEBAQEBAAAAAQEAA AAA
AAEBAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQEAAQEAAQEAAAEBAAABAQAAAQEAAAABAQEBAQA A
AAAAAAEBAAAAAAABAQEBAAAAAAAAAAAAAAAAAAAAAAABAQABAQEAAAABAQEAAQEAAAEBAAAAAAAA
AQEAAAAAAAEBAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQEBAQABAQAAAAAAAAAB
A QEBAQAAAAAAAAABAQABAQEBAQEAAAAAAAAAAAAAAAABAQAAAAAAAAEBAAAAAAEBAQEBAQAAAAAB
AQA AAAAAAAEBAAAAAAAAAQEAAQEAAAAAAQEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQAA
AQEAA AEBAAABAQAAAQEAAAEBAAABAQAAAQEAAAABAQEAAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAQE AAAABAQABAQAAAAEBAAEBAAAAAQEAAAEBAAEBAAAAAAEBAQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAA AAAAAEBAAAAAQEAAQEAAQABAQABAQABAAEBAAEBAQEBAQEAAAEBAAEBAAAAAAAAAAAA
AAAAAAAAAAA AAAAAAAAAAAABAQAAAAEBAAABAQABAQAAAAABAQEAAAAAAQEAAQEAAAEBAAAAAQEA
AAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAAEBAQEBAQAA
AAAAAAEBAAEBAQE BAQAAAAAAAAAAAAAAAAAAAAAAAAABAQEBAQEAAAEAAAEBAAAAAAABAQAAAAAA
AQEAAAEAAAEBAQEBA QAAAAAAAAAAAAAAAAABAQEAAAAAAQEAAAAAAAABAQAAAAABAQEAAAAAAAAA
AQEAAAAAAAABAQAAAAA AAAABAQEAAAAAAAAAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAAB
AQAAAAAAAAEBAAAAAAAAA QEAAAAAAAABAQAAAAAAAAAAAAAAAAEBAQAAAAAAAAABAQAAAAAAAAEB
AAAAAAAAAAEBAQAAAAABAQA AAAAAAAEBAAAAAAEBAQAAAAAAAAAAAAAAAAABAQEAAQEAAQEAAQEB
AAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAEAAAAAAAABAQEAAAAAAQE AAQEAAAEBAAAAAQEAAQEAAAABAQABAQEBAQEBAAAAAAAAAAAA
AAEBAQEBAAABAQAAAAEBAAEBAAAAA AAAAQEAAAAAAAABAQAAAAEBAAABAQEBAQAAAAAAAAEBAAAA
AQEBAQAAAAEBAAABAQAAAAAAAAAAAAA BAQAAAQEAAAEBAAABAQAAAQEAAAEBAAABAQAAAQEAAAAB
AQEAAQEAAAAAAAAAAAAAAAAAAQEAAAAAA AEBAAAAAAEBAQEBAAABAQAAAAEBAAEBAQEBAQEAAQEA
AAAAAAAAAQEBAQEAAAAAAAAAAAAAAAEBAQE BAAABAAAAAAABAAABAQEBAAAAAAAAAAEBAAAAAQEB
AQEAAAEBAAABAQAAAAEBAQABAQAAAAAAAAAAA AEBAAAAAQEAAAAAAAAAAAAAAQEBAQAAAAAAAAAB
AQAAAAEBAQEBAAABAQAAAQEAAAABAQEAAQEAAAA AAAAAAAAAAAEBAAAAAAAAAAEBAAAAAAEBAQEA
AAAAAAAAAQEAAAABAQEBAQAAAQEAAAEBAAAAAQEBA AEBAAAAAAAAAAAAAAABAQAAAAAAAAEBAAAA
AAABAQEBAAAAAAAAAAEBAAAAAQEBAQEAAAEBAAABAQA AAAEBAQABAQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAQEBAQEBAAEBAAAAAAAAAQEAAAAAAAAAA QEBAQEBAAAAAAABAQAAAAABAQEAAAAA
AQEBAQEAAAEAAAAAAAEAAAEBAQEBAAABAQAAAAEBAAEBAQE BAQEAAQEAAAAAAAAAAQEBAQEAAAAA
AAAAAAAAAQEAAAABAQAAAAAAAAAAAAABAQEBAQAAAQEAAAABA QABAQEBAQEBAAEBAAAAAAAAAAEB
AQEBAAAAAAAAAAAAAAAAAQEAAAAAAAAAAQEAAAAAAQEBAQEAAAE BAAAAAQEAAQEBAQEBAQABAQAA
AAAAAAABAQEBAQAAAAAAAAAAAAAAAQEAAAEBAAAAAAAAAAAAAAABA QEAAAAAAAABAQAAAAAAAAEB
AAAAAAAAAQEAAAAAAAEBAQEAAAAAAAAAAAAAAAEBAQEBAAABAAAAAAA BAAAAAQEBAAAAAAAAAQEA
AAAAAAABAQAAAAAAAAEBAAAAAAABAQEBAAAAAAAAAAAAAAAAAQEAAAAAA AAAAQEAAAAAAAAAAAAA
AAAAAQEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAQEBAQAAAAAAAAAAAAABAQA AAAEBAAAAAQEBAAAA
AAEBAAEBAAABAQAAAAEBAAEBAQEBAQEAAQEAAAABAQABAQAAAAEBAAAAAAAAA AAAAAABAQEAAAAA
AQEAAQEAAAABAQEBAQAAAQEAAAABAQABAQEBAQEBAAEBAAAAAQEAAQEAAAABAQA AAAAAAAAAAAAA
AAEBAAAAAAABAQAAAAABAQEBAQEBAAEBAAAAAAAAAQEBAQEAAAABAQAAAAAAAAEBA QEBAQEAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQEBAQAAAAABAQAAAAABAQEBAQEAAQEAAQE AAAAAAQEB
AQEBAAAAAAAAAAAAAAABAQEBAQAAAQEAAQEAAAEBAAABAQAAAQEBAQEBAQABAQAAAQEAA AEBAAAB
AQAAAQEAAAEBAQAAAAAAAAAAAAABAQEBAQAAAQAAAAAAAQAAAQEBAQEAAAEBAAAAAQEAAQE AAAAB
AQABAQAAAAEBAAABAQEBAQAAAAAAAAAAAAABAQAAAAEBAAAAAAAAAAAAAAEBAQEBAAABAQAAA AEB
AAEBAAAAAQEAAQEAAAABAQAAAQEBAQEAAAAAAAAAAAAAAAABAQAAAAAAAAABAQAAAAABAQEBAQA A
AQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAAEBAQEBAAAAAAAAAAAAAAABAQEBAAAAAQAAAAABAAAA
AAAAAAAAAAEBAAABAQAAAQEAAAEBAAABAQAAAQEAAAABAQEAAQEAAAAAAAAAAAAAAQEAAAAAAAAA
A QEAAAAAAQEAAAEBAAABAQAAAQEAAAEBAAABAQAAAQEAAAEBAAAAAQEBAAEBAAAAAAAAAAAAAQEA
AAA BAQAAAAAAAAAAAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAABAQEBAQEAAAAAAAABAQABAQEB
AQEAA AEBAAAAAQEAAAABAQEAAAAAAQEAAQEAAAEBAAAAAQEAAQEAAAABAQAAAQEAAQEAAAAAAQEB
AAAAAAA AAAAAAAABAQAAAAEBAAAAAAAAAAAAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAAB
AQAAAQEBA QEAAAAAAAAAAAAAAAAAAQEAAAAAAAABAQAAAAABAQEBAQEAAQEAAAAAAAABAQAAAAAA
AAABAQEBAQE AAAAAAQEAAAAAAAABAQAAAAAAAQEBAAAAAAEBAAEBAAAAAQEAAAEAAAEBAQEAAAAA
AAEBAAAAAAAAA QEAAAEBAAEBAQEBAQAAAAAAAAAAAAAAAQEAAAEBAAABAQAAAQEAAAABAQEBAAAA
AQEBAQEBAAAAAAE BAAAAAAEBAQEBAQAAAAABAQAAAAAAAAEBAAAAAQEBAQEAAAABAQAAAQEAAAEB
AAABAQAAAQEBAQEAA QABAQAAAAEBAAEBAAABAQEBAQEAAAABAQABAQAAAAEBAQAAAAABAQEAAAAA
AQEAAQEAAAABAQAAAAA AAQEBAQAAAAAAAQEAAAABAQABAQAAAAABAQEAAAAAAAAAAAAAAAAAAAAB
AQAAAAAAAQEAAAAAAAEBA QEAAAAAAAAAAQEAAAABAQEBAQAAAQEAAAEBAAAAAQEBAAEBAAAAAAAA
AAAAAAAAAAEBAAAAAAABAQA AAAAAAAAAAAAAAAABAQEAAAAAAAABAQAAAAAAAAEBAAAAAAABAQEB
AAAAAAAAAAAAAAAAAAABAQAAA AAAAQEAAAAAAQEBAQEAAAEBAAAAAQEAAQEAAAABAQABAQAAAAEB
AAABAQEBAQAAAAAAAAAAAAAAAAA BAQAAAAAAAQEAAAAAAQEAAAEBAAABAQAAAQEAAAEBAAABAQAA
AQEAAAEBAAAAAQEBAAEBAAAAAAAAA AAAAAEBAQABAQABAQABAQEAAAAAAAAAAAAAAQEAAQEBAAAA
AQEAAAEBAAABAQAAAQEAAAEBAAABAQA AAAAAAAAAAAABAQEAAQEAAQEAAQEBAAAAAAAAAAAAAAEB
AQAAAQEAAQEBAQABAQABAQABAQEBAAEBA AABAQEAAAAAAAAAAAAAAAEBAQEAAAABAQABAQAAAAEB
AAEBAAAAAAEBAQEBAAAAAAAAAAAAAAEBAQE BAQAAAAAAAAAAAAAAAAAAAAAAAAABAQEAAAAAAQEA
AQEAAAABAQABAQAAAAABAQEAAAAAAAAAAAAAA AABAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAEB
AAAAAAAAAAAAAAAAAAABAQAAAAAAAAEBAAAAAAA BAQAAAAAAAQEAAAABAQAAAQEBAQEAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQEBA QEBAAEBAAAAAAAAAQEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAQEBAQEBAQAAAAAAAAEBAAAAAAAAAQEA
AAAAAAAAAAAAAAAAAAAAAAABAQAAAAEBAQEBAAABAQAAA QEAAQEAAAABAQEBAQEAAAABAQAAAQEA
AQEAAAEBAAEBAAABAQAAAAAAAAEBAQEAAQEAAAABAQEBAQA AAQEAAAEBAAEBAAAAAQEBAQABAAAA
AQEAAQEAAAEBAAEAAQABAQABAQEBAQAAAAAAAQEAAAAAAQEAA AAAAAAAAAAAAAAAAAEBAAAAAAAA
AQEAAAAAAAEBAQEAAAAAAQEBAQAAAAAAAQEAAAAAAAAAAAAAAAA AAAAAAAAAAAABAQAAAQEAAQEA
AAEBAAEBAAABAQAAAAEBAAABAQAAAAEBAAABAQAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAEBAAAB
AQAAAAEBAAABAQAAAAEBAAABAQABAQAAAQEAAQEAAAEBAAAAAAAAAAA AAAAAAAAAAAAAAAABAAAA
AQABAAAAAQAAAAAAAQAAAAEAAQAAAAEAAAAAAAEAAAABAAEAAAABAAAAA AABAAAAAQABAAAAAQAA
AAABAAEAAQABAQABAAEAAQAAAQABAAEAAQEAAQABAAEAAAEAAQABAAEBAAE AAQABAAABAAEAAQAB
AQABAAEAAQAAAQEBAAEBAQEBAAEBAQABAAEBAQABAQEBAQABAQEAAQABAQEAA QEBAQEAAQEBAAEA
AQEBAAEBAQEBAAEBAQABAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAA AAAABAQAAAAAA
AAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAA AEBAAAAAQEB
AQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAQEBAQE AAAAAAAAB
AQAAAAEBAQEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAABAQABAQAAAAEBAAEBA AAAAQEA
AQEAAAABAQABAQABAQEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAAAAAAAAAAAAAA AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAQEBAQEBAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAAAA AAA
AAAAAAAAAAAAAQEBAQEAAAAAAAABAQAAAAEBAQEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAA A
AAABAQABAQAAAAEBAAEBAAEBAQEAAQEAAAAAAAABAQABAQEBAAEBAAAAAQEAAQEAAAABAQABAQAA
AAEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAAA
A QEAAQEAAAABAQABAQAAAAAAAAAAAAAAAAAAAAAAAQEBAQEBAQAAAAAAAAEBAAEBAQEAAQEAAAAB
AQA BAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAEBAQEAAQEAAAAAAAABAQABAQEB
AQEBA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEA
AQEAAQE BAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQAAAAAAAAEBAAAAAQEBAQEA
AAAAAAABA QAAAAEBAQEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAA AAAAAAAAAAAABAQEBAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAA
AAAAAQEAAAAAA AABAQAAAAAAAAEBAAAAAAAAAQEBAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAABAQAAAAAAAAE BAAAAAAAAAQEAAAAAAAABAQAAAAEBAQEBAQEBAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQEBAQEBAQAAAAEBAAAAAAAA
AQEAAAAAAAABAQAAAAA AAAEBAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEBAQEAAAAB
AQAAAAAAAAEBAAAAAAAAA QEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQEB
AQEBAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEA
AAABAQEBAQEBAQAAAAEBAAAAA AAAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQEB
AQAAAAEBAAAAAAAAAQEBAQEAAAA BAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAEBAAEBAAAAAQEAAQEA
AAABAQABAQAAAAEBAAEBAAAAAQEAA QEBAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAA
AAEBAAEBAAAAAQEAAQEBAAABAQAAAAA AAAEBAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAEBAQEBAQAAA QEAAAAAAAABAQABAQEAAAEBAAEBAAAAAQEAAQEAAAAB
AQABAQAAAAEBAAEBAAAAAQEAAQEAAQEBAQA BAQEAAAAAAAAAAAEBAQEBAQEBAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AEBAQEBAQEBAAAAAAAAAAABAQEBAAEBAQAAAQEA
AQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAA BAQABAQAAAAEBAAEBAQAAAQEAAAAAAAABAQAB
AQEAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAAAA AAAAAAAAAAAAAAAAQEBAQEBAQEAAAAAAAAA
AAEBAQEBAQEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAABAQABAQAAAAEBAAEBAAEBAQEAAQEB
AAAAAAAAAAABAQEBAAEBAQAAAQEAAQEAAAABAQABAQAAA AEBAAEBAAAAAAEBAAAAAAAAAQEAAAAB
AQEBAQEBAQAAAAAAAAAAAQEBAQEBAQEAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAEBAAEBAAAA
AQEAAQEAAAABAQABAQAAAAEBAAEBAAEBAQEBAQEBAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAEBAQEBAQEBAAAAAAAAAAABAQEBAQEBAQA AAAEBAAAAAAAAAQEAAAAAAAAB
AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEBA QEBAQEAAAEBAAEBAAAAAQEA
AQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAAAAEBAAE BAAAAAQEBAQEBAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEAAAAAAAABAQAAAAAAAAEBAQEBA AAAAQEAAAAAAAABAQEB
AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA BAQEBAQAAAAEBAAAA
AAAAAQEBAQEAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAA
AAAAAAAAAAAAAQEBAQEBAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQABAQA AAAEBAAEBAAAA
AQEAAQEAAAABAQABAQABAQEBAQEBAQAAAQEAAQEAAAABAQABAQAAAAEBAAEBAAAAA AEBAAAAAAAA
AQEAAAABAQEBAQEBAQAAAAEBAAAAAQEBAQEBAQEAAAABAQAAAAAAAAEBAAAAAAAAAQE AAAAAAAAB
AQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAEBAQEBAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQEBAQAAAAEBAAAAAAA AAQEA
AAAAAAABAQAAAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBA QEB
AQEBAQEBAQEBAQEBAQEBAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQEBAQE B
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQAAAAABAQEBAAAAAAEBAQEAAAAAAQEBAQAAAAAB
AQEBAAAAAAEBAQEAAAAAAQEBAQAAAAABAQEBAAAAAAAAAAABAQEBAAAAAAEBAQEAAAAAAQEBAQAA
A AABAQEBAAAAAAEBAQEAAAAAAQEBAQAAAAABAQEBAAAAAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQE BAQEBAQEBAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAA AABAQEAAQEAAQEAAQEBAAABAQAAAQAAAAEBAAEBAQAAAAEBAQABAQAAAAAAAAAAAAABAQEB
AAAAAQE AAAEBAAABAQAAAQEAAAEBAAEBAAAAAQEAAAEBAAABAQAAAAEBAAEBAAABAQAAAAAAAAAA
AAABAQEBA QEBAAEBAAAAAQEAAQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAAA
AAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAEBAQEBAQEAAAEBAAEBAAAAAQEAAQEAAAABAQABAQAA
AAEBAAEBAAAAA AAAAAAAAAEBAQEBAQEAAQEAAAABAQAAAQEAAAAAAAAAAQEAAAAAAAEBAAAAAAAB
AQAAAAEBAAEBAQE BAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAQEBAQABAQABAQAAAAEB
AAEBAAAAAQEAAQEAA AAAAQEBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQAAAQEAAAEB
AAABAQAAAQEAAAEBAAA BAQAAAQEAAAEBAQEBAAABAQAAAAAAAAAAAAAAAAAAAAEBAQABAQABAQAB
AQEAAAAAAAEBAAAAAAAAA QEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAAAAAAAAAQEBAQEBAAAAAAEB
AAAAAAABAQEBAAAAAQEAAAE BAAABAQAAAQEAAAABAQEBAAAAAAABAQAAAAABAQEBAQEAAAABAQEA
AAAAAQEAAQEAAAEBAAAAAQEAA QEBAQEBAQABAQAAAAEBAAABAQABAQAAAAABAQEAAAAAAAAAAAAA
AAAAAQEBAAAAAAEBAAEBAAABAQA AAAEBAAEBAAAAAQEAAAEBAAEBAAAAAQEAAQEAAAEBAQABAQEA
AAAAAAAAAAAAAAAAAQEBAAAAAAEBA AAAAAAAAAEBAAAAAAEBAQEBAAABAQAAAQEAAAEBAAABAQAA
AAEBAQEAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAABAQEBAQEAAQEAAQEAAQEBAQABAQABAQAB
AQEBAQEAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAQEAAAAAAAEBAAAAAQEBAQEBAAEBAAEBAAEBAQEA
AQEAAQEAAQEBAQEBAAABAQAAAAAAAQEAAAA AAAAAAAABAQEBAAAAAQEAAAAAAAEBAAAAAAAAAQEB
AQEBAAABAQAAAAAAAAABAQAAAAAAAAABAQEBA AAAAAAAAAAAAAAAAAAAAAAAAQEBAQEAAAEBAAAA
AQEAAQEAAAABAQABAQAAAAEBAAEBAAAAAQEAAQE AAAABAQAAAAAAAAAAAAAAAAAAAAAAAQEBAQEB
AQAAAAAAAAAAAAEBAQEBAQEAAAAAAAAAAAABAQEBA QEBAAAAAAAAAAAAAAAAAAAAAAAAAAABAQAA
AAAAAAEBAAAAAAEBAQEBAQAAAAABAQAAAAAAAAEBAAA AAAAAAAAAAAAAAQEBAQEBAAAAAAAAAAAA
AAABAQAAAAAAAAABAQAAAAAAAAABAQAAAAAAAQEAAAAAA AEBAAAAAAAAAAAAAAAAAAEBAQEBAQAA
AAAAAAAAAAAAAAABAQAAAAAAAQEAAAAAAAEBAAAAAAAAAAE BAAAAAAAAAAEBAAAAAAAAAAAAAAAB
AQEBAQEAAAAAAAAAAAAAAAAAAQEBAAAAAAEBAAEBAAAAAQEAA QEAAAABAQAAAAAAAAEBAAAAAAAA
AQEAAAAAAAABAQAAAAAAAAEBAAAAAAAAAQEAAAAAAAABAQAAAAA AAAEBAAAAAAAAAQEAAAAAAAAB
AQAAAAEBAAEBAAAAAQEAAQEAAAAAAQEBAAAAAAAAAAAAAAAAAAAAA QEAAAAAAAAAAAAAAAABAQEB
AQEAAAAAAAAAAAAAAAABAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAABAQEAAQEAAQEAAQEB
AAAAAAAAAAAAAAABAQEAAQEAAQEAAQEBAAAAAAAAAAAAAAAAAAAAAAAAA AABAQEAAAAAAQEAAQEA
AAABAQABAQAAAAABAQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAEBAAAAAAAAAQEAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAQAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAA
AAAAAAAAAAAAAAEBAQEAAAAAAQEAAAAAAAABAQAAAAAAAAEBAAABAQEAAQEAAAABA QABAQAAAAAB
AQEBAAAAAAABAQEAAAABAQABAQAAAAABAQABAQAAAAEBAAEBAAAAAQEAAQEAAAABAQA BAQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEBAQAAAAAAAAABAQAAAAAAAQEAAAAAAAEBAAAAA AABAQEB
AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQEBAQAAAAA BAQEB
AAAAAAEBAQEAAAAAAQEBAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

Hi folks,

this is just a little tip for those of you who dislike their xhtml to end up as tag soup and still prefer to send out Html 4.01 strict. Here is how to make all helper functions in Cake 1.2 output Html 4.01 compliant markup instead of xhtml:

If you wonder why somebody would prefer the good old html over the all-so-hyped xhtml, read a little bit about it here.

-- Felix Geisendörfer aka the_undefined

If you want to use a Javascript file, you usually reference it in the head section of your layout:

<head>
    <?php echo $javascript->link('script.js'); ?>
</head>

But sometimes you want to use a certain Javascript file only in one view. Then it doesn’t make sense to reference it in the layout. You could take the PHP statement from above and place it in your view, that will work. But it is not a clean solution as the Javascript reference is placed somewhere in the middle of the generated HTML code.

Fortunately, CakePHP 1.2 allows you to define a reference to a Javascript file which is then added to the head section of the generated HTML code. For this purpose the variable $scripts_for_layout has to be added to the layout:

<head>
    <?php echo $scripts_for_layout; ?>
</head>

In the view you can now link to the Javascript file with:

$javascript->link('script.js', false);

That’s it.

I’m going to be hanging out in Redmond, WA. late next month… why? That… I’ll explain at a later date. ;-)

What I can say is that I’ll be available on a few evenings if anybody is interested in meeting up to talk shop, which can include anything from d3, ruby on rails, bdd, agile interaction design... to BBC comedy shows. :-)

I’ll be flying up from Portland to Seattle on Saturday, March 24th. I’m going to try and stay downtown for that night… and then will be staying at Sheraton Bellevue until Tuesday night. So… Saturday-Monday nights are currently open.

I’m also planning to head to the monthly Seattle.rb meeting on Tuesday, March 27th.

If you’re interested in meeting up, drop me a line.

UPDATE If you’re taking the kinky aspect of BDD too serious... please don’t email me. ;-)