Opened 13 years ago
Last modified 13 years ago
#690 new enhancement
bitten-slave GUI
Reported by: | mpotter@… | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 0.7 |
Component: | Build slave | Version: | 0.6 |
Keywords: | Cc: | mpotter@… | |
Operating System: |
Description
Add an optional GUI to the bitten-slave, either as a command line option, a separate program that wraps the bitten-slave, or a different version of the bitten-slave.
Presentation
This GUI would basically be structured as an informational frame around a scrolling text field where the normal bitten-slave messages appear. The informational frame could give various statuses, such as:
- General:
- Slave Name.
- Configuration using.
- Time of (or time since) last Server communication (Ping or other).
- When working:
- Current Recipe working on.
- Current Step in Recipe working on.
- Date Time started current Recipe.
- Time spent on current Recipe
- Date Time started current Step.
- Time spent on current Step.
- When idle:
- Time of last Server pole.
- Status of last pole, if a failure.
Implementation
This GUI addition ideally needs to be able to run under anything that bitten-slave runs on providing it supports graphical users interface. Doing a quick search, I would think using TK might be a good choice.
Future Additions
This application could be expanded in the future to include other features such as:
- The bitten-slave message window could:
- Add time stamps to each line.
- Highlight messages differently based off of:
- Source of message:
- From slave
- From external commands called by recipe.
- Destination of message:
- Standard Out.
- Standard Error.
- Regular expressions:
- Appears to be a warning message.
- Appears to be an error message.
- Source of message:
- The GUI could control the slave in additional ways, such as:
- Exit slave when finished with current recipe.
Another option for cross-platform GUIs is Greg Ewing's PyGUI http://www.cosc.canterbury.ac.nz/greg.ewing/python_gui/.