Developer notes

####Impromptu notes and advice for developing Customizer.

Do you have interest to further develop Customizer, but you don't know where to begin? Then, this page is where you can get started. Below are notes which have been listed in groups, from highest to lowest priority.

####Basics first

• Installation via make for 4.1 releases from the master branch based on Python2, using "injection" method has been noted in this comment under issue #89.

####Improvements

• Look up issues with "Pending" label, which requires further investigation and come up with proper solution.
• Look up issues with "Official" label, which may be limitation of existing build. Therefore, less priority compared to "Pending".

####Trivial matters

• Look up issues with "Feature request" label.

####Historical reviews

• TODO: Tell the stories of changes made since 3.x releases, so that future developer won't repeat the history or same mistake again!

Choosing Python + Qt over Bash + Gambas had the following advantages:

1. no glue code, Python bindings for Qt are used (PyQt4) thus calling sub-processes is avoided as much as possible with native exceptions handling that are used across backends and frontends
2. porability, Qt has support for many platforms and architectures which the less used Gambas does not (or didn't at the time).
3. Python is duck-typed language which allows various things to be done with the same codebase and a hand full of tricks
4. errors catching was a pain, with Bash everything has to either be trapped or a code-block behind a statement had to be in place with a function what do when something bad happens. with Python all of the errors are exposed and trown at you right away when they happen but the cool part is that they are (sorta) categorized and the program can react according to the error and if possible try to its best to attempt to fix, cleanup, or something else for better results and user experience.