Dreamweaver MX 2004 for Mac OS X
Pages: 1, 2, 3
Use the New CSS Style dialog box to assign a new style class for an individual page, or create a new style sheet.
The new style appears in the Property inspector's Style pull-down menu, and can be applied to any text on the page.
Dreamweaver's new features make style markup easier and more convenient. The CSS Properties panel, which shows you selector properties, appears in a Rule inspector whenever you select a style from the CSS Styles panel. You can see properties in list or category view, and you can edit properties right from the panel -- no visits to the CSS Styles dialog box.
Select any element on the page, and a new Relevant CSS panel appears as part of the Tag inspector. Relevant CSS is a two-part panel: one part highlights the element you chose on the page, while the other part reveals its properties and lets you edit them right in the panel grid. When you apply edits, you will see the change immediately on the page. The panel will indicate any CSS styles that affect the selected element.
New Browser Validation Feature
The Target Browser Check feature lets you check your site against a wide range of graphical browsers, and assures that your site is designed for its audience.. Choose which browsers you want to test by accessing the Settings command via the Target Browser Check button.
The Target Browser dialog box lets you choose which browsers to test.
Then, from the Document menu, click the Target Browser Check button pull-down menu to check errors for a page or site, or to add further settings. This utility runs through your code to identify which tags and attributes are not supported in the browsers you chose. The results are available from the Target Browser Check panel of the Results inspector.
The Target Browser Check panel gives you a line-by-line analysis of all non-compatible elements. It offers a plain-English guide containing detailed explanations about the errors. Clicking anywhere on an error report highlights the error in your page code.
An error preceded by a red stop sign indicates a serious problem. A yellow warning icon lets you know that certain code may not display correctly, but that there are no serious display issues. An informational message tells you that code may not be visible, but that it will not affect how your page displays.
Other Neat Features
Some other neat features include customizable syntax coloring, reference books, coding aids, and a customizable tag database.
Those who have used BBEdit know how convenient color codes can be. Slogging through a sea of black type is not my idea of fun. Dreamweaver, with or without BBEdit integration, lets you custom color your code.
Under Dreamweaver-->Preferences, choose the Code Coloring category. Choose any scripts and web languages that you use to set up a color scheme for your documents.
While you don't have to be an HTML wizard to use Dreamweaver, you can use its built-in reference panel to bring yourself up to speed. The O'Reilly Network (publishers of this web site) has contributed complete versions of its reference works on HTML, CSS, JavaScript, ASP.NET, PHP, and SQL. The reference panel also includes Macromedia's ColdFusion references, UsableNet's accessibility reference, and Wrox's ASP 3.0 and JSP references. To access them, choose Window-->Reference to bring up the Reference tab in the Code panel group.
Hand-code faster and more accurately by invoking Code Hints in code view. Generally, you can find the place where you want to add code. When you type the open bracket, clickable code hints automatically appear.
Control-clicking a selection in code view brings up a contextual menu that you can use to tweak your tags.
Tag libraries (located in an XML tag database) are an easy, visual way to manage your collection of tags. Use the tag library editor to add, edit, and delete tag libraries, tags, and attributes. You can also import custom tags into Dreamweaver to make them part of the coding environment. When a tag is part of the program, it appears with its attributes for coding and editing. A plus (+)/minus (-) interface lets you add and delete tags easily.
Use the Tag Library Editor to set properties and edit tags and attributes. Select a tag to see its properties.
Performance Issues Are Problematic
Dreamweaver MX 2004 is a different world when it comes to visually designing and coding your site. However, be aware of some issues that have arisen for OS X in the initial release of this version.
First, there are some disappointing kinks in performance in Jaguar. For example, launching the program seems slow; it seems to hang before finally launching. Then, some commands, such as opening and closing documents, switching documents, FTP, and various other common functions, initiated a spinning beach ball for varying lengths of time. Launching the application and other functions seem snappier in Panther.
There are also a few glitches in customizing the workspace via panel groupings. It is sometimes awkward to expand some panels past a certain point. A Maximize command opens a panel to its largest setting, which is not always necessary. There are limits to grouping certain panels together, too. You can't just tear off any panel and group it with any other one, as some choices are dimmed out or do not appear.
Anyone can appreciate the need to conserve paper and save on printing costs, but Macromedia should include a free, printed instruction book with the program, in addition to the 800-page (9.1 MB) PDF.
Those who installed or plan to install the program in Jaguar, and then upgrade to Panther using the "Archive and Install" or "Erase and Install" features, will need to install a patch from the Macromedia web site at http://www.macromedia.com/support/service/ts/documents/mac_archive_install.htm. Otherwise the program will not launch.
If you are looking for a change, the best way to go about it is to download a free tryout and see how it works for you.
Jackie Dove is a technology writer, editor, and software reviewer specializing in digital art, Web design, the Internet, and of course, the Mac.
Return to the Mac DevCenter
Do you have additional tips or insights about Dreamweaver MX 2004 for the Mac?
You must be logged in to the O'Reilly Network to post a talkback.
You must be logged in to the O'Reilly Network to post a talkback.
Showing messages 1 through 37 of 37.
-
Well all the complaining should cease now...
2004-03-24 09:44:18 odueck [Reply | View]
On 3/11 Macromedia released an update for both the Mac and Windows versions of Dreamweaver. The performance improvement on my Power Mac G5 is incredible. I had been getting very fed up with Dreamweaver's slow speed and had been contemplating switching over to GoLive. Needless to say my faith in Macromedia has been renewed.
-
Another (re)view of Dreamweaver 2004
2004-01-21 09:26:47 dznr [Reply | View]
I wrote a real-world review of DWMX 2004 recently, posted here:
http://www.exuberance.com/notes/2003/dwmx2004.html
A wonderful new bug I came across is DW's ability to TOTALLY ERASE MY FILE when it crashes.
I have isolated the crash+erase to occur consistantly in pages after I make an edit in the meta description in the Properties window. I have tested this on both template-based and stand-alone HTML pages.
I have hacked my HTML template to allow page-by-page editing of meta keywords and meta description, by inserting by hand the DW editable region tags in my template Here is my meta description, with my hand-inserted editable tags in place:
<!-- InstanceBeginEditable name="metadescription" -->
<meta name="Description" content="this is the description text" />
<!-- InstanceEndEditable -->
DW crashes after I make a change to the description, in the Properties Inspector window, then click in the document, then either preview (which will ask me to confirm a save) or save. Even if I take a template-based doc and "detach from template," the bug is easily reproducible.
I have tested, and can confirm, that the app will NOT crash if I edit the meta description in code view or split view. The crash only occurs when I edit in the Properties window.
-
DW MX04 on Panther way too slow
2004-01-17 08:35:22 anonymous2 [Reply | View]
I used DWMX and Flash on Jaguar with no problems on my powerbook G4, but the performance of DWMX04 on my new G5 Panther is unacceptable. Opening documents hangs for several seconds, typing text is even slow. The panels have a mind of their own. Dreamweaver MX 2004 for Mac OS 10.3 has made web design painful.
I have been a Dreamweaver supporter since it first came out, but last night I spent a little time looking how I can utilize GoLive. It looks much more stable and offers more features. If anyone has migrated to GoLive from Dreamweaver please post a note. I want to make sure the templates and library items can be transferred without recreating them since static html pages seem to be no problem.
-
MX04 on Panther
2004-01-17 08:33:31 anonymous2 [Reply | View]
I used DWMX and Flash on Jaguar with no problems on my powerbook G4, but the performance of DWMX04 on my new G5 Panther is unacceptable. Opening documents hangs for several seconds, typing text is even slow. It has made web design painful.
I have been a Dreamweaver supporter since it first came out, but last night I spent a little time looking how I can utilize GoLive. It looks much more stable and offers more features. If anyone has migrated to GoLive from Dreamweaver please post a note. I want to make sure the templates and library items can be transferred without recreating them since static html pages seem to be no problem.
-
Does it upload to dot mac?
2004-01-17 04:43:40 anonymous2 [Reply | View]
For months I've waited to know this. Since dot mac gave a discount on MM Contribute 2 which was my first foray into web design. The ease of designing and uploading to my dot mac account with C2, I posted to the MM forums-emailed MM with never a response to the question of Dreamweaver MX 2004 can upload to dot mac. Anyone know?
-
Root level?
2004-01-16 16:52:10 anonymous2 [Reply | View]
"Make sure your site and all its folders -- including web pages, images, CSS files, templates, and rich media files -- are located in the root folder of your hard drive."
For anyone considering DW who might be alarmed by the above statement, don't worry -- it is not true. The program doesn't require you do this. Your site can be anywhere, but within the site's folder, the folder structure must match the structure on the web server. Standard practice.
-
Macromedia worst software for Mac ever
2004-01-16 07:25:06 anonymous2 [Reply | View]
I was a hardcore Dreamweaver/Flash user at work and home for several years. Eventually I shelled out the money for Studio MX for OS X. After using this atrocity for the last year and half, I will never buy another Macromedia product again.
Dreamweaver and Flash MX were filled with - at least - 100 bugs, irritants, performance issues and duplicable crash scenarios. They are hands down the two worst 'big name' app released for OS X yet.
My theory is that Macromedia is fast becoming a PC-only company, and since they developed both OS 9 and OS X versions of each app in the original MX series (a stupid decision for sure), corners were cut. Even more unforgivable is the fact they refuse to fix their bugs and release . upgrades.
Knowing Macromedia's track record first-hand, it really
bothers me when I read reviews like this, Not only because you're being positive about what is reportedly a very negative product (I've yet to use MX 2004), but more because it forces me to ask, "If O'Reilly gives high marks to a product company this bad for the Mac, what else about them can't I trust?" -
Macromedia & Tim O'Reilly
2004-01-16 08:13:10 anonymous2 [Reply | View]
Keep in mind that Tim O'Reilly is now a member of Macromedia's Board of Directors. -
Macromedia & Tim O'Reilly
2004-01-16 10:48:22 anonymous2 [Reply | View]
Wait a minute...
1 Tim O'Reilly is on the BoD of Macromedia.
2 A glowing review of a new MM product appears on his website.
3 From the looks of the comment board, the review is completely off-base, as the app in question actually has significant performance issues on the Mac.
I smell a rat... -
Re: Macromedia & Tim O'Reilly
2004-01-18 14:05:34 Derrick Story |
[Reply | View]
Are you kidding?
First of all, you must not read this site much or know much about how we work. Tim's activities with Macromedia have no influence what so ever on the text posted on Mac DevCenter. The review posted was the opinion of the author, Jackie Dove, who is not even an O'Reilly employee. She does coordinate reviews for Macworld Magazine, so she has some experience at doing this.
And, Jackie closed her review of Dreamweaver's features with a caution about its performance.
I contributed a talkback a few days ago thanking readers for cautioning others about how this software runs on Mac OS X based on their experiences. I think the totality of the message (article plus talkbacks) are a very fair appraisal of this application.
No rat here. The process is working exactly how it should. -
Macromedia & Tim O'Reilly
2004-01-16 10:46:22 anonymous2 [Reply | View]
Then Tim's either jumped on a ship departing for PC waters, or he's got a lot of work to do to get them delivering decent Mac apps again. I hope it's the latter, but I'm not holding my breath. From the MM reps I've seen at conferences, the company is littered with arrogant pricks that have no interest in anything that's not from Microsoft.
And I'm not saying this as a Mac zealot, just as a very disappointed MM customer. Either sell me something that works as advertised on my platform of choice, or don't sell it at all, but do NOT sell me a half-assed product and expect me to come back for more.
Still, maybe Tim will set them straight.
-
Features vs Performance
2004-01-14 16:40:02 Derrick Story |
[Reply | View]
I don't use Dreamweaver myself (and by the looks of the reader comments don't plan to in the near future).
As I scan the talkbacks it becomes clear to me that you can add all the new features you want, but if the application doesn't perform on par with others in its class, people won't buy it.
Thanks to all who have contributed comments that will hopefully save many others from a painful experience.
-
dreamweaver mx 2004 is a piece of crap
2004-01-14 16:12:12 anonymous2 [Reply | View]
I wonder if the author really did some serious work using dreamweaver mx 2004. I bet anyone who used it for 10 minute will say the speed is too slow to tolerate. Time wasting on waiting for the application to response is much more than time saved by any new feature introduced in this version. If they cannot do it right, then don't do it.
-
SFTP support?
2004-01-14 11:30:57 anonymous2 [Reply | View]
Dreamweaver MX supports FTP access to the "live" site, which makes synching files wonderfully convenient. Unfortunately, there is no support for sites which are configured to be updated thru secure FTP.
Has this support been added to the new version? It's the only thing that would compel me to upgrade.
----
Obbie Z
La Crosse WI
-
Performance Issues
2004-01-14 10:59:00 anonymous2 [Reply | View]
I bought the 'upgrade' without downloading the free demo version - my bad. Within a few days I was re-installing Dreamweaver MX and got a refund. I wasn't impressed in the least.
While Dreamweaver MX certainly had issues for some users running Jaguar the 'new upgrade' is worse and under Panther it might be slightly better but it's not much to write home about.
Macromedia's customer service is of little/no help with this problem and the Macromedia User to User Forums are moderated by clowns whose first response to these performance issues is to question whether you're running a pirated copy - laughable.
Back to the drawing board folks................ -
Performance Issues
2004-01-15 17:30:18 dreamweaver [Reply | View]
We hear you. We've been looking issues with Dreamweaver MX 2004 since we shipped and are working away at a dot release that specifically addresses performance issues. It should be coming out shortly. In the meantime, if you want to provide specific feedback on performance issues you are seeing, please review our tech note and fill out the performance survey we are conducting.
Thanks!
Jen Taylor
Product Manager, Dreamweaver -
Performance Issues
2004-01-16 10:39:10 anonymous2 [Reply | View]
No offense Jen, I know you're just doing your job, but Macromedia DOESN'T hear.
I've personally put in many, many bug reports to Macromedia regarding the last MX apps and never got a word in reply, much less a FIX for the bugs, so don't come on a board to defend your company's name and try to tell me that Macromedia cares about its Mac customers because it's plainly obvious that Macromedia doesn't give a damn about their Mac user base. If they did, we'd have had bugs fixed in the last MX round, and this current kludge would have never made it out of beta.
As for the tech report offer, I'm done being your beta tester because I'm done being your customer. -
Performance Issues
2004-01-25 02:43:07 Crag [Reply | View]
Here! Here!
The company i work for purchased 4 copies of DW MX04 upgrades before their actual release. We put our trust in Macromedia and got burned.
We've replaced all 4 copies of DWMX04 with DWMX and we are now searching for a better solution. Adobe GoLive is being considered.
Considering some of the bugs I can't believe Macromedia tested the product on a Mac. Cause after using it for a few hours we all gave up. DWMX 2004 is not stable or useable on OSX (10.2 or 3), (we use PowerMac Dual G4 loaded with 2gigs of Ram). Do not be fooled by the O'Reilly review. Don't waste you money.
Franly I am somewhat shocked that O'Reilly allowed this review to be posted on their site. O'Reilly you should be embarassed! -
Performance Issues
2004-01-15 12:05:43 anonymous2 [Reply | View]
How did you manage to get a Refund?
I too just baught the Studio MX Upgrade right away, trusting the usual quality of Macromedia Products, but dreamweaver MX 2004 is just a bad joke. A nightmare to work with constantly waiting for the app to get its brain arround. Most definitively also cause by the use of Opera as the rendering engine and this even as MacOS X has this beautiful WebKit already available for developers...
Please email me with how you managed to get the refund at: oreillydreamweaver[ATSIGN]index-s.de
Thanks
Stefan Seiz (www.stefanseiz.com) -
Macromedia's Return Policy
2004-01-15 12:57:03 anonymous2 [Reply | View]
Stefan
Here is a link to Macromedia's Return Policy: http://www.macromedia.com/support/service/ts/documents/return_info.htm
Up to 30-day money-back for most situations.
Never, ever again will I purchase any software from Macromedia or Adobe Systems without downloading the demo first and even after doing that I think it's wise to scan the user-to-user forums to see it's working (or rather not working) for other folks.
Just my opinion..........
JB
-
Performance Issues Are Problematic
2004-01-14 07:22:44 anonymous2 [Reply | View]
Performance issues are more than problematic: Dreamweaver 2004 MX is completely unusable on my G5. I would rather not have the updates and work in my old version if it is so slow. This is inexcusable. So please save yourself the $400 to upgrade. -
Performance Issues Are Problematic
2004-01-14 16:31:13 anonymous2 [Reply | View]
I made the mistake of upgrading without trying. DWMX 2004 is unusable in Panther. What is most annoying is the pathetic shilling done by the Macromedia sycophants on the user to user forums. I keep thinking that an update will be coming shortly to repair a disgraceful piece of software. Until that comes, do not waste your money on DWMX 2004. -
Performance Issues Are Problematic
2004-01-14 09:26:26 anonymous2 [Reply | View]
The speed problems have been reported since the initial release of Dreamweaver MX 2004 and still have not been addressed. (There have been updates to the other applications within the MX 2004 suite, but not Dreamweaver.) Even trying to edit one of the supplied templates (the CSS page with various navigation elements) is horribly slow. When typing text it takes anywhere from 3-5 seconds for each keypress to finally display on the screen. My machine is at the low end of the system requirements (600mhz G3) however I have heard similar reports from users with G5 machines. I have reported this to Macromedia, the support rep duplicated my issue, yet I was still sent to the same web page to submit my issues regarding the problem. This page has been up for months now. -
Performance Issues Are Problematic
2004-01-15 17:54:34 cjennings [Reply | View]
One of the reasons that you haven't seen a patch for Dreamweaver yet is the fact that we've decided to spend more time gathering our customer complaints and fixing much more of them.
This patch should be available in several more weeks since it's in the final testing/validation phase right now. I think you'll be much happier with the performance and stability of the product as well as the number of issues we've corrected.
How do I know? I work on the team (in fact I'm ordering dinner for a long evening right after I hit the submit button). :)
-- Craig Jennings -
Performance Issues Are Problematic
2004-01-21 09:00:12 agallisa [Reply | View]
Its always nice to see a developer chime in and let us know that they are aware and are working on the problem. I am very excited about a patch to MX 2004. I use it all the time at work and it really is much better with it CSS integration.
My only wish besides the obvious performance problems is that they somehow give us the ability to tab the documents the same way you can in the Windows Version. It certainly makes for a much neater workflow. I use Exposé to help me with this but its just not the same.
Thanks for posting here Craig. -Alexis -
Performance Issues Are Problematic
2004-01-16 07:33:07 anonymous2 [Reply | View]
Mr. Jennings, you seem nice enough, but please pass along my disgust to your fellow Macromedians. I used to love your Mac products, but with the release of the MX line, your company's offerings have become a sorry joke who's pathetic performance has cost me more money and time than I care to think about.
If MM is no longer interested in creating GOOD - hell, I'll settle for FUNCTIONING - software for the Mac, just pull the plug and stop the charade.
I said it to your customer 'service' and I'll say it here: I will never pay for another Macromedia app again. You're incompetence has lost you another customer. -
Performance Issues Are Problematic
2004-01-16 08:14:32 anonymous2 [Reply | View]
Folks, let's all not jump in Mr. Jennings. He did say they're working on the problems, which is what you wanted, right? And, it takes time to find the bugs in the codes, fix these, then test these, and then pull it all together for an update. What more do you want? For Macromedia to drop all Macintosh development stone cold?
If you have read the blogs by Macromedia folks, you'll notice that a good number of them are Mac users. That should tell you something - I'm sure they're not happy with this release but then it was a major update, with a major interface redesign and sometimes things just don't go the way you want. I'm speaking from the developer's perspective (ColdFusion-generated websites) so I know what it's like - you run into things you didn't expect to happen and you have to fix these and it takes time. -
Performance Issues Are Problematic
2004-01-25 03:05:05 Crag [Reply | View]
Well I've checked out some of the blogs and I must say if these guys are Mac users then either they ignored the problems or were told to ignore them. I mean, did MM want to get the product out the door for the Windows users and decided to screw the Mac user in the process? Maybe they figured that we'd all hang in their till they got around to fixing the Mac only bugs?
Because reading MM own boards, EVERY Mac user has had serious problems with MX 2004. And usually, when someone brings one up they get a standard reply from a "MM Team Volunteer" swearing on a stack of bibles that it works on their Mac. Right. What special Mac do they have?
Frankly, MM has had it's chance and it lost many Mac customers in the process. I feel no pitty for them or their programmers. Maybe they should test the product first? They could have delayed the release of DWMX04 till the Mac side was stable... but that would've delayed the Windows version. So, we Mac users, who help establish MM as the defacto Wed Development company got screw. I won't again and I hope you don't either.
Do I sound pissed? I am. It's cause my company lost over $1500 dollars casue we didn't act within the 30-day return window. -
Performance Issues Are Problematic
2004-01-17 20:50:41 robreed [Reply | View]
I couldn't agree more. I registered just to say that. I want to say thanks to everyone at Macromedia working on these issues. And thanks for openly acknowledging them in the first place. You don't have to look any further than Apple for a company that does less than that. As a matter of policy it seems Apple refuses to even acknowledge huge issues with shipping products before they have a patch available and even then you have to read between the lines with the release notes to find vague references to real problems. 10.0/10.1 Server had huge problems and 10.3 Server still has big problems, though it's much improved... Panther client has problems and everything from Apple Remote Desktop to PowerSchool... iPhoto 4 is great, especially compared to the horrible performance of the previous version. There was an iPhoto article (at least one) here too and that article didn't make a big deal out of big performance issues either, if I remember correctly.
As users (or administrators, managers and developers)we're as much a part of the platform as any application developer, hardware or software product or the OS itself. Do you ever think to ask yourself if you're living up to your responsibilities? Take the time to ask yourself if you're a good member of this community? These performance and stability problems are real. If they are preventing you from being productive and waiting for a promised fix isn't an option for you then unfortunately you may have some difficult choices to make. This is hardly new territory for anyone who has spent any amount of time working with IT and computer technologies. We're all disappointed with issues like these from time to time. They're an unavoiable part of the process. No one has unlimited development dollars, testing is hardly a perfect process and no one would be happy if developers endlessly sat on products chasing some unattainable perfection.
It's a respected adage in IT that's it's best to avoid any 1st revision product in a production environment, whatever the product.
I want to know if a developer is working in good faith. When I go through the new Dreamweaver I see a product that has a number of real improvements, new features and enhancements, that does a good job of matching the pace of the related technology and other indications that Macromedia is indeed working in good faith and I say to myself, it's too bad the performance is such an issue and I hope they can correct it and keep building toward a strong and important application (important to me and important to the platform).
This ranting doesn't help anyone and certainly isn't making you anymore productive. Making note of the problems is helpful... but this thread stopped being helpful to anyone many posts ago.
-
Performance Issues Are Problematic
2004-01-25 03:14:34 Crag [Reply | View]
"but this thread stopped being helpful to anyone many posts"
Oh really? I think it's very helpful to the poor sap who thinking of buy DWMX2004 for the Mac. I think it's very helpful indeed.
As for making notes of the problems.. many here, inculding me already have, numerous times at MM's own Tech Support Website and boards.
These kinds of rants, and notice not many have been in support of MM, are helpful to both MM and any future customer. It tells MM they have troubles and this "version" has created a bad image problem for them in the Mac community and it tells any customers to look before you spend your dollars.
-
Performance Issues Are Problematic
2004-01-27 10:31:16 robreed [Reply | View]
There are endless little dicussions like this all over the Internet about Dreamweaver MX and every other piece of technology you could think of, including ones that you love... ones that I think are great.
It is a problem that they are fractured and scattered all of the place, in places Macromedia will never find. They've found this one which is good, O'Reilly.com is a 'well known place' obviously but still this is one random article. Even if you stuck to just major mainstream periodicals and publisher websites you would find dozens of Dreamweaver reviews and almost as many discussions.
What's my point. If you have an issue with a Macromedia problem, the best place to take it is Macromedia. If everyone did that they would know exactly where they stand with Mac users and every other category of customer. Macromedia knows how many Dreamweaver licenses Macromedia has sold to what platforms, what version and when. If a significant # of users start complaining (to Macromedia) then they'll certainly know they have a problem - whether a technical problem, image problem or whatever.
Macromedia has openly acknowledged this issue here x2. I'm not saying that the discussion isn't helpful... just the dog-pile style ranting. New comments have been added in since my post that are helpful in my opinion. They contribute new information about these performance issues. New "yeah Macromedia sucks bad..." comments aren't necessary, they've been made here already.
Hey, I'm just saying that I've been involved in IT for a long time and it is rare for a company to openly fess up to performance issues in a shipping product. I'm thankful for that as a user. I don't think it makes sense to slap it away.
I'm sure that the best way for you to complain to Macromedia about a product is to take the issue to Macromedia.
In the interest of adding some helpful info... here is a link to Macromedia's support site that talks about "emerging issues" with Dreamweaver MX on Mac OS X including this one.
http://www.macromedia.com/support/dreamweaver/ts/documents/emerging_issues.htm
They've also posted a performance survey here. Everyone who has Macromedia Dreamweaver MX would do themselves nd everyone else using the product and Macromedia a favor by investng the time to take the survey
http://www.surveymonkey.com/s.asp?u=5358277649%20
(I think this will work if not then there is a link to the survey on the emerging issues page above).
I'm in favor of Mac OS X being a strong platform. That requires great applications running great on Mac OS X. As users we should be concerned about doing everything we can to help developers build support and maintain great Mac applications.
-
Performance Issues Are Problematic
2004-01-14 13:11:00 anonymous2 [Reply | View]
I too used MX04, until I just could not take it anymore. The app would at times crash, but worse was the response times to the opening of files,creating,editing CSS. Forget trying to move quickly in the app, and updating templates or library items. It is just too slow. I had to reinstall MX 6 and use the update(6.1) and everything was again snappy and stable. The biggest complaint is that I use code view in most all the site I build, and that was just as slothful.
NOTE: If you use v6 stick with it until Macromedia gets on the ball with the problems with MX04. -
Performance Issues Are Problematic
2005-02-23 15:47:33 kurt.wisener [Reply | View]
I really should have been around to writ this a yera ago, when it was still pertinent. Things are a little behind out here in my neck of the woods... -
Performance Issues Are Problematic
2005-02-23 10:28:57 kurt.wisener [Reply | View]
Look, enough already. I have been following this thread for a while now and all I can say is, wow. Macromedia has been a great company since I came across it in 2000. I have always been patient with their release issues, and been well rewarded for that patience. Contrary to all the salivating and ranting I've seen here, I have found them to be quite amicable in every instance. FOR GOD'S SAKE MAN A DEVELOPER APOLOGIZED IN HERE! Find an Apple developer that would brave a thread like this. Now, if you are all that pissed at Macromedia and Apple over their performance issues, shut up, get in line, buy a Dell running XP, load MacroWin and leave the community. They already know full well that a bad product costs customers, hell, linecooks at Denny's know that. Your venting is doing no real service, save the one you are doing yourself. Macromedia is a good firm with a solid but mercurial history, deal with it or leave, but either way, get over it in here, please.
-Kurt
