||1 year ago|
|calfbox||1 year ago|
|documentation||1 year ago|
|engine||1 year ago|
|qtgui||1 year ago|
|LICENSE||3 years ago|
|Makefile.in||1 year ago|
|README.md||3 years ago|
|__init__.py||3 years ago|
|configure.template||2 years ago|
|gitignore.template||2 years ago|
|helper.py||2 years ago|
|launcher.template||2 years ago|
|main.py.template||2 years ago|
|mypy.ini||1 year ago|
|start.py||1 year ago|
File Structure, Description and How to Update the Template
The principle of this program is that it can be used in a self-contained "all in one directory" version but also in a compiled version with files all over the system, following the linux file hirarchy.
For that reason that are some processes that must be done manually and which will create generated but static files (not at compile or runtime) that are included in git. For example the qt resources and translation or documentation html files from asciidoctor sources.
Copied files from 3rd party libs that need to be updated manually.
- For Calfbox copy the whole source directory into template/calfbox and delete its .git
- nsmclient.py from pynsm2 into qtgui.
There is a menu in the example MainWindow but it is emtpy. Some default menu entries will be added dynamically by the template.
You can merge template and client menus. But there are some naming conventions you must uphold: menuFile menuEdit menuHelp menuDebug
These menuActions are standard and can only be hidden, deactivated or rerouted. But you can't create them on your own in QtDesigner actionUndo actionRedo actionAbout actionUser_Manual