Tom Muck's Blog
News and Views
in February - 2007
Extension Manager problems
Monday, February 05, 2007 8:37:37 PM
Has anyone had problems using the Macromedia Extension Manager? I've come to the conclusion that someone (a third party) will have to create a program to install extensions into Dreamweaver. The current EM has too many problems. I'm really not sure why it is so hard to make it work -- it is, after all, an unzipping program. Basically, the EM unzips files into appropriate Configuration folder subfolders. However, problems arise with multiple programs installed trying to use the same extensions (DW 8 and DW MX 2004, for example.) Problems arise with shared files among extensions. Problems arise when users install extensions that overwrite DW system files. Problems arise when the DW cache file has become corrupted or contains outdated information. Problems arise with multiple users on one machine. On top of that, even after all these years there is no automatic packager for extensions. People have created packagers over the years, but nobody has run with it and kept up with it. There is a server behavior builder in Dreamweaver, but without the ability to package the resulting server behavior, it becomes a hassle to distribute your code without knowing the intricate details of the MXI file format. Files created by the server behavior builder are actually hidden by default in Windows. Too many problems, too much frustration, too little time. I think it may be easier to distribute extensions as ZIP files and leave instructions for users. Your mileage may vary. If you have one program installed and only use a few extensions you may never have a problem. I've had more than my share.
Category tags: Dreamweaver
Posted by Tom Muck
Add comment | View comments (4) | Permalink | Trackbacks (0) | Digg This
in February - 2007
Before posting comments or trackbacks, please read the posting policy.