WYSIWIG: Good or Evil?

Super Mod · 02-08-06, 01:45 AM

A lot of people use Dreamweaver and I don't really have a huge problem with that, but I do think that it can hurt your understanding of HTML if you are looking to learn HTML. The World Wide Wed Constortium has set guidelines on how HTML should be correctly written. What are your thoughts? I'll write mine after I've heard from a few people.

**Avix** · 02-08-06, 04:20 AM

I use Dreamweaver, but I rarely use the design view.

I just like to have number code lines, find and replace, autocomplete, colour code etc

stef686 · 02-08-06, 06:29 AM

I much prefer to code it all myself - the I know it will work, I know what everything does, I know where everything is and it is a lot neater and cleaner!

freeosin · 02-23-06, 09:50 AM

I prefer Dreamweaver, but i understand spencer's comment. Im just on time constraints alot, and im not doing corporate level web design yet.

anne · 02-24-06, 06:15 AM

I think WYSIWYG can be good to help total beginners accomplish their goals, and it can be good to help experienced people do something quickly, but for people wanting to advance their skills I agree it is a mixed blessing.

I use Dreamweaver, but I keep code and design view open at the same thing, and tidy up bits as I go.

No matter what - at least Dreamweaver isn't MS Word or Frontpage

Josie · 02-28-06, 06:07 PM

I don't like to rely totally on a WYSIWYG approach. I use DreamWeaver and work with both code and display on, which works well for me. I know that DreamWeaver's display mode is dependable and that when I go into browser preview, I'm going to see exactly what will show up on the browser.

With other programs, I've found too many that have a WYSIWYG setup, but when you get the page into the browser, there is something wrong somewhere that gets screwed up. So in the end, I wind up going back into the code to find the problem anyway.

Overall, I think a balance is the best way. I've known some fantastic young designers who have absolutely no experience with designing outside of a WYSIWG environment and therefore can't fix a problem that comes about as a result of a missing piece of code like an end tag, etc. Of course, then I get to feel like the king of the world because I can solve the problem in a couple of seconds, while they've spent hours trying to re-do it over and over. Personally, I think designers should have a good basic knowledge of HTML just for those times when WYSIWYG setups let you down. It may not happen a lot, but when it does, it can really mess you up.

ArunK · 02-28-06, 11:49 PM

It can definitely reduce the amount of time it takes to code something. Depending on the situation time constraints can be greatly reduced by using something like Dreamweaver.

darren · 03-01-06, 04:35 AM

I use dreamweaver on every project. I find the add ons that come with it like find and replace and the option to be able to change every page at once is just too much of a time saver to ijnore.

However before Is started using a WYSIWYG editor, I made myself learn html first.

**Chris Gwynne** · 03-01-06, 07:39 AM

I hate WYSIWYG. I don't like not having full control over my code, having some application place their sub-standard code is just wrong. All of my coding for the past 5 years has been hand written, that's how everyone should do it.

anne · 03-03-06, 10:40 AM

Dreamweaver doesn't really place sub-standard code all over the page - its normally quite passive, and lets you do things your way.

A good text editor can have similar sitewide search and replace features though.

I think both 'sides' to this argument have advantages, and its really down to personal preference.

Of course, anyone who uses Frontpage should be shot