Unfortunately, 99% of dreamweaver users barely know how to hand code.dornoforpyros said:...I'd highly suggest sticking with dreamweaver and learning to code properly.
Sounds like a great answer to me. Additionally, I'd say that to compare iweb with dreamweaver would be to compare photoshop with MS paint.rtdgoldfish said:For personal use, iWeb is really easy and makes some great looking sites. However, Dreamweaver is a professional application and MUCH more can be done with it.
If you are looking to make a personal site, go with iWeb. If you have never made a website before, go with iWeb. However if you are doing a site for a college class or for a business, I'm pretty sure you'd want to go with Dreamweaver.
I used dreamweaver for about 5-6 years ever since macromedia bought the app from another company. Let's just say I've moved on to a much more powerful editor (textmate) ever since I started the transition to css-based design. Dreamweaver is bloatware and most of the features aren't really necessary these days. Why use an editor that takes 10 seconds to start up, is full of toolbars and palettes, and costs $400+ when you can use something better, faster, cheaper, and more powerful (assuming you know how to hand code well). Here's a tiny example of what textmate can do:Jimmieboy said:I'd got for dreamweaver. I use it for a lot of school assignments. It's definatly a pro app. Theres a lot of books out there to help you out if you don't know how to use it.
And by the way radiantm3. I'm part of that 1% that can understand code. What types of code do you use? I'm assuming that you do know how to use some kind of code. I use a lot of php and html for assignments and other things. I wouldn't call myself and pro user but way ahead of beginners.
Jimmieboy said:At school they have version 6. it doesn't support css so making websites with css is impossible.
jessica. said:Sounds like a great answer to me. Additionally, I'd say that to compare iweb with dreamweaver would be to compare photoshop with MS paint.
ThunderLounge said:If you only take one thing from this, remember:
Tables are for tabular data, not layout.
What do you consider "non-standard?" The past couple versions of Dreamweaver have always produced perfectly validated code in all doctypes. Dreamweaver also doesnt do anything different with CSS than what a person would do manually, Dreamweaver just makes it faster and easier to manage. You still have to know CSS to use Dreamweaver since its preset GUI functions are so limited.Using a WYSIWYG editor is not how you want to start out. They all produce non-standard code, even the big names.
stainlessliquid said:I dont know why the hardcore coders always have something against Dreamweaver. If you took out the tabs that DW creates for easier code reading then theres no way to tell the difference between a DW page and a textpad page. Most good DW users still work almost exclusively from the code view mode, DW simply offers a number of tools to make the process faster.
stainlessliquid said:What do you consider "non-standard?" The past couple versions of Dreamweaver have always produced perfectly validated code in all doctypes. Dreamweaver also doesnt do anything different with CSS than what a person would do manually, Dreamweaver just makes it faster and easier to manage. You still have to know CSS to use Dreamweaver since its preset GUI functions are so limited.
I dont know why the hardcore coders always have something against Dreamweaver. If you took out the tabs that DW creates for easier code reading then theres no way to tell the difference between a DW page and a textpad page. Most good DW users still work almost exclusively from the code view mode, DW simply offers a number of tools to make the process faster.
Oh my god.. have you seen the code that generates?![]()
stainlessliquid said:DW has a true WYSIWYG feature where you draw divs/tables on a grid, I forget how to even use it but it can create some horrifying code. I think thats where DW code really comes out bloated.
Ive been using DW for a few years and havent come across a validation error in a really long time with the new version (if ever), whether I use DW's built in one or a third party one. I was skeptical of DW's new xhtml ability but it still managed to nail it even though its so much more strict. If I do get an error its usually my own code where I experiment rather than DW's generated code.
I think it just depends on whos using it. DW usually doesnt do anything you dont want it to do, if someone's code is bloated with abunch of crap they dont need then chances are they would have added those things by hand as well. Building a site using only the GUI isnt the smartest thing in the world, Macromedia definately concentrated more on the pro usage which involves making manual coding faster (the reason I use it).