Yikes! You mean they don't use a text editor to for html? Seriously, you do have two choices here and I certainly prefer the one suggested below. You may have to talk to the project manager about the designer's refusal to allow thier precious dreamweaver source files to be chopped up. On the other hand, their insistance on using CSS is ideal.
If the project manager does not want the html chopped up then it is not the end of the world. I recently completed a project where the designer insisted on using dreamweaver and leaving the html as single files. I wrote the functions for everything I needed and placed them in include files. I then replaced his sample data with <?= ?> statements and all is well. I'd give you the URL to see how seemlessly it works, but it is a porn site and i'd rather not link it on the list. The moral is that you can certainly be successful in approaching the project this way. Personally, I do not like wading through all that html to figure out where to put my precious php code, but then again they were paying the bills that month. Fred Mike Eheler <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > They sound like good ideas, with one quisp.. the sites are currently > being designed in *shudder* Dreamweaver. > > They absolutely refuse to chop files up into header/footer includes, and > they want to be able to do all their colour customisation through their > beloved .css files. > > Mike > > Jimtronic wrote: > > > > > I try to seperate the php code from the html as much as possible. So, if > > a page is dynamic, have php figure out the dynamic parts first, put them > > into variables such as $html, or $pull_down_menu, or whatever. Then all > > that needs to replaced in the html is that section. HTML coders aren't > > dumb, so they can be trusted with a simple <?= $html ?> placement. > > > > Additionally, I try to seperate php logic from php presentation as much > > as possible. This means creating as many variables as possible that > > affect how things look and then including a conf.php file that the > > coders can also change pretty easily with good documentation. > > > > Moving even further in this direction, my logic code calls many > > presentation functions which I find HTML coders can also decipher rather > > well. You can put these in another include file so your designers don't > > ever have to touch any of your precious logic. > > > > Then ... if you have time ... you can make an admin screen to change, > > edit, and preview the finished product. > > > > Jim > > > >> Hi There, > >> > >> I'm looking for some community feedback on being a coder working with > >> designers. Techniques that work that allow my php-inept page/graphic > >> designer comrade make changes to the layout of the page without > >> destroying my code, or requiring me to make any changes whatsoever. > >> > >> Or what is the best process? Code the dynamicity (heh -- sad thing is > >> you know what i mean by it) of the site, then integrate a designers > >> HTML into your code, *or* the other way around.. have the designer > >> create the site using all static html files, then go in and remove > >> sample data to be replaced with dynamic data (pulled from a DB, for > >> example). > >> > >> I'm about to enter a very large project working with about 3 or 4 > >> designers and 2 other coders and any suggestions on making this > >> relationship work is greatly appreciated. > >> > >> Mike > >> > >> > >> -- > >> PHP General Mailing List (http://www.php.net/) > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> To contact the list administrators, e-mail: [EMAIL PROTECTED] > > > > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]