| | 1 | Please do not delete anything from this page. Add comments under the requirement |
| | 2 | or add requirements if necessary. Must means it it is essential to the upgrade. |
| | 3 | Should means it would be a nice feature to have. |
| | 4 | |
| | 5 | List of requirements |
| | 6 | |
| | 7 | 1. The new format must provide an easy upgrade path for the user's commands. |
| | 8 | a. A keyword system appear to be the best option |
| | 9 | b. Something like |
| | 10 | |
| | 11 | ; FM/2 commands file -- 3 lines: title, cmd line, flags |
| | 12 | version = 2 |
| | 13 | |
| | 14 | Name = Unlock exe or dll |
| | 15 | Command = unlock -v %a |
| | 16 | Icon = 4096 |
| | 17 | MenuId = 2100 |
| | 18 | IconName = areallygoodicon.ico |
| | 19 | |
| | 20 | 2. The format must be easily expandable while remaining backward compatible. |
| | 21 | a. A keyword system appear to be the best option |
| | 22 | |
| | 23 | 3. The format must lock in the resource number for each command. |
| | 24 | a. A keyword system appear to be the best option |
| | 25 | |
| | 26 | 4. The menu structure of the commands should be under the control of the user. |
| | 27 | a. Should the user be able to name the sub menus or should a limited number |
| | 28 | of sub menu options be provided? |
| | 29 | b. Should all user added and FM/2 provided commands be movable to all potential |
| | 30 | sub menus? |
| | 31 | |
| | 32 | 5. The user should be made directly aware of new FM/2 command options and have access for adding FM/2 command options at anytime. |
| | 33 | |
| | 34 | 6. Under a keyword system. The rules would be that each definition much start with a name keyword. The others could be in any order. |
| | 35 | |
| | 36 | 7. The ini file should be considered for the storage medium. |
| | 37 | |
| | 38 | 8. A version keyword would allow us to add features while retaining backward compatibility. If we know the file is version 2, it's trivial to provide |
| | 39 | default values for a version 3 file. |
| | 40 | |
| | 41 | 9. We should provide a drop down of the icons that were unused because their commands is not being used and we should include extra icons in FM2RES.DLL. |
| | 42 | |
| | 43 | 10. An FM2PATH for use with commands, associations, archivers, etc to reduce the need to include full path names & without cluttering up OS/2's PATH should be developed. |
| | 44 | a. FM2PATH is probably just another settings page item. Probably |
| | 45 | needs to be presented as a listbox with reordering support. |
| | 46 | |
