Possibly, but it’s not something I’m thinking about. My Arduboy2 library is simply meant to quickly get something out there that is as close as possible to Arduboy API V1 but solves the issues that are described in my initial post in this topic.
The code currently on the master branch of the Arduboy Library, being referred to as V1.2, which I forked from, has been sitting in a mostly completed state for about 4 months, mainly waiting on the decision “Should we release this and break existing sketches which use the things that have changed and are no longer compatible, forcing these sketches to need updating?”.
Meanwhile, all this time developers have been asking and wishing for ways to make more code space available for their sketches. Arduboy2 addresses this, and a few other things, without having to deal with the issue of broken sketches because we can now leave the Arduboy library at API V1 and it can happily coexist in the IDE allongside Arduboy2.
Do you now want to spend more time, of an unknown duration, reworking Arduboy2 as you’ve suggested, while developers still keep asking how they can make more code space available for their sketches, and aren’t able to take advantage of any of the new features currently in Arduboy2? Why not accept Arduboy2 as is, and then continue to work on your proposals without pressure, eventually to be released as Arduboy API V3?