Editing ModRana Roadmap
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 39: | Line 39: | ||
== What needs to be done to get the Qt GUI in a usable state == | == What needs to be done to get the Qt GUI in a usable state == | ||
- | === Separating the GUI logic to a GUI module | + | === Separating the GUI logic to a GUI module === |
Most of the core GUI logic currently resides in the modRana "kernel" the ''modrana.py'' file. This logic needs to be transfered to a separate GUI module tat can be loaded by modRana at startup, either by providing a CLI parameter or automatically (once implemented). | Most of the core GUI logic currently resides in the modRana "kernel" the ''modrana.py'' file. This logic needs to be transfered to a separate GUI module tat can be loaded by modRana at startup, either by providing a CLI parameter or automatically (once implemented). | ||
Line 53: | Line 53: | ||
** -d, --device - set device module '''DONE''' | ** -d, --device - set device module '''DONE''' | ||
** -u, --ui - set which GUI to use '''DONE''' | ** -u, --ui - set which GUI to use '''DONE''' | ||
- | |||
** --lat, --lon, --zoom, --layer - set a given map screen parameters at startup | ** --lat, --lon, --zoom, --layer - set a given map screen parameters at startup | ||
** --no_gps - don't start GPS on startup | ** --no_gps - don't start GPS on startup |
Learn more about Contributing to the wiki.