A number of posts out there today concern working with HTML forms in PHP (Paul M. Jones » Form Processing Questions). The debate seems to hinge mostly on whether a single monolithic, automatic form generation class/script should be preferred to an approach that separates the Model and View more cleanly.

I have to agree with Thoughts on form building/processing that handling forms is one of the most tedious tasks that you can come across. I'm all for any solution that makes it easy to present a form, collect the input, and store it. Since 99% of the time the information is stored in a database, I'm not so worried that the Data, Model, and View are so tightly bound together. That just frees up time to work on more interesting problems.

From: MercuryNews.com | 09/09/2004 | TiVo, ReplayTV agree to limits. How many people order pay-per-view, especially for movies? The last time I ordered PPV, I can barely remember. I think it was a friendly between the USA and Chile back in 1999...

The new technology also will allow Hollywood movie studios and broadcasters to regulate how often movies purchased through pay-for-view services can be watched. Digital video recorders that recognize these new copy restrictions will begin appearing in the spring of 2005. But it could be years before entertainment companies begin to take advantage of the technology, according to ReplayTV President Bernie Sepaniak.

I didn't want to let Sandy beat me to the punch this time so here goes. Over at Forum One, my employer, we released Syntax CMS version 1.1.0, which is the content management application that we've built and use. The code has come along way over the last few months in response to features requests we heard from multiple clients.

We've added some more feature that make managing content on a site easier, particularly if you want to have groups of content managers with different access privileges to content. For example, you can now define a group for "authors" who can add and edit site articles and another group for "editors" who can approve and delete site articles.

I also diagnosed and fixed a big performance bottleneck associated with displaying paginated results from modestly large mysql query results. With Sandy, we've made improvements to the API that simplify writing custom code you might want.

The source code is availble via CVS:

export CVSROOT=:pserver:anoncvs@cvs.tigris.org:/cvs
cvs checkout -d syntaxSandbox syntax-cms/src

You can also download it as a gzipped tar file: Syntax CMS 1.1.0