view in He3

One more RTFM question - does he3 support viewing the current document in the IDE yet? --

What do you mean "viewing the current document"? -Matt ----- Excess quoted text cut - see Original Post for more -----

HomeSite+ allows you to define mappings for files, so I can say,. f:\web == 127.0.0.1. So if I'm at f:\web\foo\moo.cfm, I can hit a key and HomeSite+ will display 127.0.0.1/foo/moo.cfm in an embedded IE browser in the IDE itself. This is a nice feature for quickly testing small mods. -r ----- Excess quoted text cut - see Original Post for more -----

Okay, so how about the following. 1. A preference setting indicating whether to open a file in an embedded browser or an external one. If you choose external it would use the default browser, but allow you to override it will a different one. 2. A project property specifying the base URL for the project. 3. If you are using the CFML editor it would append the path of the CFM file to that of the base URL and show it in the browser. The question is what to do with the HTML editor. Should it do the same as the CFML editor or should it just open the file directly since it isn't dynamic? -Matt ----- Excess quoted text cut - see Original Post for more -----

> 1. A preference setting indicating whether to open a file in an embedded > browser or an external one. If you choose external it would use the default > browser, but allow you to override it will a different one. Yep. > 2. A project property specifying the base URL for the project. Yep. > 3. If you are using the CFML editor it would append the path of the CFM file > to that of the base URL and show it in the browser. > > The question is what to do with the HTML editor. Should it do the same as > the CFML editor or should it just open the file directly since it isn't > dynamic? Well, why would it matter? If I have /foo.htm and /foo.cfm open, I'd expect the same thing to happen when I use view. Ie, just go to URL/filename. Period. -r

In a real APP I rarely can just view the active document via the URL.  It always has to go through a controller (similar to fusebox and mach-ii). An option for a single URL for all views of the project would be nice, or even better is a way to map individual CFMs to URLs.  It would have to be set on an individual CFM basis and stored with the project, but once set then ready.  I believe this is what CFStudio did. Thanks, Sam ----- Excess quoted text cut - see Original Post for more -----

> In a real APP I rarely can just view the active document via the URL.  It > always has to go through a controller (similar to fusebox and mach-ii). Certainly there will be documents that can't be viewed normally. Custom tags, Application.cfm, etc. > An option for a single URL for all views of the project would be nice, or > even better is a way to map individual CFMs to URLs.  It would have to be > set on an individual CFM basis and stored with the project, but once set > then ready.  I believe this is what CFStudio did. Ack. That would be horrible. I'd hate to set a URL for every single file in my application. I'd much rather just set one default URL. NOw, maybe it would be nice to override it on a case by cases basis. As for Studio, it wasn't per file, it was per directory. -ray