- Not currently. I can put up the source somewhere when I get back from my vacation. Although as it is now there isn't much to put up.
- A custom output folder was planned, that's part of the saving/settings that I figured could wait till later. I just wanted to get something out that works in a standalone executable at first.
- I've been doing some research on how to make it cross-platform. It's written in C# -- I was hoping that mono would work out of the box but that didn't work quite as expected. I would love a Linux version just as much as you
- I'm not really sure how I could make color selection easier. The designation text boxes are already color coded -- I guess its possible to focus them if you click on a corresponding pixel in the image... but that seems like a lot of work for little benefit. Especially after adding a settings file which would save all of your current color settings (among other things).
Awesome, it sounds like you're on top of the whole thing
. I personally recommend GitHub as it's free in both senses, works well, and most DF-related stuff is on there already. Release early! You're right that saving color choice takes care of selection, I'm just too used to chromafort...
BTW, does Quickfort support multi-level designations? If so, how would I format the .csv for that?
The whole readme for editing blueprints
is worth a look.
Multilevel designations are possible, see here
, and work by adding a '#>' to the first cell of the enclosing '#'s. In fact, a high priority for enhancement should probably be to add the enclosing '#'s around exported blueprints, since they don't exist at the moment.
I'm not quite sure how you'd get multi-level plans out of an image - multiple images could work but would be pretty clumsy, or you could go for a tall image with 1px dividing lines of some unique color (#). That would be tricky unless the first pixel was a different (#>), and even then I'm not sure how QF handles multiple levels of different sizes so there's potentially a lot of error handling to be done. Generally it can probably be done by a user right now, but takes some careful thought.
Another enhancement would be to enhance the opening cell by limiting input and allowing users to explicitly specify a starting position
and comment/s. Where there is currently a text entry field (with '#dig' in the image above), you could instead use a drop-down menu as there are only four valid choices for blueprint type. Having three explicit text entry fields for start point coordinates and comments would also be good, defaulting to "#dig (1;1;cursor starts at top-left)".