Slashdot Mirror
Dreamweaver Is Dying; Long Live Drupal!
Barence writes "Here's an interesting blog post by a designer who reckons Dreamweaver is dying. It's not Dreamweaver's fault, though. Nor is the problem Adobe and its development team — the last Dreamweaver CS4 version was the most impressive release in years. Moreover, although Microsoft Expression Web poses a far more credible threat than FrontPage could muster, Dreamweaver remains the best HTML/CSS page-based editor available. The real problem for Dreamweaver and for its users is that the nature of the web is changing dramatically."
I highly doubt this, I check NetCraft daily, and I've seen NO confirmation of Dreamweaver dying!
Congratulations on getting first post. A copy of Microsoft Windows Live Expression Web Express Edition is in the mail.
I've never tried it, when I do web design I do it with Gimp, Vim and Firebug. And I think that combo works great!
How do Dreamweaver compare to Vim? Is it advanced enough to not fool users to use css styled text for strong expressions?
Drupal et al make life a whole lot easier when it comes to updating a website and adding content. But what about the design?
Unless you want to stick to the default Drupal (or insert CMS here) themes, you'll probably want to design your own CMS template so people get a unique feel for your website. You'll still need to fall back on your classic static web-design skills using programs like Dreamweaver (or notepad).
Dreamweaver isn't dying, it's just falling into a more specialized category now. If you just used Dreamweaver as a way to update content, then you were really failing to use the program to it's full potential.
It's true, most people who make sites in Drupal, Wordpress, etc. clearly didn't spend more than 10 minutes on the design.
There's no -1 for "I don't get it."
Even Microsoft already did what had to be done for that. Integrate the tools with the content management system, duh!
Sharepoint Designer is pretty much Expression Web made to modify Sharepoint's dynamically generated pages. Point Sharepoint Designer to a Sharepoint site where you have required permissions, and have fun. All the power of a content management system, all the power of design and web development tool, all at the same place.
Adobe and Dreamweaver are in an even better position for this. They could work with the open source community, and various vendors (like Alfresco), and make Dreamweaver work the same way Sharepoint Designer works, but across a variety of content management system. The idea of something like Drupal and Alfresco with Dreamweaver having the same kind of integration as MOSS and Sharepoint Designer is quite exciting, in my opinion, and has far more potential.
Am I doing this right? The whole comparing 2 different things?
Veryu misleading title. The story isn't about Dreamweaver but the dying of static HTML editing tools of any kind, contrasting them to the changing web. The web is becoming more dynamic. Some HTML editing tools are very static. Therein lies the problem for the old tools.
Well, developer has utmost freedom to redesign theme from scratch or mod currently available ones, here are some websites done in drupal, check it out:
more here and here.
I completely agree however, drupal != dreamweaver.
o_O
Dreamweaver will always have a place next to microsoft word for helping moms everywhere create hideous, 1990's-era web pages.
Posted anonymously because I have one of those moms, and I'd hate to break her heart. She things her pages are awesome.
I've seen some of the HTML these tools (Frontweaver, Dreampage, HotMetal, etc) produce, and I Do Not Want It.
I use Emacs and w3schools, and my HTML is clean, scalable, efficient, reasonably accessible, and very maintainable, and honestly I don't spend that much time on it. HTML is, fundamentally, very easy, once you know what you're doing.
In terms of keeping all the pages on a site updated with side-wide changes, I mostly use a combination of keyboard macros, custom elisp, Perl, regular expressions, chewing gum, and bailing wire. But it works, and it works the way I *want* it to work.
As far as Drupal, though, I thought that was a CMS. Do people really try to use it as an HTML editor? Ugh.
Cut that out, or I will ship you to Norilsk in a box.
From the blog post:
The bottom line is that the old model of the central webmaster hand-spinning every page of every website and, worse, manually adding the navigation necessary to help users find it, just isnâ(TM)t scalable or viable. The only feasible course for the future is for content to be posted by the content contributor, whether thatâ(TM)s the site owner or site visitors, and for the best possible navigation to be constructed around that content on the fly.
This particular paragraph leads me to think the author has never actually used Dreamweaver - he certainly doesn't even understand the fundamental concept of "templates". I mean, who is manually adding navigation to a large site on a page by page basis?
Thing is, there are a lot of circumstances where "Web 2.0", in the limited sense the author seems to understand (that is, end-users providing added content), doesn't do much for you. There are only a few places on your typical corporate or government web site, for example, where this would make sense. Certainly there are specific applications where this would be handy; but they're fairly narrow and can be handled well by adding some wiki software alongside the "mainstream" website.
Now the tools of Web 2.0 - e.g. dynamic, javascript-driven pages with sql backends - are a different matter. But really Dreamweaver-style templating works just fine with those, IMHO, to the degree one is going to use any tool to make those pages anyway (meaning there's a significant amount of hand-coding happening with the page-specific content).
Personally speaking, I've found Dreamweaver templates (that I've put together) very handy when combined with Contribute. Really the templating is mostly what I use it for; both for allowing other staff to easily maintain content and letting me easily push section-wide and/or site-wide changes to our several-thousand-page web site (templates can be nested, which is quite handy). I know I'm only using a fairly restricted subset of what all Dreamweaver can do; but it does that pretty darn well. Certainly other software can also do this - but I haven't seen anything that works quite as well in all regards.
#DeleteChrome
Yeah, this entire thing just sounds like FUD. Granted CMS's are the way to go for content updates but but unless you're a mom and pop shop you don't want to stick with a template... and that means hiring a designer... and that means using design tools.
CMS is just a fancy way of saying, "Keep the secretaries out of the friggin' HTML because they always screw it up." Handing Dreamweaver over to someone with no experience was always a joke.
You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.
the best html/css editor is any editor with syntax highlighting used in combination with brain.
I'm just saying dude, that nobody died and made you Emperor of the Internet so you know, we're all perfectly able to mess around and build our own websites even without your permission. And even without knowing everything there is to know about CSS and HTML. Farkknocker.
Enjoy your Karma, after all you earned it. Feel your Karma Joe, feel it burn.
Architects no longer needed due to rise in demand for modular homes.
Ridiculous, right? My point exactly.
Dreamweaver was great if you want to code ColdFusion, Flash, and Flex. For a full IDE it beats Visual Studio in many features. Eclipse and other free "IDE" don't come close in terms of responsiveness and user friendliness. The problem is CF/Flex is a small percentage of the web compared to PHP, ASP.NET, Java, and a host of new platforms and frameworks (Django, ROR, etc.). Now with the advent of open source CMS and wiki systems, even for .NET, plus free plug-ins for Eclipse to code just about anything, along with shrinking IT budget, WHY would anyone pay the equivalent for full VS for it? The Server + IDE has been Adobe's bread and butter for years, that's why it's critical for Adobe to keep pushing for AIR/Flash. The only way to make DW popular again I can see is embrace open source languages and new frameworks, and lower the price.
A designer might need Dreamweaver
Anyone doing design (artwork rather than page layout) isn't going to use Dreamweaver. It's great as a WYSIWYG html editor. From a design standpoint, it doesn't do much else. No raster or vector creation (unless you've decided to try the Celik CSS polygon method).
The only people I know who still use it are coders who find the extra features it provides in terms of editing and site management useful. In this sense, the article is quite correct -- Drupal and Wordpress and other software are eating away at the market that used to see Dreamweaver as the option for editing webpages without knowing HTML. Now CMSs do that.
Given that Dreamweaver really isn't a design tool either, usefulness as an IDE is pretty much the last thing Dreamweaver really has going for it.
Tweet, tweet.
As alluded to in my post, it allows me to see a list of CSS properties (in a drop down that can easily be ignored), and then once I typed in the property, it gives a list of appropriate values.
It does not make things quicker, it helps me keep track of the correct properties and values, since I don't do it enough to it all perfect, and it is quicker than browsing a reference site to see, "what type of border styles are there?"
It does not interfere with the performance at all for me, and it does not obscure the text I am typing. And I can certainly click the dark green on the color wheel it pops up quicker than I can come up with my the hex values (though I bet dark green is a predefined color, I would know if I were typing this in dream weaver).
We don't all do this all day, yet some of us need to do it sometimes. And with a pretty good grasp of the concepts (better than a lot of designers I am willing to bet), the auto-complete helps fill in the details (that I have worse than most designers), and it does it quicker than using the web for a reference (which I do at home), or even the giant O'Reilly CSS reference book by my desk.
If you don't have access to DW Screem has a pretty decent start to it. When you type less than, it pops up a list of tags instantly, in DW this list shrinks as you type. That's not too useful, but when you hit space, it pops up a list of attributes, and only ones that apply to the tag you just types/picked. This makes it easy to see what you can do with a div, or a span. These are things that take a lot of time to just "know", so the fact that your editor does it can be helpful for beginners, or people who don't do it day in and day out.
DW does it far better than screem (it works with CSS for starters), and that is worth something.
Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
When was the last time Dreamweaver gave you standards compliant code (Actually, as a slashdot user, you probably never used Dreamweaver
You might be surprised. I definitely prefer Vim myself, but at my last full-time job, most of the other coders used Dreamweaver and periodically, I'd fire it up... either because I found myself doing something where it was kindof nice to be able to interact with the page visually, or just to understand what the other guys liked about it as a tool and how they used it.
To my surprise, at least with Dreamweaver 8, the code was pretty standards compliant. You could set which doctype you wanted for your (X)HTML, CSS support was decent, and could set it to warn you if you did something that violated the standard. Heck, I think you could actually even set it up to validate arbitrary XML documents.
There were some other nice features. It's sortof nice having an integrated FTP client to save you a trip to another app, the sitewide search and replace function was certainly a little friendlier/convenient than some of the unixy ways, "clean up word html"...
I don't miss it all that much myself, but honestly, I can see why some coders see it as a good tool to work in. Maybe that'll be enough to save it as a product.
Tweet, tweet.
1. Designer - Design tools such as Photoshop, illustrator etc (not my role!)
2. Front end developer - Photoshop (for slicing and dicing PSDs supplied by the designer), text editor (I'm using Geany at present) and lots of browsers.
This is pretty much the process I've used when I've been involved on the client side, and while it can have its problems (many designers who've never actually had to code a site have trouble groking liquid layouts and other web-centric design issues), it seems to be the best setup. People who are good coders and talented in both art and visual communications are rare, so it makes sense to divide the labor.
The one thing that surprises me about this process, though, is that almost everyone uses Photoshop to do the artwork. This seemed like a basic fact of life to me, until I ended up working at a shop that did everything in Illustrator, and I was surprised to find out how much better this setup was -- not only did the artists seem to be more productive, the vector artwork seemd a lot easier to take apart however I saw fit as a coder. After working there for three years, it's been kindof painful going back to working with PSDs, and I wonder how much of the industry has every tried both given the apparent advantage of Illustrator...
(And this is to say nothing of Fireworks. I mentioned it in the parent and don't want to sound like a broken record, but if Illustrator is better than Photoshop for this stuff, Fireworks is another 10 times better -- it's all the good stuff about both integrated into a program expressly designed for making websites, and it's so good at its job that I don't understand why its product cousin Dreamweaver gets all the fame.)
Tweet, tweet.