In Dreamweaver’s defense

9 July 2009, in Rants, Tools, Work method | 52 comments »

One of the things that causes me great frustration being a web designer is how my coding tool of choice is constantly looked down on. That tool is Dreamweaver. Tired of all the nasty comments that are constantly thrown at it, I’d like to explain, to those who don’t mind reading a quick rant, why I like it. Bear with me.

Attention, rant alert!

First things first: not everybody that uses Dreamweaver is using it in the Design mode, or even Split mode. Or uses the automatic CSS creator/editor tool.

My intentions with this post are not to convince anyone to move from whatever tool they’re using to Dreamweaver—just to make people understand that Dreamweaver is not that little evil tool everyone seems to think it is—a tool for people who can’t code.

One of the reasons I wanted to get a Mac was because then I would be able to use Coda. It looked so clean, intuitive and without all the clutter that Dreamweaver brings with it! Then I finally got my hands on to a Mac, and actually tried Coda: it didn’t last a day.

I’d like to be able to use a cooler or prettier tool, and, believe me when I say that I’ve tried a lot of them: Coda, Espresso, BBedit, Notepad, etc. I end up frustrated because simple things I’d like them to accomplish just aren’t there or, when they are, they’re not clear.

But don’t get me wrong: Dreamweaver is far from being perfect! It’s just that I’m more prepared to miss out on the great new features that keep popping from the new apps, than from the simple ones that Dreamweaver provides me with and that help me code faster.

I’m sorry I won’t be adding any screenshots to this post, I just have to let this out of my system as quickly as I can. :)

The details that matter to me

This list focuses on the way I use Dreamweaver, and that is mainly to code HTML and CSS. I’m aware that I don’t use it to its full potential, so this list could be so much longer, right?

So why do I like it so much then?

  • It adds links to the external files your HTML is linking to at the top
  • The list of colours, assets, links used in a Site
  • It doesn’t close HTML tags as soon as I open then
  • It closes HTML tags if I type “</
  • You get a list of all available CSS classes and ids when you're typing "class=" or "id="
  • It auto-completes the properties in CSS files (yes, all the others probably do that as well)
  • You can add strong, em, or headings, for example, with just Cmd+B, Cmd+I, or Cmd+1
  • If you type "&" in your HTML code, you get a list of glyphs available
  • It doesn't add annoying project files to my folders
  • Search and replace across an entire site
  • The inbuilt FTP: it's not great, but it's OK for quick uploads
  • I can use the tab key to indent several lines of code without the need of a plug-in
  • Update: If you set up a Site, and then change the name of a file (html, image file, etc.), it updates the links to that file within the Site
  • Update: When inserting an img tag, after inserting the source file code, Dreamweaver adds the correct height and width automatically when you type in height and width

People keep trying to convince me to move from Dreamweaver (and sometimes I try to convince myself), but save your words if none of the above mentioned features is present in the tool you’re about to recommend.

I’d also like to add that I don't use Dreamweaver's live preview—I never got used to it because it used to suck (I've heard it's a lot better now though), so I use a combination of Firefox and Firebug to do the live editing.

The details that I don’t love, but that I can live with (or without)

  • The price tag. At almost £400 (or $399), it’s quite expensive and sometimes prohibitive
  • It can be slow
  • It’s not as pretty
  • It doesn’t know which properties have already been used for a particular tag
  • Search and replace could be nicer (like Espresso’s)
  • I’d like to have a more visual navigator (like Espresso, for example), but it has one that serves its purpose well
  • Spelling checker: if there is one, I don’t know where it is (Espresso has it)

Dreamweaver is sad

So please, next time you say mean things about Dreamweaver, think twice, look at how sad it is:

sad dog
Photo by protographer23

What would you like to add? Are you a Dreamweaver hater? Do you secretly use it when no one is looking?
Let me know in the comments section!

There are 52 comments:

  1. Trisha Cupra says:

    Yes, I do use it. But only to do HTML email/eZine designs, which still have to use some tables (which I never use for websites! Unless I am creating an actual table for tabular data).

    I like it because I can paste in an article and it creates all the paragraph tags automatically for me.

    I use it in split view.

    I’m the designer, and Dreamweaver is one of my tools.

    What worries me is when it’s the opposite way around – Dreamweaver is the designer and the designer is the tool! ;)

  2. Clive Walker says:

    I agree with your points and I am also a DW fan. In fact, DW does have a spell checker [at least on Windows], it’s Commands – Check Spelling or Shift + F7.

    The reasons that I like DW include most of that you have said but I also find the DW templates feature [.dwt layout file] incredibly useful and a great time saver. This, together with Library items and other site features like Find + Replace makes it the web coding/site design/management tool of choice for me.

  3. Alex Mahan says:

    I personally use and prefer Coda for nearly all of my coding work. However, we also use Dreamweaver in split view for some tasks (like for editing/tidying complex financial tables such as those found here: http://ar08.angloamerican.solutions.investis.com/financial_statements/principal/index.html) and the site management/link-checking tools are quite good.

    Dreamweaver _used_ to generate horrible/proprietary code, but if you just use it as a code editor rather than as a WYSIWYG tool, it works just fine as long as you’re not relying on its design view for rendering your HTML/CSS. I still hear things like “Ugh. I don’t go near Dreamweaver and I sure wouldn’t want any developers I work with using it either” – actually got this from a job applicant yesterday! – which is a pretty ignorant view IMO.

  4. inayaili says:

    @Alex: That’s just sad, I honestly wouldn’t want to work with someone who’d say that :(

  5. Emily H says:

    I use Dreamweaver for FTP – I can’t find anything else that lets me upload single files from different folders (into their corresponding separate folders) at the same time.

    I also use it for 1 very specific task: writing help files (user guide for CMS). I use the design view or split view then and it is just the best place to do it because I’m mostly word processing (using those shortcuts for bold etc) and I want to see/read what I’m writing as I go, but I’m also throwing in the odd table(not for layout!!), adding images and hyperlinking and all that jazz which DW makes easy.

    For my HTML/CSS coding I use Textmate. I was using BBEdit for the last 5 years but I made the switch to Textmate cos it has an Expression Engine bundle (colour coded, shortcuts etc) and I’m doing a lot of EE dev these days.

    I still end up using BBEdit for a couple things that Textmate doesn’t do, or if it does I don’t know how: comparing 2 documents (finding differences), find (where it tells you how many instances there are) and (randomnly) character count!

  6. Andrew Fox says:

    I struggle with Dreamweaver simply because…

    1. it feels so ‘heavy’ (hey, like most other Adobe apps!)
    2. …and un-Mac-like (ugly little details that look very Windows 98).

    BUT, all those features Yaili talks about are there in DW and are brilliant. People don’t realise it is a great text editor… and sometimes a visual editor can be much simpler than a text editor (for quickly formatting large amounts of text, for instance).

    I used to be equally defensive of GoLive – a fantastic, ground-breaking and misunderstood tool – now gone to the great SVN suppository in the sky.

    That said, I will continue with Coda/CSSEdit and secretly hope they get as smart as DW can be.

    Cheers!

  7. Bastien says:

    Well, I don’t really hate Dreamweaver, I appreciate the fact that writing HTML in Dreamweaver is very comfortable.

    But, writing HTML is as comfortable in Espresso (which is inspired from Dreamweaver I guess), and every IDE has its own good parts.

    The thing is, Dreamweaver is ugly compared to the cute other tools we have on Mac.

  8. LT says:

    I cant wait to get a copy of dreamweaver myself. I dont care what everyone else is doing? Software is like social sites everyone has their preference. Thanks for this informative rant. Your rant cemented my choice to pick Dreamweaver thanks.

  9. Bob Hay says:

    I have never used Dreamweaver and probably won’t just because of the price that you mention. Notepad++ is great and free. I also use Firefox with Firebug and will probably use it more once I learn more about its developer tools. Nice rant and cute pictures.

  10. Johnnny says:

    The only time I have ever *sort of* used deign view in DW was when I was editing content for an HTML email that was in Welsh! I highlighted the text in design view and switched back to code view where my code was highlighted. It sped things up especially as making HTML emails requires tables :-(
    But I do like the tools DW has (find/replace, find opening and closing divs etc…)

  11. I take a lot of crap for continuing to use Dreamweaver, too, but my list looks a lot like yours. I LOVE the site management features. The search & replace is the one I use most often, but getting a warning if I try to delete an image or CSS file that’s referenced in a page is great.

    Emily’s right, too: I haven’t found another tool that lets me upload files from different levels of the directory hierarchy all at once.

  12. rb3m says:

    Hi! Nice article! Although DW isn’t my choice that is more due to my own style than a fault of DW itself. However, I do hate it when people rely on DW to do the work for them instead of learning proper web design and coding principles. When that happens DW becomes a crutch instead of a tool.

    So to any novice in web design I always say “get rid of DW”. When they actually learn how web design works then they’ll be able to use DW as the tool it was made to be and get the best out of it.

  13. Martin Smith says:

    I’d like to see a DW Lite. A completely stripped down coding tool with all the features you listed and none of the additional chaff.

    A stripped down ‘Lite’ price tag would also be nice, but would need to be around $40 to tempt developers away from the likes of Coda, TextMate, Espresso etc…

  14. Olof Fredrikze says:

    I’m using DW for many years but start it up very rarely. I do my coding in TextMate / CSSEdit / Transmit. But for sitemanagement (changing files and folders sitewide) and for editing tables it’s worth to keep the mastodont awake. And somtimes even the compatibilitychecker saved my day.
    When Adobe manages to make an app for handcoders with just the functionality we love in DW without the complete circus with crippled clowns I’m the first to buy it.

  15. Jameos says:

    I’m still rockin’ Homesite…it runs just fine on Vista x64 without any problems.

    • George says:

      @Jameos – What version of Homesite are you using? 5.5+? Do you have Administrator rights on your PC? Did you have to do anything special to get Homesite running? Thanks!

  16. Chris says:

    I think the Dreamweaver stigma comes from the bad old days of the web, when it was competing with FrontPage.

    However, unlike FrontPage, Dreamweaver actually evolved into something useful over time. I use it every day and love it!

    I’d add another can’t-live-without feature:
    Select the path to a linked document, then press Control+D. It saves you the hassle of rooting through folders to find that css or script file you’re looking for.

  17. inayaili says:

    @Chris: That’s a new one for me. Brilliant! :)

  18. Richard says:

    Agree with your comments and sentiment. I am still using the older Macromedia Dreamweaver v8 that is very pleasant to use. Like the HTML close too, and the class/id listings. All helps infrequent coders like me write valid code.

    And installed a couple of DW extensions to help me learn quickly, save lots of time, and look more like a pro coder. :)

  19. Matt says:

    I’m a proud user of Dreamweaver too. I tend to even use the WYSIWYG environment at times! But only really for typing paragraphs / headings and occasionally inserting images.

    I find it’s a good way to select certain elements too before switching to code view where all of the necesarry code is highlighted.

  20. Pedro Heliodoro says:

    Altough I’m more a developer than a web designer, I prefer to develop code in DW, by mainly two reasons: the code colouring ( except when I’m embedding PHP onto a HTML file type ) and expand/contract document blocks.
    DW can be messy when does not render the design mode as stated on the style sheet.
    The Find/Replace feature lacks some type of restraint, like having find and replace files on the site’s root but ignoring some folders…
    And of course… The evil costly price tag…
    I’ve tried NVU in the past, and of course some inline web Rich Editors. Not one of those could cope right with table layout management as DW, ( please don’t flame me for this one, I’m not a table layout fanatic :p ) even in Thunderbird, visual manipulation of tables sucked.
    The snippets folder are sure a handy tool to quikcly set up common pieces of code that are needed.

  21. Cosmin says:

    I’ve used Dreamweaver since I ever started webdesign, and boy did I hate it for a couple of weeks (back in 2006 – DW MX)

    Since then, I’ve been using it for webdesign and newsletter design as well (just tables).

    I never use the split/design view anymore – well only in some cases when I write the code for newsletter designs.

    I guess I chose it because it was more affordable at that time (I was in high school and a friend borrowed me his DW), and am still using it because macs are so friggin expensive :(

    I just got used to it (have tried several others on Windows), and the only one I would try is Coda, just to see if I can perform better.

    One thing I don’t like about DW is that it distracts you by being so cluttered – a coder should only focus on the code, not on a million other buttons and texts that show up in the app.

    Go Dreamweaver!

  22. I use Coda for every project. However, I agree that DW is underestimated.

    I learned to make websites using DW and later moved to text-only.

    I still go back to it for repetitive HTML elements like long list of content and pasting Word docs sent over by clients that need to be converted to HTML.

    Yes, I COULD code a list of 15 items in HTML but why would I do that? I just go into DW and type them out in a few seconds then grab the code and move on in my text editor.

    There’s nothing bad I could say about it because, the features that I don’t prefer… I simply DON’T use. It’s an easy fix.

  23. For the most of the time, i use CSSEdit (that’s one helluva app) for CSS and Smultron for the rest.

    I don’t hate DW, but i miss a updated GoLive. Mostly for the GUI, DW looks clumsy, it does not conform to any other apps UI and so on.. It feels like an X11 app. :)

  24. Nils Holmström says:

    I use Coda exclusivly, and i’d say that it is only minor things in your list that it lacks, but i can understand how those things can be a dealbreaker for some, such as the lack of an “end tag”-function and that it doesn’t show you what classes ar availeble…

    I’d be happy to point out som of the reasons why we use coda at my company:

    - Built-in subversion client. Invaluable on projects were many people are involved.
    - Excelent ftp-client, both for publishing whole sites and individual files.
    - Colors markup in a variaty of languages (not only css and html, but php, javascript and ha whole bunch of non-web related too)
    - Webkit-based preview that works on both static markup and dynamicly generated content (such as php-pages)
    - Snippets of code and/or text readily available, with the ability to add your own. Shorthands are availble for most (write “lorem”, press tab, and presto! you have a nice chunk of filler text.)
    - Blockedit function for indenting text, but also for creating repeating lines of code, such as a list.
    - autocompletion for tags, attributes, css selectors and properties, aswell as javascript functions.
    - easy to create and organize sites/projects.

    With that said, to each his own, and i feel that you should use the tool you feel comfortable, and that it is the output that counts. In my humble beginnings as a 13-ear old wannabedesigner I wrote everything in Notepad…

  25. inayaili says:

    Thanks for the comment Nils. I have tried Coda, and to be honest, I didn’t like it (it *looks* beautiful though…).

    Your points are fair, but DW does a few of them as well (like the syntax highlight — it actually does it quite well, specially on the JavaScript files — I don’t really work with other types of files, other than the occasional PHP for WordPress or some RoR).

    I’m used to using Firefox/Firebug for preview. Because in the old days DW sucked so much doing it, that’s how I got used to work, so I don’t really feel the need for the preview.

    DW has snippets, autocompletion for tags, attributes, selectors, properties *and* JS functions, too.

    I’m not trying to convert anyone to using it though, far from it. I just want people to stop looking at it and at people that use as if they were somehow worse coders, which is rubbish.

    • Nils Holmström says:

      But looks are darn important, why else would we care about stuff like border-radius ;) But in all seriousness, the look and fell is important, i for one work better in a clean and orgaized environment, and that goes for the office aswell as the tools.

      An AS3-developer at my company tried to convince us to use Eclipse, but for all it virtues, it still looks and feels like and java-application from 98 so that was a big nono…

      And, as I said, in the end it’s the output that counts, and i guess that’s why ppl tend to frown upon wysiwyg-editors, since the code generated by the programs usually is (or at least was) utter sheit…

      That being said, I think everyone should use the tool they are comfortable with, and looking down on collegues tool of choice is downright arrogant.

      Thank you for an excellent blog by the way!

  26. lawless says:

    Interesting discussion. I’ve always used Dreamweaver for my HTML since I started coding. I went to work for a large corporation that had a big design team and a bunch of developers. I was used to using DW as my primary tool for coding and uploading via the built-in FTP. The new job had source control/development & staging servers/replication to production… the whole 9 yards. We used an old-ass copy of Homesite. Needless to say the process flow to update a single bit of text in an HTML file was a nightmare. You had to check the file out in source control, open it in Homesite, find the text you were trying to edit in sometimes massive documentation files, save it then manually copy it from Dev to Stage over mapped drives (did I mention this was all on Windoze :( ) then the Replication would run on a schedule to push the files from Staging to Production.

    The first week there I was crying I didn’t have Dreamweaver. You can check files in/out, easily scan multi-column page layouts in split-view then save and FTP into the staging environment all in DW. DW has file synchronization as well in the FTP so it’s warned me many times when I’ve updated personal projects at work and forgotten to pull down the changes at home and nearly overwritten them.

    My first full-time design job was using Frontpage when I first started. Luckily I convinced them in the first week to switch to Dreamweaver. I agree that Frontpage/Dreamweaver association forever tarnished DW reputation. FP was a true abomination.

    One thing I do like and find extremely useful is in Find/Replace you can click on the results and it will open the file and take you directly to the search result. I’m constantly doing sitewide Find/Replaces on sites with thousands of files and it saves me massive amounts of time.

    BTW, spellchecking is under Text-Check Spelling, been there as long as I can remember. You can do the whole document or highlighted sections.

    There’s a lot I DON’T use in Dreamweaver, but the things I do use, I use on a daily basis and having it all in one program simplifies things greatly.

  27. lawless says:

    Holy shit, that was a long ass comment. Sorry about the rambling…

    • inayaili says:

      Thanks for commenting.

      I’m glad to see that a lot of people use and like DW, I wish they’d be more upfront about it when talking among peers. I even received some comments to this article via email because some people didn’t want to make it public they like/use it :(

  28. Qoska says:

    Functions vs. price it’s not equal to price vs. functions you will use it.
    So why pay around €500 for a tool that you will only be using 20% of it’s “potential”?

  29. lawless says:

    In response to Qoska:

    Because it’s a tool I’m very proficient at and am comfortable using. The price is very low when looked at from a time-savings perspective. The difference between DW and something like Coda is only $300US. That’s less than a day’s worth of hourly wage coding. So I’ll see a return on my investment quickly.

    As I mentioned in a previous comment, you can use multiple other tools (even many free ones) but there is a time savings to:
    1. knowing the software and being comfortable with it
    2. having all your tools in one package.

    With that said, I’ll also admit I use Fireworks for my web graphics versus Photoshop. My time is worth money, the tools that allow me to work the quickest allow me to make more money doing what I do.

  30. Qoska says:

    @lawless,

    I agree with all that you said. We should all use what we’re comfortable with and not what the “gurus” advocate. My point is, that for someone who’s starting in the coding realm, DW isn’t the best option in terms of what I’ve said above and even for “how-to-code-properly” because all the distractions ( functions ) the tool has.

    On a side note, I to use fireworks for my web design. It’s a matter of using the right tool for the right job.

  31. rpr says:

    The fact that you wrote this article Inayaili, proves a point?

    The main reason people make disparaging remarks about Dreamweaver stems from their ignorance. They can’t be bothered to learn how to use it properly.

    Dreamweaver is easily abused, but so can any application.

    It’s the best tool I’ve used for CSS management:

    Right-click a CSS rule on the ‘Rule’ list, to go straight to rule code.

    Drag ‘n’ Drop, rule order.

    Automatically warns on CSS Browser compatibility issues (90% IE6, which we’ll be able to ignore very soon).

    Drop-down list of CSS Classes, that can easily be attached to HTML elements.

    Ignore those who are ignorant I say!

  32. Taufik says:

    Dreamweaver helps me to build tables !!

    It is easier to build tables on Dreamweaver than using notepad or whatever-it-is..

    Otherwise, DW GUI sucks (I say it honestly)

  33. Elijah says:

    I am using DW cs4, it’s fine. i accept your post!

  34. RobUK says:

    It’s been a while since this article was posted, but just wanted to say that I’m in complete agreement, and love DW for all the same reasons as you!

  35. Charlie Matar says:

    Thank you so much for defense Dreamweaver!.

    I’m using DW since 2000 and always have work for me.

    -Love the way you wrote articles.-

  36. Igor says:

    Absolutely, DW is a greate tool for thouse who “Can” code. In addition to what have been said, I’d add that it allways upload changed file automatically in right folder on server. You dont have to worry where it goes. I wish it aded links to “included” .php files

  37. Hussain says:

    Dreamweaver is a nice tool

  38. Eric says:

    I learned (still learning actually) coding through Dreamweaver. Being able to see what it looks like on Firefox, helps me to look at it as code in Dreamweaver. While at the same time allows me to work/tweak the code right there and then.

    To each there own I guess, but it works for me, and I’ve been able to design some decent web pages with Dreamweaver.

    By the way I’m a graphic designer, not a web designer. But I do like to learn other aspects of the design field. Plus, it’s nice to get as a freelance gig. ;-)

  39. SKBrn says:

    I used to like DW waaaay back in version 3.0; however, now I avoid it as much as possible. Why? Because as others have said, I’m a designer, not a coder…and Adobe has made DW way too code-centric.
    Also, DWCS4 has sad site management tools, especially compared with the other visual web site design tool, GoLive. I love that I can diagram a complete site, send it off as a PDF to others for comments, and then create all the pages (with links) with just a click of a button.

    It just seems odd to me that we are still hand coding so much; it’s like we are going back in time instead of progressing. Sort of like going back to the early days of wordprocessing when one had to insert tags or code to make a word italic, or to start a new paragraph, etc.

    I hope what I’ve written makes sense, I’ve been up for 48 hours trying to decide on a design ‘look’ for my own site. Pathetic that I can’t make up my mind.

    Scott

  40. PGabor says:

    I love Dreamweaver. The reasons I use it on a daily basis:

    - Snippets. I have a bunch of own and when it comes down to repeating code (CSS global reset, conditional comments, meta section, comment forms, etc.), using of snippets could really speed up the process
    - Built in validation tool
    - Sitewide links checking tool
    - Collapse / expand chunks of code
    - Find and Replace

  41. Right on! So glad to read sound defense of a great tool that also integrates with Fireworks and can create clickable mockups/wireframes really easily. Due to what all my current coworkers use, I’ve become a Textmate/CSS Edit/Transmit person, but DW is a great tool–and has saved my bacon more than once by helping me to see where I failed to close a div, thanks to code highlighting via clicks in the tool bar at the bottom of the document. Textmate is useless for that.

  42. I’m always amazed at the passion these discussions drum up. I guess it’s akin to rooting for your favorite football team. My team is better! No! My team is the best! But when you step back and put them all in the same white shirts and black shorts. There are the same number of players kicking around a ball. It’s what they do with the ball that matters. If you doubt me read the flaming comments surrounding any HTML5 vs Flash story.

    I guess what I’m trying to say is that Dreamweaver, Coda, Textmate and all the rest are just tools. It’s the man or woman behind the keyboard that makes the difference and always has. Someone using GIMP can produce a superior design than someone using Photoshop. Provided that person is more talented and more familiar with the application they are using.

    So In closing, use the applications that work best for you. I started out with Dreamweaver 1.0 and used it until I wasn’t getting the results I wanted, in the time I wanted them. Moved on to Textmate, Transmit and CSSEdit. Used that for a while, got tired of the problems with these three and then moved on to Coda. I’ve been using Coda since it came out and will continue to use it as long as it works for me. When it doesn’t I will figure out what does and move on.

  43. Chris White says:

    Hey,

    I too was a Dreamweaver user and i swore by it above any editor. But eventually i grew tired of the lack of PHP support and PHP hints so i eventually tried a handful of editors.

    These included Netbeas, Zend Studio, Komodo and others.

    All of them are either too slow or lack the management tools i required. No editors have any kind of file management on the level of Dreamweaver, and i could not find one that had FTP built into it effectively.

    However, i did stick with Komodo Edit. The only thing i really miss is Move/Cut/Copy/Paste which all seem to work but actually do not. I could get the Komodo IDE but thats not free :)

  44. ChrisR says:

    Chris: These days, DW has extensive support/live preview of php and even, from what I’ve read, WordPress php and templating system.

  45. logiic says:

    Back in the day, the people in my world were using FrontPage, and so after throwing up, I found myself in an agency with a guy that said the magic words “Here, try Dreamweaver”. That was 1998 I believe. I use it today in split mode, and of course keep all my styles properly tucked away in css files, and I don’t leverage much of the code that DW spits out if I decide to utilize an extension.

    I am sure there are other better products for editing CSS/HTML sites, but I just feel at Home with Dreamweaver, and still refer to it as Macromedia Dreamweaver *FU ADOBE* (grins)

  46. I have used different HTML editors but definitely Dreamweaver is the best. I do like Komposer (it is in Ubuntu repository) but it is far inferior to Dreamweaver. There is a grammar spelling in Dreamweaver. In the Commands menu choose Check Speller (the shortcut is Shift+F7.

  47. The only time I’ve used design view is for image maps on older sites, it’s much easier to just drag them to where they need to be.
    But other then that, its code view only. We deal with 500 or so sites across multiple servers, so the built in FTP is nice too.
    I’m sure there are other tools that could replicate my setup, but I think I would lose time.

  48. Mike says:

    I’m hoping that some people that use Dreamweaver still visit this blog.

    Sometime ago I discovered that my original Webmaster is no longer available and is not able communicate with me. My site is now in need of some serious maintenance due to changes in external data source locations, and the data formatting for input into the MySQL database.

    The dynamic site that he had created for me many years ago (2004) was done in Dreamweaver, and has always worked great. It has 2 major components that I’m aware of: The main Web Site and a MySQL database. Each of these are hosted on separate servers and from what I understand there is a Coldfusion triggering mechanism (task scheduler) that controls when the data is imported to the database from the selected Web sources.

    I’ve given some thought to what the best approach might be to getting the site completely functional again. I thought about either finding someone in my area that has a working knowledge of Dreamweaver or trying to repair it myself by attempting to learn this program. I came across the ”Sam’s Teach Yourself Dreamweaver UltraDev4” in the library and before I go any further I wanted to get an opinion. I haven’t gotten the actual DW program as yet.

    Should I attempt to perform the required site maintenance by learning this program, or seek help from others who are more experienced?

    My Web hosting company has assured me that I can gain access to all of the files containing the Web content through an easy to use FTP client program like FileZilla. From what I’ve read here it seems that DW also has a built-in FTP application.
    Thanks
    Mike

  49. Neil says:

    I use dreamweaver and I think I haven’t used it in design view for about 7 years now. I code everthing HTML, CSS, Javascript, jQuery. I use it becuase it’s what I used when I first started designing. I’ve tried aptana, komodo but never really liked them.

Leave a comment: