Comments are embedded: On Oct 19, 3:58 pm, drmikecrowe <[EMAIL PROTECTED]> wrote: > It's a specific situation where the template design is done by another > entity, and that person typically uses something like Frontpage or > Adobe Premier.
I don't think you're being prevented from such a task. The app I'm currently working on had a "template" created for it 2 years ago. It has since been added on to and maintained using Dreamweaver. You can imagine what the code looks like... We took that code and simply cleaned it up, converted it from tables to CSS and gave it back to the designers to do a final review. They made some modifications (again in Dreamweaver) and we got what became our default layout for the site. > A HTML page developed by a wysiwyg editor is difficult > to *develop* in symfony without a template system which is wysiwyg > friendly. Your coders and designers are going to have to work together. I might point out: http://www.37signals.com/svn/posts/642-ask-37signals-do-i-need-a-designer-to-make-pretty This is a great blog post that really encompasses what I'm getting at here. > If you merge it once (and put the PHP tags inside), it's > ok. However, merging it 5 times is 5x the work. In the past, I've just gone ahead and created dummy "data" to lay down my styles and formatting in CSS. Then when I actually want to merge the design and the code I just take the dummy data out and put in the appropriate helpers, etc. Ultimately your designers ARE going to have to understand, at least on a basic level things like link_to, form_tag, etc. I'm sure this will sound repetitive, but your views should have VERY little logic contained in them. The majority of the logic should never be sitting in a template. > Naturally, I'd much rather code the template from the ground up and > make it very light. However, when a 3rd party is involved, this > allows much better interactive development. I can certainly see the advantage to what you're saying. If you engage an expensive design agency that does straight XHTML/CSS design and graphic assets you don't want to continually pay them to go back and forth doing a bunch of Symfony specific related "merges", etc. That said, you can take a design and break it down into the required partials, templates, and layouts. I am interested in hearing how you resolved the issue after you've read through everyone's responses and actually implemented whatever solution you choose. Ultimately you cannot REALLY go wrong, but people have some great ideas in here for you! Regards, Keith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
