Indeed, the quality of Rails, CakePHP, Django, and Catalyst notwithstanding, some developers have rebuffed the large frameworks, citing bulk and complexity, to create smaller and simpler alternatives. Dubbed micro-frameworks-think microcomputer versus mainframe-the tools shape incoming requests into something manageable and leave the rest up to you. Choose your design pattern, object-relational mapper (ORM), and rendering technology, and off you go. As you'll see, a working Web application can be composed in less than ten lines of code in a single source file.

He covers the Ruby framework first (Sinatra) and Limonade next. The framework takes incoming requests and maps them into the developed code. It works like a basic MVC-formatted framework - the request comes in with an action and is sent to a method by the same name. You can use wildcards in the URI, regular expression matching, views, templates and it includes error handling support and configuration option support.

If you're looking for a simple tool that uses Zend Framework's robust database classes (such as Zend_Db and Zend_Db_Table), you can check out zdbform. It's a short yet effective library that let's you perform simple administration tasks on your database, with minimal coding. It's not a full blown phpMyAdmin, but it's a simple way to view, edit and add your tables rows on a web interface.

He shows how you can use it in a script - from the front controller to the input forms - and some of the changes he needed to make in the form class itself to handle a few of the bit more tricky parts.

Up until now, I have used Wordpress.com for my blogging. It works quite well. You can get started quite quickly and it does what most people need. My wife uses Blogger for our family blog. It is, IMO, not as nice as Wordpress.com in some ways. But, it does allow you to edit your styles (for free) and such which is nice. So, why would I want to reinvent the wheel? I am a control freak and rarely run other people's code. I know, it is a character flaw. I am working on it.

His application, WordCraft, already includes things like Akismet/CAPTCHA support for comments, custom page creation, pingback support, temlpating and email notifications. You can download the latest release (version 0.5) from his google code page.

The code in the example reduces the image colors to 10, then discards all but one pixel of every color and then creates the palettes out of those colors. This might not be the most accurate way to do this, but at least it's fast.

His code makes three different "palettes" from the image - average, dark and light - and outputs them as a range of colored boxes for each all of the three palettes. Examples of the output are also included in the post.

I made a very light DBAL that uses PHP5.2.x only (Since many people seem to want that) and it has the exact same DSN syntax as MDB2 for now and the query method are also called the same (No API Changes). [...] The main goal of the DBAL is to have a very effective and light way of switching RDBMS but also the possibility to change your DBAL to something more "0feature complete" as such as MDB2.

He includes the list of query method names and the types of databases that he wants it to support (as well as mentioning the fact that it would be unit tested for reliability).

If you keep an eye on the timeline, you probably saw that the symfony unit tests have been completely reworked lately. This is because we switched from simpletest, which was fine but had side effects when functional tests were executed all at once, to our own testing framework, lime.

Lime is more lighweight than PHPUnit or simpletest and has several advantages. First, it launches test files in a sandbox to avoid strange effects between each test file run (one of the reasons we were unable to fix the old symfony core tests). It also introduces a new sfBrowser, sfTestBrowser and more importantly sfDomCssSelectorBrowser that allow you to write functionnal tests with ease. It is not backward compatible but is a lot more powerful than the old system. Oh, and it holds in a single file, lime.php, without any dependence.

They show some examples of its usage (and a note on which tests will need to be updated) as well as the output that would come of it. They've also included some sample tests (in the "test/" folder of the release) if you'd like to check it out more throughly.

Matthew also mentions a real truth behind programming, no matter who you are - that it takes practice, lots and lots of practice. That's what it is - constant practice so you know better how to combat the troubles you might find the next time they rear their ugly head.

The concept's pretty simple - the form they build submits back to the page and writes the input out to a file. This file is then read by the controller for the LED they have connected and, with the proper input, will turn it on and off. The code for the PHP/web side of things is included, but it might take a little work to get the rest of the hardware interfaced (as the author saw as well).

Chris also points out some of the interesting comments made in the entry, including mentions of Digg's stats and some great comments testifying to the light, powerful nature of PHP.

The most popular open-source software is also the most free of bugs, according to the first results of a U.S. government-sponsored effort to help make such software as secure as possible.

The so-called LAMP stack of open-source software has a lower bug density--the number of bugs per thousand lines of code--than a baseline of 32 open-source projects analysed, Coverity, a maker of code analysis tools, announced Monday.

The results are a product of a Homeland Security effort (performed by Stanford University) for three years. They found that the LAMP combination contained about 0.434 bugs per 1,000 lines of code. Unfortunately, their results also showed, of those problems, PHP had the higest bug count of the four.]]> Tue, 07 Mar 2006 07:25:42 -0600