TO DO List

These items are things that we would like to get done, and are not necessarily items that are a part of the SourceForge todo list.

Localization
Now that HexEdit is easily localizable, it would make sense to have those resources in files within a folder. I am thinking that each resource file would be named the language it is (English, French, German, etc. except spelled native to the localization). HexEdit would then read the filenames within the folder and create a Language submenu in the "options" menu with these names. When the user selected the name, it would close the existing resource and open the new one. The selected preference would be saved, and the default would be "English" if no preference had been set.

The files would simply contain those resources that need localization. For instance, DLOG, ALRT, DITL, TEXT, STR#, etc. One problem is that the folder could be seperated from the application, and thus required resources could be missing. So, I could make the English resources embedded within the program, and selecting English would simply close any open external language resource file.

Help
A help option would be fairly easy to implement. I have the code for a modeless dialog that does this; the problem is that the code relies on a lot of support code for modeless dialogs (including modal filter and list procs) that do not exist in HexEdit. Hmmm....more thinking to do on a new GUI shell for HexEdit.

New GUI Shell
The HexEdit GUI code is pretty hacked up at this point, and could really use some extended functionality. The best solution seems to be to use an existing framework to design and implement the GUI shell, and then move the HexEdit chunk and hex editing code over.

