> 1) Dreamweaver's file panel is difficult to navigate because > the files and the folders are all nested together in a very > small area. HomeSite and Windows Explorer for example, divide > the files and folders in an easy to use fashion. Solution: > Make an option to view the file/site structure in that manner.
I'm not sure how I feel about this. One of my biggest issues with Dreamweaver is simply that it takes up a lot of screen space if you use it effectively, so you simply have to have a giant high-resolution monitor to take best advantage of it. As for the display of the files and folders themselves, this seems more to be a preference that we might have based on our usage of Windows Explorer. > 2) Combined with (1), is the interesting choice of not > showing the full file path in the title bar, or somewhere. > Again, in HomeSite, you can see exactly which file you are > editing, but in DW, if you are looking at the same file in > both the dev server and the edition on your workstation, you > CANNOT easily tell which one is which. Solution: display the > full filepath in the titlebar, or another reasonable > location, AND show the full filepath when mousing over the > document title tabs. I think that's a great suggestion. > 4) Lack of support for Source Control systems, HomeSite > supports VSS, CVS, etc. And it appears that because HomeSite > support SCC, it inherently supports more Source Control > systems without additional development by the user. In my few attempts to use it, I had quite a bit of trouble getting CF Studio to work with source control systems. Have you had success with this? Do you think it's worth incorporating this into the product rather than just using a standalone client? > 6) The HomeSite query builder was pretty decent to work in, > put something like that in. Yes, for the love of all that's holy, I've been asking for a standard query builder since the dawn of time! For the life of me, I can't imagine what was going through the DW team's heads when they came up with the ones DW has. > 7) Interactive debugging! That's really going to be more > useful in the age of OO with CF. I think that's a limitation imposed by CFMX. CF 4 and 5 supported interactive debugging, but CFMX doesn't. As for its usefulness, most people were lucky to get it to work at all! Once you did get it working, it wasn't usually that helpful anyway in my experience. > 9) There's a number little annoying things missing, such as > convert tags to lowercase, a code sweeper/source formatting > that understand comments and 'middle' tags (cfelse), go to > end of tag hotkey, code collapse and so forth. Code collapse is probably the one of those features I miss most. I'd like to see all of them added. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190673 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
