HTML/ CSS / JS will be your best bet for production ready code. Even a tool like Dreamweaver tends to add unnecessary code.
As far as your second Q is concerned- there is space for a prototype only tool. If you're building a small 10 page website (or a simple tool), maybe not so much...but for complicated ones its a different story. The trade-off here is that of complexity & domain expertise. Production ready code is not easy to automate and I'd rather not be pixel pushing when I'm working on a design problem. One approach would be to have the front-end developers within the design team as opposed to the dev. Dunno how they would feel about it, but its great from a UX perspective because of better control of the product (esp when the UX & dev don't report into the same manager, as is common in most large orgs) > I hope this isn't a dumb question, but are there any prototyping > tools (Visio, Axure, Fireworks, etc.) that actually give you a usable > website at the end? I'm just wondering if it's worth spending the > time applying all this functionality to a prototype, if it's all > going to have to be re-coded afterwards. -- -Vishal http://www.vishaliyer.com ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
