Some have noticed that Dreamweaver can perform sluggishly.
One reason is that, by default, it's checking all files in a site (and all subdirectories) to determine if they have changed--and it does this every time you leave and return to DWMX, such as to go read email, edit a word processing document, etc. The thinking is that you may have created or edited a file while outside DWMX. Unfortunately, that "lookup" can cause a painful delay if you leave and return to DWMX often, especially if the site has many files (and subdirectories).
The option is controlled by the feature "refresh local files list automatically", a checkbox in Edit Site>Advanced>Local Info. Turn it off and see if that helps.
You can use the "refresh" button in the site tab to refresh the list. Also, if you expand a directory for he first time since opening the site, that will also obtain a refreshed list of what's in the directory. Once it's opened, though, the file list is cached and only using the "refresh" or restarting DWMX will obtain an updated list (with the "refresh automatically" option disabled).
It's worth clarifying that this is a site-specific feature. You can leave it enabled on one site and disable it on another.
One other comment about poor performance in DWMX in general: I mentioned in my entry of 9/27 ("Getting into Dreamweaver for Studio users") that your machine's performance may have an impact, and in an entry on 8/10 ("Time for developers to consider a hardware upgrade?") I suggested other benefits of considering a machine upgrade.
Wednesday, October 16, 2002
Friday, October 11, 2002
Running the updater
Well, I've waited a few weeks to install the updater and while I've heard of some problems none seem so grave so I've installed the updater (http://dynamic.macromedia.com/bin/MM/software/trial/hwswrec.jsp?product=cfmx_updater.
It went well, though while it reminds you to stop the CFMX service and the release notes tell you to also stop the CFMX ODBC Services as well as restart all of them after the updater is done, it's easy to forget to start those ODBC Services which could lead you to think something went wrong with the install (I did, and none of the datasources were working correctly until I figured that out).
I was disappointed to see that the udpater did not fix the problem I raised in my June 2002 article on the new server-side redirect, with the getpagecontext().forward() method. It still does not work if a forward is attempted from a form action page. Grr.
/charlie
It went well, though while it reminds you to stop the CFMX service and the release notes tell you to also stop the CFMX ODBC Services as well as restart all of them after the updater is done, it's easy to forget to start those ODBC Services which could lead you to think something went wrong with the install (I did, and none of the datasources were working correctly until I figured that out).
I was disappointed to see that the udpater did not fix the problem I raised in my June 2002 article on the new server-side redirect, with the getpagecontext().forward() method. It still does not work if a forward is attempted from a form action page. Grr.
/charlie
Thursday, October 10, 2002
Looking for Some Verity Docs?
Are you looking for more info to understand how CF's underlying Verity Search engine works? Whether for creating or searching them, there's lots more to it than is discussed in the CFML Reference or Developing CF Apps books in the CF docs.
I've come across some sites with interesting extended documentation. If you've not seen these they may be useful.
Before that, though, some may have noticed that in CFMX there is a new manual "Working With Verity Tools". That's certainly worth a look, particularly for the coverage of using Verity Spider searching. See it at livedocs.macromedia.com.
But beyond that, there is also a complete set of HTM-based Verity docs at http://support.exln.com/doc/full/dm/vdk/doc/. This is just the docs at a particular site that's posted them. There are other places that have posted them, in case these every disappear. Do a google search for "Collection Building Guide" to find such links. This particular link offers several docs related to Verity processing.
I've come across some sites with interesting extended documentation. If you've not seen these they may be useful.
Before that, though, some may have noticed that in CFMX there is a new manual "Working With Verity Tools". That's certainly worth a look, particularly for the coverage of using Verity Spider searching. See it at livedocs.macromedia.com.
But beyond that, there is also a complete set of HTM-based Verity docs at http://support.exln.com/doc/full/dm/vdk/doc/. This is just the docs at a particular site that's posted them. There are other places that have posted them, in case these every disappear. Do a google search for "Collection Building Guide" to find such links. This particular link offers several docs related to Verity processing.
Wednesday, October 09, 2002
New Search Feature for My Blog
You can now search my blog. Been wondering where I talked about how to edit the web.xml file? Or how to make the most of Studio? Or whatever? Now you can find the topic of interest to you. Notice the available "Search" form on the right above the archive links. Go to town!
BTW, I enabled this using Google's feature allowing creation of a search form on my site using their indexed data about my site. See http://services.google.com/cobrand/free_select to sign up to allow searching of your own site.
For bloggers, you may wonder how to get your site content searched by google. It won't just find it on its own. I found the solution was to create a page on my systemanage.com site (which is often spidered by Google) that linked back to all archive pages on my blog site. After a few days, Google found that page and began indexing the blog pages.
BTW, I enabled this using Google's feature allowing creation of a search form on my site using their indexed data about my site. See http://services.google.com/cobrand/free_select to sign up to allow searching of your own site.
For bloggers, you may wonder how to get your site content searched by google. It won't just find it on its own. I found the solution was to create a page on my systemanage.com site (which is often spidered by Google) that linked back to all archive pages on my blog site. After a few days, Google found that page and began indexing the blog pages.
Subscribe to:
Posts (Atom)
