ToDo

From Woofgui

Revision as of 13:42, 15 March 2009

Gettin' down & dirty with codework

• Coding: Complete Code-Rewrite. After we find out how to test for GTK/QT and which environment (Parent-Process) has launched our tool, we'll have to rewrite the whole script based on the original woof-code and keep the console-functionality working this time. We'll add variables to only display GUI-stuff for GTK/QT if the parent-process was in fact not a console.
• Coding: Write the autoinstaller-script taht copies all necessary files to their locations + chmods them.

Decisions that need to be made

• Decision: Settle our tool's name. We need to get consistancy.
• Decision: Gui-application or filemanager-script? This affects our whole approach!

Research which needs to be done

• Research: How to check for GTK / QT (NOT Gnome / KDE!) on an enduser's system?
• Research: Is the active service (Pythons baseHTTPserver-module) to offer a file for download easily hackable?

Done! Things we've accomplished!

• Research Is it wise to use the same port 8080 again and again
• Decisions Modify or enhance the_original woof console-concept
• Research How to read out the set system-language of an enduser's computer
• Find out outer-IP so people can download files while not in LAN
• Include a simple Abort-Button on the interface
• Design a Logo
• Research mutlilingual software written in Python
• Copy URLs to clipboard in Gnome/KDE
• Research Versioning Control Systems
• Set up Versioning Control System + more to collaborate on the code
• Set up Wiki
• Notify the woof-author about our efforts