GUI needed about radiochronicle

[GoogleCodeExporter]

Original comment by [email protected] on 24 May 2010 at 10:54

• Changed title: GUI needed
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I think the GUI should be implemented in an additional .py file.
It can be lunched on demand in a third thread, receiving a pointer to the main 
radiochronicle object.
this way
-we do not create two parallel projects (GUI/CUI);
-the GUI-mode can be set as the default one using the config file;
-the GUI can be swiched on/off whatever happens in the main cycle.
-we do not overcharge the radiochronicle.py file;

Original comment by [email protected] on 5 Jul 2010 at 5:58

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

BTW, are you sure, that PyQT is the best solution?
It requires a list of other modules to be installed, so the installation 
process can become complicated for the final user.
May be the base TK is enough? After all, we do not need a lot.

Original comment by [email protected] on 11 Jul 2010 at 5:20

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Yes, a separate file looks a good solution.

I'm not sure PyQT is the best, but I know PyQT is good. Maybe using basic 
functionality would work ok also.

Original comment by [email protected] on 11 Jul 2010 at 8:24

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Original comment by [email protected] on 6 Nov 2010 at 10:43

• Added labels: Component-UI, Usability
• Removed labels: ****

[GoogleCodeExporter]

Original comment by [email protected] on 6 Nov 2010 at 10:52

• Added labels: ****
• Removed labels: Usability

[GoogleCodeExporter]

Original comment by [email protected] on 6 Nov 2010 at 10:54

• Added labels: ****
• Removed labels: ****