Dreamweaver gives a lot of options, like a Live preview, split the live preview and codes, and many others options in the footer, and sidebar sections.
Can I disable it's some features to increase its performance?
Sadly you cannot disable whole "sections/modules" of the program there are however quite a few things you can do before you just replace it with Notepad++ ;)
I found a comprehensive list here http://sniptools.com/vault/speed-up-dreamweaver-mx-some-performance-boosting-tips, some of these look really useful:
- First and foremost, if you are on Windows, especially XP and 2000, then get the latest service packs from Windows Update, and most importantly, the MSXML SP4 update. This will immediately improve your system's performance. (Has worked for several people I know.)
- Make sure real-time virus protection is off in the DW folder. Most virus protection programs allow you to exclude a folder when doing virus checking. You should exclude the Dreamweaver folder from your virus protection. Dreamweaver is constantly loading and executing HTML and JavaScriptfiles while you are working. Each file is scanned if you have virus protection on. If you are worried about viruses in this folder, you can run a scan on the folder when you aren't working with Dreamweaver. Be sure to also include subfolders. This should give you a noticeable speed improvement.
- When the Dreamweaver Application window is open (particularly with the Databases or Component tab selected) Dreamweaver will keep refreshing window content. This can have a real impact on Dreamweaver performance, and so it is best to keep the Application window closed when it is not being used.
- Right-click > Close Panel Group on any panel that you don't use. Most of them don't take up any processing time, but some of them do, and if you don't use them, you shouldn't be penalized for it.
- If you want to eliminate some of the drag (but lose server behaviors functionality), you can go into Configuration > ServerBehaviors> [your server model] and rename the folder to something else (like ColdFusionOLD) and then create a new blank folder (ColdFusion). DW will respond a little quicker with no server behaviors to worry about. Your Server Behaviors menu will be empty, but DW will not have to read your document every time you make an edit to re-populate the Server Behaviors panel. Alternatively you can rename the old folder and create your own new folder and copy only the server behaviors that you need — the HTML, EDML, and JS files for each server behavior.
- The same trick will work for the Behaviors panel as well. Go into the Behaviors > Actions folder and remove HTML files of Behaviors that you will never use.
- Don't install a lot of extensions that you aren't going to use. Each extension copossibly eat up valuable processing time. Only some extensions cause slowdowns, but if it is something that you aren't going to use, don't take the chance. Also, extensions cause the load time of the program to be increased.
- Another way to speed up response time is to go into Preferences > Invisible Elements and set up the Show Dynamic Text As {}. You can also uncheck the hidden elements so they aren't rendered either.
- Also on that same Preference screen is the option to turn off Server-Side Includes. This will speed up the response time on any page that has server-side include files.
- In the Preferences > Highlighting tab, uncheck the different color highlights.
- In the Preferences > Accessibility tab, uncheck the Offscreen Rendering box.
- In Preferences > Code Rewriting, uncheck Rename Form Fields When Pasting. When this is on, DW scans your document for form fields every time you copy/paste a form field.
- In Preferences > Code Hints set the delay to 0. This allows the popup code hint menus to come up right away while you type code instead of being delayed when editing code in code view.
- In Preferences > Quick Tag Editor set the delay to 0. This allows the popup code hint menu to come up right away while you type code instead of being delayed when editing tags in the Quick Tag Editor.
- In Preferences > General set the Faster Table Updating (check). This means that your tables may not update themselves automatically each time you make an edit, but the response time of the program will improve.
- There are some tricks in the Translators folder also. If you remove the translators, DW will function more quickly, but you'll also lose a lot of the design-time rendering of code. If you aren't concerned about it, get rid of it. Rename the Configuration > Translators > [your server model] folder to something else, and replace it with an empty folder. You'll also lose the functionality of server behaviors, but if you are strictly using the code window, this may not be a concern. Try it out: rename the Translators folder to TranslatorsSAVE, and create an empty Translators folder. Restart the program and load some of your code-heavy pages into DW. You'll be amazed how fast the program responds.
- If you are on a Macintosh, set the memory used by DW to a high value — at least 100 Meg is a safe number. Also, rebuild your desktop often.
- Snippets: The snippets panel is slow when it contains a lot of snippets. Remove the snippets you don't use (probably all of the preinstalled snippets) by going into the Snippets folder and deleting or moving the files.
- When setting up your site, leave the setting unchecked for Refresh Local File List Automatically.
- Make sure that you check the Enable Cache setting in the Site panel (Local Info page). Check the Cache setting in the Bindings panel by right-clicking on any data binding that is defined, such as a Recordset, and make sure that Cache is checked.
- In the Site panel, in the Design Notes tab, uncheck Maintain Design Notes. You'll lose the functionality of Design Notes, but that may not be an issue for you.
- In the Site panel, in the Testing Server panel, leave the setting unchecked for Refresh Remote File List Automatically.
- Go to Preferences > General > Maximum Number of History Steps. If you don't have a lot of memory, you can decrease this setting. This is a very useful feature of course, so use your judgment (i.e., don't set it too low.)
- There are some issues with the Frontpage Publish commands.