Why wxWidgets is related to embedded develoment?
It is not, well, ... it is equally related to embedded as desktop
I have changed a lot of wxWidgets code on the MSW part but also generic. There were some annoying bugs (like in the statusbar handling of text) but I also freely added stuff or changed behaviour of it.
I didn't like, as an example, the handling of menus. Why different approach for a menu with checkboxes than with icon's? But the changes of wxWidgets also changed the rest of the code, different function calls etc etc.
The objectives are a little bit different here. The goal (mission statement is a bit heavy I guess) is to make an user friendly embedded development suite for windows. An embedded development suite without all kind of tweaks etc. Working out of the box with the same experiences as if you would use uVision (my favourite at that moment). Once started, almost 2 years ago, I came across all kind of problems. I first kept a list with changes or bugs that I found but that was not workable, I was more administrating than programming. So the end result became more important than the backward compatibility with the used components like e.g. wxWidgets or codeblocks.
But EmBlocks is only suitable for embedded, it can't build desktop applications. All the desktop related stuff is removed from the source pool (like resource compiler, dynamic libraries etc). In the next release I will shrink it further by removing the 22px toolbar and the Batch/make file support. There is not much left of the original codeblocks code of 2 years ago and it is drifting further away with the day
Because it is a one man project, Github etc is at this moment a bit too much overhead. I have also a daytime job to do.
So yes, I wrote it.
