Resistance perhaps not so futile...
"Since I have Dreamweaver MX, I might as well use it..."
Thus began the migration of Alrak's Parallel Universe from FrontPage 2002/XP to Dreamweaver MX. Since I wasn't using any FrontPage specific code in the site, the migration wasn't terribly painful. Learning how to make Dreamweaver MX easily do the things I'm used to doing in FrontPage, however...not painful, exactly, but at times I've found myself scurrying back to FrontPage just to get something accomplished quickly.
Other than expanding my knowledge base, I had no compelling reason for switching to Dreamweaver, so it's not that I found FrontPage lacking. And I can't say right now that I would recommend all folks immediately switch if they can. I think some folks are drawn to Dreamweaver merely because of the "cool" factor - it's not Microsoft (but, hey, nothing is "cooler" than using, say, Notepad - oh, wait, that's Microsoft, too...;-). Don't get me wrong, Dreamweaver seems to be an excellent product and capable of everything (if not more) that FrontPage can do. I would say it all depends on what you want your WYSIWYG Web editor to do for you. My demands are simple: don't change my freakin' code unless I run some clean-up command. Both FrontPage and Dreamweaver have been sworn at many times now for not meeting that demand. (Notepad, on the other hand, has never let me down in that department...)
Dreamweaver has forced me into a good habit, which is editing offline and then uploading to the live site. With FrontPage it was so easy to be bad and just edit live.
I'm sure I'll be posting more on my experiences with Dreamweaver. I'm taking a Level 1 class on it through Element K and I think I'm probably beyond the level of the class - I already [I think] know how to do a Web site - I just need to know where Dreamweaver buries its commands.
Thus began the migration of Alrak's Parallel Universe from FrontPage 2002/XP to Dreamweaver MX. Since I wasn't using any FrontPage specific code in the site, the migration wasn't terribly painful. Learning how to make Dreamweaver MX easily do the things I'm used to doing in FrontPage, however...not painful, exactly, but at times I've found myself scurrying back to FrontPage just to get something accomplished quickly.
Other than expanding my knowledge base, I had no compelling reason for switching to Dreamweaver, so it's not that I found FrontPage lacking. And I can't say right now that I would recommend all folks immediately switch if they can. I think some folks are drawn to Dreamweaver merely because of the "cool" factor - it's not Microsoft (but, hey, nothing is "cooler" than using, say, Notepad - oh, wait, that's Microsoft, too...;-). Don't get me wrong, Dreamweaver seems to be an excellent product and capable of everything (if not more) that FrontPage can do. I would say it all depends on what you want your WYSIWYG Web editor to do for you. My demands are simple: don't change my freakin' code unless I run some clean-up command. Both FrontPage and Dreamweaver have been sworn at many times now for not meeting that demand. (Notepad, on the other hand, has never let me down in that department...)
Dreamweaver has forced me into a good habit, which is editing offline and then uploading to the live site. With FrontPage it was so easy to be bad and just edit live.
I'm sure I'll be posting more on my experiences with Dreamweaver. I'm taking a Level 1 class on it through Element K and I think I'm probably beyond the level of the class - I already [I think] know how to do a Web site - I just need to know where Dreamweaver buries its commands.
posted by Alrak at 10:22 PM
0 Comments:
Post a Comment
<< Home