Thanks, Chip. In fact, the documentation already does hold a whole chapter, dealing with uninstalling the app, and the manual steps needed in that process. And, it has already been planned for a more automated uninstall, though that feature is not all in place at the moment.
It is not just that I "want" it that way; but rather a matter of being the far most organized way of handling the material. It is the most tidy way for the user, and the safest way I could come up with, for the app technically to handle the number of files that might be generated. Thanks again, for your feedback. I welcome all such ideas that the app will be as good a product as possible. Things like this, is the main reason why the developing and Beta process have taken this long time. There is SO many tiny details to take into consideration, specially so, since the app does have a somehow major impact on the screen reader, first you learn to use it to the full. ----- Original Message ----- From: Chip Orange To: [email protected] Sent: Thursday, May 24, 2012 12:58 AM Subject: RE: Shipping an app, with a tree-structure Hi David, I just want to point out there is one problem when doing this: if the user chooses to uninstall your app, all those files which you unpacked and placed into custom locations will end up being left on his pc. If it's really important to you to do this, then perhaps you would consider offering an "pre-uninstall" menu choice or hotkey, with instructions to the user that they should execute this choice before using the WE uninstall option, in order to assure that all files are removed. hth, Chip ---------------------------------------------------------------------------- From: David [mailto:[email protected]] Sent: Wednesday, May 23, 2012 3:05 PM To: [email protected] Subject: Shipping an app, with a tree-structure The Extended Dictionary app, that I am developing, will be operating with a number of files, for different voices. I have all of this set up in a nice and tidy tree-structure. Previously, I asked if there was a way of including a tree-structure or sub-folder, with the WEPM file, when shipping the app. As I understand it, there is no way of doing this the way the Wepm is constructed. Hopefully, this will be possible in later versions of WE. I was adviced, to put all the files in the user profile folder, and then let my app initially move the files into the subfolder which it would create. OK, it kind of works, but also adds on quite a number of lines in the code. Way back in the old DOS days, I knew of a small software, which would "pack" a whole tree-structure into an .exe file. Running this .exe file later on, would unpack the complete tree-structure. I wonder if anyone here knows of a similar software under windows? This way, I could simply have distributed the "packed" .exe file with my app, and let the app execute the file, and no more would be needed to have the tree-structure in place. So, if anyone knows of such a software, it would be greatly appreciated if you would share your knowledge. Thanks,
