Here
are features which will be incorporated into the program, as time allows. Please
feel free to send feedback if you have anything to add, or would like to change
any of the priority. Here
are features which will be incorporated into the program, as time allows. Please
feel free to send feedback if you have anything to add, or would like to change
any of the priority.
| Description | Difficulty | Effort | Priority |
| Currently when a room/item/actor is created, the user defines its class (e.g. 'darkRoom') but can not change this if he changes his mind. I must add this capability, but if could get nasty. | Medium | Quite a bit | High |
| Add support for replace and modify in the classes. | Medium | Medium | Quite High |
| Allow the user to delete a map which currently contains rooms, by prompting the user to delete the room(s) or move to another form. A first version will perform the same action for all rooms on the map; later will come a version which prompts on a per foom basis. | Medium - High | Medium | Quite High |
| Add lots of hot key shortcuts (boring, but straightforward) | Trivial | Little | Quite high |
| Copy/clone an existing room/actor/item, with a new name (question, should I also copy the contents? I guess that I could make it a configuration option, or prompt) | Easy | Easy | Medium - High |
| The find room/actor/item menus should probably be alphabetically ordered. Also, someone has suggested a combined menu in case the author has forgotten whether something is room, actor or item. | Easy | Little | Medium - High |
| Clicking the text above the various caption of the passages grid should sort by the corresposnding column. | Medium (unless a 3rd party component is used) | Medium | Medium |
| Make it easier to create dooways. maybe not a full blown wizard, but at least a dedicated dialog. Perhaps we need a new 'doorways' tab (visible only when there are some)? Perhaps we can create similar dialogs to simplify other processes? | Medium | Medium | Medium |
| Associate file type .Y2 with the program. | Trivial | Little | Medium |
| Perhaps the map should support different levels of zooming? | Medium - High | Medium | Medium |
| Save configuration options & screen size & position to registry (straightforward, store configuration options too (hmm, registry or save file (the latter would allow per project preferences)?) | Easy | Little | Medium |
| Add a mechanism to move a room from one map to another (quite tough, since I have to update map passages for all connecting rooms) | Medium - High | Medium - High | Medium |
| Add a help file (as complicated as I want to make it. Of course, if the program is self-explanatory, then it won't need a help file <g>). | Medium | Medium | Medium |
| Syntax highlighting of all code entry memo components (tough, even though I may have found a free syntax highlighting component, I still need to code a bunch of stuff). | Easy | Little | Medium |
| The Maps should use standard MDI keys like F6 to tab to next window (what are the standard keys?) | Trivial | Little | Low - Medium |
| Suggest new passage directons based on relative positions of rooms on map when adding a passage. | Medium | Medium | Low - Medium |
| More tooltips generally.. (boring, but straightforward) | Trivial | Little | Low - Medium |
| Allow user to specify location of the TADS compiler, then run it from within Plugh!, show the output in a window & allow the user to click a compile error & jump the location of the error (might be tough to figure out how to do it). | Tough | High | Low - Medium |
| Copy/clone an existing set of rooms - within the same map/between maps/clone an entire map. As above, what about contents? | Medium - High | Quite a bit | Low - Medium |
| More frequent info updates in the status line (anyone like to suggest what they'd like to see?). However, since the status line is becoming quite crowded, I could add a new tab showing all sorts of information about the project and remove the status line.. | Easy | Little | Low |
| Add 'credits' for those who have contributed ideas & tested and for 3rd party s/w components used (only one so far, but I may use more). | Trivial | Little | Low |
| Add a 'check for new version' option, for use when connected to the Internet. | Easy | Little | Low |
| Accept drag & dropped save files. | Trivial | Little | Low |
| Add some means to generate gameInfo . | Trivial | Little | Low - Medium |
| Currently, when a keyItem object is deleted, we remove all myKey properties of obejcts an classes which are using it for their myKey. In future we may wish to prompt the user for each one and ask him to select a new keyItem. | Easy | Little | Low |
Import existing TADS files (I'll wait until at least TADS version 3, which allows the user to write external parser files. With any luck, once parsing is separated from the rest of the compiler, I can take the parsing code (if MJR releases it) and hack it to my requirements). Nope, we've discussed it & it is actually simpler for me to write my own parsing code (probably using Lex/Yacc). The major drawback here is that there is no way to maintain comments during round trip editting (other than embedding them in a comment method which the player can't invoke, but the author can see). I am considering a 1/2 way house, where I would import TADS, but then you've lost it as I would save it as a Plugh save file, which you could continue to manipulate using Plugh. |
Complex | High | Low |
And, maybe, one day in the dim & distant future ... Mac support... 
Last updated 20 June, 2003 7:43 PM