It's primary design principle is simplicity. This means that if a feature will make the codebase cluttered, it is dropped until it can be implemented in a clean way.
Ok, so in the beginning, back with AcessOS/AcessBasic, there was AxWin. It was my attempt at making
a GUI system, and to an extent, it worked... although I never wrote anything real for it. Then I
started work on AxWin2, which was going to be a very tablet/iOS style interface. There would be no
windows, just full screen tabs. This turned out to be a nightmare to implement, and the lack of
dialogs would have crippled it.
So, I started planning AxWin3. This sat unloved in the git tree for quite a while, until not long
after the 0.13 release, I started really working on it. 0.14 is the first GUI release, however
stability is questionable.
On that note, I plan to finish bugfixing everything sometime soon (at least for this round of
features) and release 0.15
In preparation for the UWA open day next weekend, I have been
giving the Acess2 networking code a real workout using the telnet ASCII Star Wars stream from
towel.blinkenlights.nl (thanks to the guys who made that)
After several days of fixing fiddly bugs (including some dumb ones in non-networking code), I
managed to get the entire show to play through. :)
The next week will be spent cleaning up some little issues and getting the display presentable, so I
can show it off for the UCC's stand.
So, finally after three months, I've uploaded a new release file. Most of the changes between the
two versions have been in the networking code (implementing routing tables, cleaning up usability
issues).
Aside from that, there were a heap of bugs fixed and issues resolved (e.g. user apps shouldn't be
able to segfault and take out the kernel any more)