Comments on: Speed up Dreamweaver MX: Some performance boosting tips

By: BlackRabbit

BlackRabbit — Sun, 04 Sep 2011 15:00:25 +0000

There must be some kind of script filtering two — out. There should be two — after nomunge.

By: BlackRabbit

BlackRabbit — Sun, 04 Sep 2011 14:41:01 +0000

Correction:
java –jar c:\yuicompressor-2.4.6.jar –nomunge –o

not
java –jar c:\yuicompressor-2.4.6.jar –nomunge –o

By: BlackRabbit

BlackRabbit — Sun, 04 Sep 2011 14:38:22 +0000

Hey, I tested Heinz's tip on optimizing the *.js files and I think Dreamweaver CS5.5 starts much faster now. I did this for a friend.
I used the YUI Compressor to "compress" the files, and it reduced the filesize about 50%! There are 971 js files in dreamweavers configuration folder. Size before 1Â 012Â 472 bytes, size now: 5Â 507Â 096 bytes.
The YUI Compressor is build with java, heres what I did (for windows)(you may want to google some of the steps):
1. Download the YUI Compressor (I placed it in "c:\")
2. Make sure you have the latest version of java, if you don't install it.
3. Make sure java is in the enviormental variables.
5. Make a copy of the configuration folder to somewere on your harddrive (I used "c:\temp")

Now you need to produce something that runs the YUI Compressor on all the files and appending them with new code. I created a .bat file for doing ths:
6. Use cmd and the dir command to create a textfile with paths to all the *.js files in the c:\temp\configuration folder
7. Open excel and copy the content of the text file to a spreadsheet
8. In the column to the left of this write this: "java –jar c:\yuicompressor-2.4.6.jar –nomunge –o "". Copy this for for all rows to the end (where the textfile output ends)
9. On the column to the right of the adresses type "" "", copy this to the end where the adress row ends.
10. Copy the adress column. Paste it to the right of "" "".
11. Copy the entire thing and paste it into a text editor. Remove all the tabs. A correct line looks like this:
java –jar c:\yuicompressor-2.4.6.jar –nomunge –o "C:\TEMP\configuration\Behaviors\Actions\Call JavaScript.js" "C:\TEMP\configuration\Behaviors\Actions\Call JavaScript.js"
12. Save it as a bat file and run it.
13. When finished, MAKE SURE TO MAKE A BACKUP of the orginal configuration forlder in the dreamweaver directory, and copy the new one to the dreamweaver directory.

That sould do it.

By: Ken

Ken — Mon, 02 Aug 2010 21:27:43 +0000

I am having an issue with Dreamweaver CS3 taking a LONG time to add a file to local files. Or for it to show up on the drop down. If I add an image and have to put that image to the server, it might take 1–4 minutes for the jpg to show up in the local files. I don't have ANY real system in place unfortunately. The local files are basically a huge list of jpg's etc. Is that why this is happeneing? Could it be the anti-virus slowing it down. I wrote NOD32 on how to exclude the Dreamweaver folder from real time scanning but they haven't gotten back to me. (what a surprise.)

Thanks,
Ken

By: Nick Jackson

Nick Jackson — Mon, 15 Mar 2010 11:26:06 +0000

Hi.

Thanks for the tips. Trying most of them.

Any updates for CS3/4?

By: Alexis

Alexis — Thu, 17 Dec 2009 06:57:15 +0000

These look really handy. I’m currently re-designing my site so will see how I can incorporate some of this functionality.

By: bill

bill — Mon, 03 Jul 2006 04:21:39 +0000

I am here to say hello and you have a great site! nokia6630

By: sniptools

sniptools — Thu, 04 Dec 2003 16:23:34 +0000

That's a brilliant suggestion, Heinz. Thanks!The URL to Brainjar's Crunchinator: http://www.brainjar.com/js/crunch/

By: Heinz Malcharzyk

Heinz Malcharzyk — Wed, 03 Dec 2003 06:37:08 +0000

Here's another way to speed up DW MX:

Remove all comments inside any JavaScript file in any DW MX Configuration folder. But CAUTION! This is going to take a really long time. In addition, the JS can be shrunken by removing lots of obsolete tabs and spaces. If this is too much work for you, go to the BrainJar JavaScript Crunchinator

As DW MX checks every line of code inside those JS files on startup, a line that doesn't have to be checked is a time saver. There are thousands of lines that consist solely of // comments /* or even multiline comments */

Unless if you are a developer who wants to know exactly what these JS files do, get rid of 'em.