Lacewing Android has been funded!

Hey folks,
Lacewing Android was funded in one fell swoop by a single CT user!

With the work still needed for Lacewing Unicode, it will take a while before I can work on Android, but after Unicode is released, I simply have to package and polish the two other Patreon goals for release: the Tree Lister and SQL extension.
Polishing those shouldn't take more than a few days. Then it's Android time.

Current state of play with Lacewing Android is I got the codebase to compile, but was unable to get it to work at runtime, and found it tricky to debug. Since it was mainly a proof-of-concept for what would evolve into the DarkEdif MultiTarget SDK, I didn't push hard on that project; spent a couple days but dropped it in favour of something easier to work with.

Now the MultiTarget SDK works on any ABI for Android (at the cost of a somewhat large file size), and with the fixes for Lacewing Blue, and optimisations done to the DarkEdif SDK, it's definitely looking likely that Android will be a very intense extension.

After that, I'll have to add the goals for

• DarkEdif smart property system - no more incompatible MFAs when properties are changed
• DebugObject update - which will drastically change Fusion debugging and logging
• Web Query Object for Android
• JWT upgrades to Web Query Object, to aid with use in REST queries
• Intense Functions Object - which will drastically change how folks code at all, even with child events, IFO introduces a vastly more modular coding system. From its release, it will be both Unicode and Android-compatible.
  With Uppernate's new scoping extension and work he's done on scoping, IFO can be more fleshed out; I originally dropped it because I was hitting a mental block with how to pass objects to functions, and preserve scoping.
  The A/C/E IDs are generated by the extension at runtime for the most part, and should I change the design of functions, MFAs using the old function object will fail to load... and if it's as impactful an extension as I expect, it'll be an extreme pain to comment out all use of the A/C/E.

There's also Lacewing for HTML5... but arguably, that will impact Patreon users a lot less, as multiplayer HTML5 isn't something everyone is working on, despite popularity of agar.io, slither.io etc. Should I choose to add those goals, I'll likely add them before HTML5, and thus make HTML5 a larger-cost goal; but I'll do a poll for the patrons if switching the goals seems like a good option.

Thanks for the patronage folks!

Cheers,
~Phi