Conclusions

From Woofgui

Contents

Name

  • The program needed a name so that developers and users could talk about it. Secondly, the name was important because it should reflect the program's origin. Many ideas were discussed, but after long debates + the acceptance of our project by Woof's original author, we decided to stick with "Woof" after all!

Decision:

  • Name = Woof: Tobias, Martin, Chris


Installer script

  • We will write an installer-script that will copy the files of our software to the correct places on the user's system.
  • For the fully-fledged releases (the ones with actual names + changelogs), we shall provide precompiled distribution-packages: .deb, .rpm etc. - Launchpad seems to do part of this (e.g. 32 / 64 bit) automatically

Decision:

  • Pro Installer: Tobias, Martin, Chris


Window-generator

  • App to generate the interface
  • wxpython: it's python, it's well documented on the web; users need python anyway and won't mind installing wxpython, at least less than installing a different package.

Decision:

  • Pro wxpython: Martin, Tobias, Chris


Enhance the original woof-console-concept

  • Enabling our software to be just as usable from the console as it will be from the GUI makes it far more usable for people outside the 'normal' Gnome/KDE spectrum
  • All GUI-related commands will have to be wrapped in GTK/QT = true conditions so that they won't be launched if someone is using console only!

Decision:

  • Keep console-functionality: Tobias, Chris, Martin


Naming-Scheme for fully-fledged releases

  • We will use funny names from "The Big Bang Theory":
  • The "Wollowizard" Release
  • The "Queen Penelope" Release
  • The "Sheldor" Release
  • The "Rajmahal" Release
  • ...

Decision:

  • Big Bang Theory: Tobias, Chris, Martin


Language-support

  • We'll add language-support right before a release. We need to get fixed on the phrases that appear in the GUI and need to be translated, though!

Decision:

  • Add language support: Tobias, Chris, Martin


Personal tools