Todo list for 1.0 Release

[gyrovorbis]

If you've been following libGimbal at all, you'll know that it has never actually had an official release... because it was pretty much only used by me internally for the longest time...

Fast forward a few years, and suddenly I have a bunch of people using it, contributing to it and doing cool shit with it... and while I have sooooooo many features I want to see eventually make it in, I've created a list of essentials for the upcoming 1.0 release. Here they are, in case anyone is interested or wants to weigh-in.

Sorry, I'm a notebook guy... lol.

Basically, the gist is, that I need to finish up some of the macro DSL stuff, for declaring:

1. GBL_SIGNALS()
2. GBL_ENUM()
3. GBL_FLAGS()

which will automatically declare them within the C language and register them within the type sytem.

Then I have a few things I've been adding to the type system over the last few days, such as a GblBox::finalize signal which gets fired right before destruction commences after the last hard reference is freed, allowing for the implementation of weak references.

I just implemented a GblObject::propertyChanged signal, which was a ROYAL PITA to get to only emit when a property truly changed (GTk does it no matter what and is lazy). I'm still unit testing, though.

Then finally, the #1 thing I want to fix... is get rid of all of the disgusting GBL_CTX_XXX() macro bullshit that plagues a bunch of the internals, and the GblContext type that goes with it... instead GblLogger, GblAllocator, and GblError will be disjoint constructs which will be used to implement all of the same behavior without the insanity...

Unfortunately that last one might take awhile to untangle and refactor, because it's ubiquitous in the back-end. :)

[Haikuno]

Very excited for this! Can't believe this lib can get even better.