>requires the developer to actually configure information in a project.
>I know DWMX's project configuration annoyed me when I was used to just
>pointing Studio at a file system directory
Matt,
The key in to ensure that I can can get a feel for functionality without slogging my way through a project setup. (Perhaps bundle a series of simple "Hello, World!" projects that can be used to get a feel for things.) Once I'm sold, the minor investment in setup time won't be a big deal.
>Second, the project's
>settings could get out of sync with the target platform thus causing
>unexpected behavior.
Throwing out ideas:
- Let me tell the app which files contain vital settings (hopefully, there won't be more than a few per project), and optionally (by default?) remind me to check my project settings when changes are made to those files.
- Let me define the settings in the project info, and then automatically insert the values into my files wherever I enter something like [$He3.CFCpath$]. If I change the value, sweep through and update my code.
--
Roger Benningfield
work: http://journurl.com/
blog: http://admin.mxblogspace.journurl.com/
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
