Suppose that a guy (because the problem is general, not just for me) wants to create a dialog plugin for Orbiter, without going mad with WinAPI and .rc files.
Say he doesn't want to buy Visual Studio.
He needs a free widget:
[ame="http://en.wikipedia.org/wiki/Widget_toolkit"]Widget toolkit - Wikipedia, the free encyclopedia[/ame]
or framework? or toolkit? Well, you got it anyway.
There are a lot of options.
Windows:
http://en.wikipedia.org/wiki/List_of_widget_toolkits#On_Microsoft_Windows
Cross platform (ok, Orbiter currently isn't, but you never know, and some cross-platform software may be better anyway):
http://en.wikipedia.org/wiki/List_o...B_.28including_bindings_to_other_languages.29
What do you think should the guy choose? Especially taking into consideration that:
* he may want to share the code/development with other fellow orbinauts, so the toolkit can't be too difficult to learn and should be well-known;
* the toolkit needs to decently fit with Orbiter API and Visual C++ (since, unless I'm wrong, VC++ should be used anyway for the final DLL compatibility - ?).
Forgetting all this and just going for good-old-WinAPI-code-solution is also an acceptable answer, just please elaborate/verbalize motivations.
Discussion is open.
Say he doesn't want to buy Visual Studio.
He needs a free widget:
[ame="http://en.wikipedia.org/wiki/Widget_toolkit"]Widget toolkit - Wikipedia, the free encyclopedia[/ame]
or framework? or toolkit? Well, you got it anyway.
There are a lot of options.
Windows:
http://en.wikipedia.org/wiki/List_of_widget_toolkits#On_Microsoft_Windows
Cross platform (ok, Orbiter currently isn't, but you never know, and some cross-platform software may be better anyway):
http://en.wikipedia.org/wiki/List_o...B_.28including_bindings_to_other_languages.29
What do you think should the guy choose? Especially taking into consideration that:
* he may want to share the code/development with other fellow orbinauts, so the toolkit can't be too difficult to learn and should be well-known;
* the toolkit needs to decently fit with Orbiter API and Visual C++ (since, unless I'm wrong, VC++ should be used anyway for the final DLL compatibility - ?).
Forgetting all this and just going for good-old-WinAPI-code-solution is also an acceptable answer, just please elaborate/verbalize motivations.
Discussion is open.