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 41: | Line 41: | ||
=== Separating the GUI logic to a GUI module - DONE === | === Separating the GUI logic to a GUI module - DONE === | ||
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). | ||
- | |||
- | |||
This work will be partially based on Mieru, which already uses the concept of separate GUI modules & has advanced CLI argument support. | This work will be partially based on Mieru, which already uses the concept of separate GUI modules & has advanced CLI argument support. |
Learn more about Contributing to the wiki.