Here are some things we ''must'' do to get Thandy integrated to the bundles:
Here are some things we _must_ do to get Thandy integrated to the bundles:
* Implement a PackageSystem for OSX, and another for whatever win32 package system we're on by then. We'll need to figure out what features our current packages lack, and how best to get them. I think that we only partially have a Thandy 'upgrade system' implementation like this for win32, and we have no 'upgrade system' like this implemented for osx. So Thandy's current requirements for an upgrade system are that there be:
* Some good way to install packages
* Some way to tell which version of a package is installed
...
...
@@ -10,11 +10,11 @@ Here are some things we ''must'' do to get Thandy integrated to the bundles:
* Solve other issues as identified by testing.
* Either internationalization, a simple gui frontend, or both.
Here are some things that we ''should'' do that would help Thandy-and-bundle integration:
Here are some things that we _should_ do that would help Thandy-and-bundle integration:
* Split the bundles into separate packages that can get upgraded separately.
* Maybe, move our windows packages to MSI.
Here are some things we ''could'' do that would help Thandy-and-bundle integration.
Here are some things we _could_ do that would help Thandy-and-bundle integration.
* Maybe, port the Thandy client to some language or runtime that is easier for Windows use than Python.
Here are some things that we ought to do not necessarily related to Thandy-and-bundle integration:
