MariusElvenwood Thanks! I plan to make a minor version update even though there's little interest. I also plan to generate better boards before a 1.0 release.
All of the GUI libraries attempt to make forms straight forward. There are always corner cases, and sparse documentation that doesn't suggest what else should be looked at or known. There's also the documentation that gets too technical with numbers, terms, and obscure internal keywords. I can't claim to be an expert on any of the GUI libraries that I've used but in short:
- Qt is great since it's LGPL 2 and it has working ports on many platforms!
- Qt's build system is very easy to pick up and probably the only that can be modified by both the user and its own IDE.
- The major cross-platform libraries have proprietary elements unlike Qt.
- Qt's design is easy to get into. Having worked in C++/MFC, C#/.Net probably adopted some of Qt's ideas.
- No intermediate byte code!
- Qt has a full test suite to verify client platforms.
All of the libraries are straight forward (somewhat). There are things I've learned on how to approach these libraries. This is probably the advise you are looking for:
- GUI code needs to be learned by creating sample programs.
- Be ready to play system administrator with development tools! Take setup notes.
- Know how to debug!
- Know and use lots of assertions!
- Push the limits of the library early.
- Find sample code.
- Copy exact lines of the sample code into your program for a starting point! Beware of hidden quirks because they are there and you don't know about them!
- Don't be afraid of higher level patterns.
- Don't be afraid of lower level work.
Even with Qt, I've come across a lack of information on topics where I found myself stuck and experimenting for long periods of time.