Personally I think a the usability of CFStudio debugger depends on how you develop
apps, how the apps function, and how many you're working on at once.
Most all the sites/apps I build have their own root folder and use absolute paths
(/path/to/stuff.gif). So this means I have to set up and maintain a bunch of mappings
in Studio, which isn't very easy to get to quickly (Options/Settings/Browse/Dev
Mappings/Select or Setup RDS/enter up to 3 paths/then 2 OKs to get back). By itself
this wouldn't be a major deal, I agree, but...
For me, it's rare for the current CF template I have open to just work as a standalone
unit. Often it's a piece of a page that is going to be CFINCLUDED into some other
template(s). Usually it will need URL/form variables passed to it to work. Sometimes
it's part of a frameset and has TARGETs or JavaScript that depends on other frames.
And there are other instances along the same lines. With Fusebox, for example, you
always execute index.cfm which then calls other cfm files as needed. While it's still
possible to run it like this through the debugger, it becomes a pain.
So, given all that, I find it easier (and often just necessary) to Alt-Tab to the
browser and hit reload to test my code. If needed I turn on CF Server debug output,
or stick some CFOUTPUTs in my code to show me variable values on the fly. There are
also some tools out there to get debug info at runtime, such as CF_DEBUG, etc. I only
hit the Browse tab when I'm working on a pure HTML page, because that's pretty much
the only time it's useful to me, given the way I work.
Cheers,
-Max
At 5/6/2000 09:44 PM -0400, you wrote:
>Sorry Josh & Bill,
>
>But I think you've failed to set the debugging environment up properly.
>True, it's not perfect, but I use it daily and wouldn't want to give it up.
>
>Bill
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
