RE: [PHP] Dreamweaver 4 ignores PHP - again

From: Date: Thu, 16 Nov 2000 10:12:24 +0000
Subject: RE: [PHP] Dreamweaver 4 ignores PHP - again
Groups: php.general 
Request: Send a blank email to php-general+get-25666@lists.php.net to get a copy of this message
> > For a product to dominate it must > > allow a company's monkeys to be productive. > > That's why these tools are more > and more popular and there is an increasing demand to get RAD > tools out > there. And of course, this leaves the IT industry with all > these so called > "programmers" out there that haven't a clue. Well, Dreamweaver became successful because it was the first "more-or-less-wysiwyg" program to try not to interfere with code unless you told it to. It also was extensible and customisable to many ways of work and as such managed to please both technically oriented developers and designers. The Dreamweaver-Homesite combination was and is a killer environment. Sometimes graphical is very much the faster/easier way to do things - it took me for ever to decompose some very big html (tables within tables within tables, arg!!!) I had to integrate with one of my applications, and had I had dreamweaver around it would have been much easier to select a whole big table and paste it to another file etc. (or had i had an editor that supports a parenthesis-matching equivalent for tags...) Dreamweaver does recognize php and hides <?php ?> bits behind little "php" icons (which the designer can see and leave untouched). As far as I know it deals with php the same way it deals with other "inline" languages such as jsp, asp, cf so I don't know what is meant by "DW ignores". You can even customize to recognize all the extensions you use (I use phtml, phpclass) or open a separate editor for the <?php ?> bits. I have not done it cause my inline php is limited to display things such <?php echo $this->fields["name"]; ?> with a few "ifs" here and there and a loop now and then. Now before anyone jumps on that ("arg, loops, means you're putting logic in your layout, bad bad bad), it is a compromise between clean separation, ease of maintenance for both you and the designers, and performance. I have noticed that designers have an easier time if a whole table structure is shown in one piece containing a loop or two - rather than a loop in the main program calling templates such as row_head, cell, row_end. There's ways to do that that do not involve putting logic in the program (i.e. loop up to $number_of_rows and $number_of_colums and use an array set in the main progam etc) disgressing again, sorry Joelle Nebbe _______________________________________________________________________ Any opinions expressed in the email are those of the individual and not necessarily the company. This email and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. If you have received this email in error please notify the IT manager by telephone on 0113 243 2701 _______________________________________________________________________

« previous php.general (#25666) next »