Quince PHP Controller


Quince: Past, Present and Future

Versions 0.1-0.7

Quince started life in the fall of 2005 as PHP-Controller, a personal project of Eddie Tejeda shortly after he co-founded Visudo, a web development business, with Marcus Gilroy-Ware.

His vision was a lightweight MVC controller, similar to that of Struts for JavaServer Pages.

Many of the best PHP frameworks that are available now, such as Symfony, either did not exist or were not widely known or supported, and those that did were far more heavyweight than a simple controller.

Borne out of Visudo's tried and tested way of building applications around a single entry point and using Smarty as a display layer, Eddie sat down and began work on PHP-Controller.

Version 0.8

Fast forward a year, and work on the Smartest content management platform, which uses Quince, was in its early planning stages.

Smartest was considerably more complex an app than anything else that had used PHP-Controller up until that point, and made fresh demands on it.

Because of the pressures of client work, and of life, if was hard to find the time to fix some of these issues, so the lead developer of Smartest, Marcus Gilroy-Ware, instead re-wrote PHP-Controller from scratch as a drop-in replacement for the original.

After some months of testing, Eddie and Marcus agreed to re-name and re-brand PHP-Controller, and Quince was born.

As the last version of PHP-Controller had been 0.7, they made the version number of Quince 0.8.

Shortly thereafter the two amicably agreed to separate their business interests, and as both turned their attention to other things, Quince faded into the background. It was being used heavily, but not developed.

In the fall of 2008 Marcus Gilroy-Ware decided that Quince was so good it should rediscovered and released.

Version 1.0

The next major release of Quince, 1.0, will be the stable resolution and completion of the code that started with the 0.8 re-write and the birth of Quince. This release will add some further new features such as namespaces, but will keep the same API that has been with the project since its birth, and will be aimed at stability and completeness rather than any grander designs.