The way I see it working is like this;
The (default) directories would be:
- My Documents\Latenite\Projects (contains saved projects)
- My Documents\Latenite\Includes (default include files directory)
- My Documents\Latenite\Plugins (plugins directory)
- My Documents\Latenite\Help (documentation directory)
- Program Files\Latenite (application directory)
Includes would contain include files - for example, ti83plus.inc. Latenite will manage a list of include directories, so for example I could install the TI API project into the "My Documents\Latenite\Includes\TIAPI" directory, add that to my include directories list in Latenite, then just use ".include tiapi.inc".
Plugins would contain plugin DLLs for Brass or Latenite.
Help would be a repository for documentation - Latenite will have a new help browser that can display text files, image files and so on, rather than having to create those fiddly XML files. If you download some new documentation, copy it to this folder and you'll be able to browse it from Latenite.
Latenite (in Program Files) will just contain the core DLLs and EXEs that make up Latenite.
The only disadvantage of the above is that you won't be able to automatically update the Latenite program files. I'll have to think about that.
(Click)
For each project, you can create a number of build configurations. Each configuration will have a number of key-value pairs (which you can add as many as you like) which are passed as environment variables to Brass for the assembler to pick up (much like it's done at the moment without the .cmd file hackery). What's obviously missing from that screenshot is a dropdown that would let you pick which output plugin ("TI-83 Plus Program", "TI-83 Program") you'd use for each configuration.
On top of those, you'd have a "configuration modifier" - a second dropdown with its own set of key-value pairs set in the same way, the most obvious use of which (and which will be the default) being a "Debug"/"Release" dropdown.
The other tabs are pretty simple; Events will have pre/post build events (run on the command-line, so you could for example copy files around or run an external program on each build). Debug will let you pick and configure the debugger; Publish will give you options for publishing your project (publishing will rebuild for each and every configuration under one configuration modifier, zip them up, possibly including source/other files and so on).
), all local programs have admin rights... I had never problems to write into Program Files
