Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Trim Dreamweaver's RAM footprint and launch times' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Trim Dreamweaver's RAM footprint and launch times
Authored by: nmerriam on May 24, '07 02:56:06PM

Just to note -- this really isn't particularly "dangerous" in any sense (although you should backup the app), but it is a technique that should ONLY be used for Dreamweaver, not any other app. That's because Dreamweaver is not really one big program, it's basically a big XML/Javascript interpreter, around which all sorts of text files that happen to support web development are supplied (and easily added).

This is why Dreamweaver always has been such an amazingly cool app from day one, and continues to be the most easily customizable and powerful web development app -- it has no features per se, it just comes with a lot of XML and Javascript file "plugins" from Macromedia/Adobe out of the box, and those plugins support all the individual CFML/ASP/etc features. So deleting those individual files won't do anything but remove that particular functionality -- it's exactly the same as deleting plugins from Photoshop, or a language addon from TextMate.

The cool thing is once you realize the entire program itself is just a bunch of XML/JS files, you can literally rebuild the program interface, functions, options, etc it in almost any way you can imagine (and code support for).



[ Reply to This | # ]