I chose to start from the ground up using HTML/CSS for layout and PHP/MySQL for the management components, rather than using a pre-built CMS, to get exactly and only the features the client and their clients needed.

Ed Townend Does Design! completed the project on time and to the clients delight – adding the tips each day and managing club members could not be easier! Members love the way they can filter tips for any date and the streamlined PayPal subscription system.

Edit Screen

This was, however, the first project I’d ever chosen to write in PHP, so I had to learn to adapt my knowledge of  Visual Basic and Access via ODBC, a client-side language, to the server-side nature of PHP and MySQL. The cient didn’t really want to hang around forever, so I thought I could speed up the whole process by using Dreamweaver’s ability to ‘build applications visually’, then tweak and add to the resultant code to add the custom features they requested. These included automatically defaulting to editing today’s date, a rich text editor for notes, easily editable drop down menus for the betting system, automatically moving to the next tip once saving, and some other stuff. It still sounded pretty easy, even for a PHP novice.

After some initial confusion regarding using phpMyAdmin to create the database (solved by the hosting provider,) I was amazed at how quickly and easily I could piece together the bones of this program in Dreamweaver without even touching the code. It seemed a great way to work, letting Dreamweaver do the hard work and then tweaking the result. I was getting paid to click and drag! However, I soon ran into problems. Once I had a few server behaviours on the page, they started to clash, as they were all trying to use the same variables. This took a few hours to hunt down, and even more to correct the problems I caused (Coming from my VB background, I kept forgetting that lines had to be ended with a semicolon.) The biggest problems arose when I finished the structure and came to tweaking Dreamweaver’s generated code. What seemed to happen when I made a change to the code, is that Dreamweaver would no longer recognise its own code, the server behaviour would disappear from the side panel, and then it would decide that the code was ‘wrong’ or redundant and try automatically correcting it or even deleting it. I can’t remember the specific problems now, but it really felt that it was me versus Dreamweaver, with it battling to keep its code and me trying to hack it up with my keyboard. In the end, I got a working system presented to the client, and thought that was it.

TinyMCE (The text editor) was really easy to integrate, and has options for every scenario

Now, a year or so later, I’ve been asked to add some more features to the code. Since then, I’ve moved from CS3 to CS4, and immediately I ran into problems with Dreamweaver not recognising the spry tabbed panels I used to separate the different actions the user can take (see the screenshots). From there I ran into the same sort of problems as last time, but I was now better prepared to deal with them. Last night I got the extra features finished, and saved the files ready to deliver to the client on Monday. This morning I had a quick check of the finished page, and spotted a line of text that could be better worded. I changed the text, which involved no changes to the PHP code, uploaded to the server to test once more, and what?! Suddenly the save button is broken! The code goes through all the motions of saving to the database, the page refreshes, the confirmation message shows, but the change has not stuck. But this was working last night, and I haven’t even changed the PHP code! Now I remember last time, Dreamweaver played this game with me, and it took ages to find that it had automatically added a closing tag or something where I didn’t want one. For some reason the update record server behaviour has disappeared from the panel. Now I’m going to have to look through all the code to find something I didn’t even cause. This sort of thing adds loads of time to a project that can otherwise be complete, and I can’t even imagine a timescale that I can find this bug in. It’s really frustrating, Adobe.

Why didn’t I just stop using Dreamweaver for this project and code manually? I’m a stubborn guy, and I really believe the concept of building applications visually, then adding on custom features can speed things along, if only Dreamweaver could keep its nose out!