On 27 Nov 2009, at 14:41, Conrad Taylor wrote: > Peter, I tend to use Fireworks CS4 to slice up the PSD to generate > HTML, CSS, and images. This gives me the initial cut of the design > in HTML and CSS. Then I'll use both Dreamweaver CS4 and Textmate. > Dreamweaver has embedded the WebKit engine so that I can see the > changes to my site code without opening a browser. Thus, I tend to > do most of the CSS and HTML in it. Next, I use Textmate mostly for > the RoR and Ruby specific things because Dreamweaver provides the > ability to invoke Textmate from DW. > In short, I use the best tool(s) for the job and I haven't hit any > walls but leveraged other toolsets.
Yes, but even then you are handcoding most of the page in Dreamweaver, aren't you? It basically means you have a very expensive handcoding IDE (but the price of course justifies itself if it makes you more productive, it doesn't for me, even though I had to use Dreamweaver for years, so I know my way around). Depending on the project, I'm also using Fireworks to slice up the graphics. Most projects we do however tend to be about structure first, having to keep in mind how the data will flow in it and make sure either Rails or Javascript will easily be able to push the data in, i.e. the HTML needs to be very straightforward. Doesn't mean the final result isn't graphically impressive. However, the code that Dreamweaver generates as a pure WYSIWYG editor is just horrendous, especially in the hands of a designer who doesn't grasp HTML+CSS in the slightest. Yes, the result renders, but having to work with the generated code for creating dynamic pages is a real pain. Hope this clears things up a bit. Best regards Peter De Berdt -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
