The way you have suggested is basicly the only way to do this in an efficient manor without building/running a templating engine. This is the method I use if I'm working with only myself or others design is submitted first and made the code to work with the design it makes for the cleanest code I've experienced yet Just my 2 cents --- Anton C. Swartz IV Phoenix Edge Network L.L.C. http://www.phpopenid.com - Owner PHPLogic Development Services http://www.phplogic.net - Co-Owner Necrogami http://www.necrogami.com - Personal Blog Based in Indianapolis, IN "The Opposite of war is not Peace it is Creation." Don't let sin rule your body. After all, your body is bound to die, so dont obey its desires or let any part of it become slave to evil. Give yourselves to God, as people who have been raised from death to life. Make every part of your body a slavethat pleases God. Don't let sin keep ruling your lives.You are ruled by God's Kindness and not by the law. Romans 6:12-14 -----Original Message----- From: Simon [mailto:simon.xhz@xxxxxxxxx] Sent: Monday, July 23, 2007 5:22 PM To: Steve Finkelstein Cc: PHP General List Subject: Re: Strategy when working with designer(s)? I have experience with designers. My suggestion. Don't code anything client-side until they are finished, you will most likely have to change everything. You can do your functionality (login mechanism, password change, listing, query with db, etc...) and be ready for when they give you their monster. I've worked in many ways like: 1) Programmer does the functionality 2) Designer gives the design 3) Integrator tries to make it work This one fails most of the time, gives headaches when it gets to work. And will most likely go back and forth #1 and #3 a couple of times! I recommend: 1) Designer does his whole job and shows the design when finished and approved 2) Integrator works on making the pages and html without func. 3) Programmer makes the whole thing work. This gives the best feeling to all people involved. All IMO! Simon On 7/23/07, Steve Finkelstein <sf@xxxxxxxxxxxxx> wrote: > Hi all, > > This is more of a conceptual based inquiry. I'm currently working on > some projects which require me to build system 'X' prior to any > (X)HTML/CSS/graphics are available to me. A lot of the time, I just > garble up default tables/forms/images to replace what the designer will > be ultimately adjusting. It's certainly a lot simpler to have someone > come to you with the CSS/HTML and then building on top of that. > > I was curious how do you folks who strictly do development and not > designing, strategically work with a designer in this fashion? Do you > have a skeleton you follow or preload some existing templates and then > code around that? If there's even a book which focuses on such concepts, > I'd be more than happy to purchase and read it. > > Thank you kindly for any insight. > > - sf > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.10.14/912 - Release Date: 7/22/2007 7:02 PM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.10.14/912 - Release Date: 7/22/2007 7:02 PM -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
