[INFRA-137] Choose standard project GUI framework Created: 24/Jun/17 Updated: 05/Apr/19 Resolved: 24/Jun/17 |
|
| Status: | Open |
| Project: | Software Development Infrastructure |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
For the sake of project administration, can we agree on a single GUI framework? LAM/PU proposes Qt5, mostly because that is how SPS AIT has been implemented. Fast, decent python bindings, general purpose canvas for things like matplotlib. The fancy GUI construction program generates a not-horrible text file. Not sure if there is a good enough image display widget. |
| Comments |
| Comment by chihyi [ 07/Jul/17 ] |
|
Currently IAA doesn't have plan to develop any GUI interface. We may do this in the future and agree to use the same GUI framework. |