"Welcome to the future of OpenRPG and Mercurial portability," Prof. Ebral, Mad Mathematician.
Jokes aside, the new update manager for Traipse OpenRPG is a one of a kind update manager. When I really got into the code of what I was doing I realized that this software would be beneficial to others, so I am working on making this software a complete package. Yessir, I think this software is a portable software that can be *plugged in* to any other Python software and used for version control by the end user or developers. In fact, the Manifest python file is a modified clone of the PluginDB python file, only fit to meet the packaging standards, and that is also why the Validate python file is included though not used.
Here is what the Update Manager offers (boy I have repeated this .. but it is awesome!)
Updater: The updater is not the heart of the software, but it is not the face alone. In the current release you can select from the various branches you have collected from different repositories and update to any of those. You can also select to Auto Update or No Update. If you select Auto Update the software will pull from you default repository and then update to the current branch you have selected. If you select No Update the updater will close before it fully opens so you don't have to worry about being annoyed by it everytime you start the software.
Repos: Finally a reason to clone OpenRPG and rip it up. Here you can add repositories of OpenRPG, Traipse, Traipse Dev, OpenRPG, OpenRPG Dev, or maybe even one you make yourself. You no longer have to worry about gathering change sets and automatically updating, all you need to do is come to your Repo tab and refresh the repository of your choice. The list can extend as far as you want it or you can delete the repo list and keep it tidy.
Manifest: Keep your files, keep your files, keep your files. And yet, stay updated! The manifest is a list of all the files that are in your current change set, plus any others that you might want to keep. Check a file off and it is saved to a file that tells the software to back it up before you update.
Control: To be re-written
The current Update Manager has been lightly tested on both Linux and Windows XP. For a beginner such as I it was not an easy to task to accomplish some process I wanted, but I think I have a tight handle on them. Here are the known issues in the order I remember them.
Repos: GUI updates is pretty lackluster and sometimes even gross, but it works. WindowsXP user look at ugly words, Linux users can see pretty graphics. Sorry. The repo list in the updatemana.xml file could use some house cleaning. Each time a new repo is set, it deletes a portion of it, but not all of it. Perhaps another dictionary would help. e_e
The repos currently does not come with the Traipse repo as part of the package. This will be changed. If you need to know the url for the Traipse source it is: http://hg.assembla.com/traipse
Windows Users and Repos: Somewhere a change was made that causes the 'URL' and Check Box items to appear outside of their box. A simple fix is to resize the window.
Controls: It is not recommended to use the Controls panel to update to older revisions and then expect them to work.
Not all branches are compatible with your files!! If you ever crash you can rename your System folder, run setup again, and then obtain your files from the renamed System folder.