Well, I definitely like the looks of the TIMER_UNLOCK build option, but the multi-script thing kind-of looks like a bail-out for my competitors at first glance
I've already merged everything into 3 apps using conditionals and the "filesel" command (especially via "Options" -- which uses a header file and labels to merge scripts in a relatively open way that is easy to expand upon). Besides, unless V: is writable, there are several things in both "Settings" and "Options" that just wouldn't work if I tried to do it that way. Then again, I have been wishing there was something more flexible to replace my CBM9 Extras menu with (if you've seen the hoops I jumped through just to create fake submenus, it should be obvious why). I could place my SSR source scripts into the "scripts" folder straight, and just write one-liners to run the CFWs and apps. I'll think about it for R11. And some splash images for that matter, since it's using .pcx now. But R10 is practically ready to release, so, I don't want to hold it up further. I'll just re-compile the SSRs with TIMER_UNLOCK and release it, I think. Thanks again.
EDIT: Well, the new versions of Cakes Launcher and Settings were significantly larger in size (and they get copied to the card 6 times each). Those really don't perform heavy NAND access though (Settings offers to install GM9 if you try to use the "Switch Boot Firm" option without it installed, but aside from that, it never touches it). So, I'll stick with the copies of those I already had built (the configuration does have to fit on a RAM drive, along with some extra apps). But I think the timer unlock is worth taking a 70K hit to Options, Nand Manager, Sighax Updater, and especially the One & Done installer. I think it strikes the right balance -- reasonably protective without being overbearing or obnoxious.
EDIT2:
@d0k3: Well, there's a problem. I conducted my initial tests with Shove & Shift (which is the only thing that isn't using SSRs exclusively at this point). The build of GM9 I used for that worked alright. But no SSR I have built is running "autorun.gm9" for some reason. I'm aware that the build option has changed to "SCRIPT_RUNNER=1" and I'm using that, but it's just not working for some reason. Maybe TIMER_UNLOCK is interfering with it somehow.
EDIT3: Found it! Have a look at "Makefile.common" line 37. Changing it to "-DSCRIPT_RUNNER" seems to fix it. So, apparently it just wasn't setting the "SCRIPT_RUNNER" option. This also seems to have been what was causing the much larger file sizes (but that makes sense -- it was building a full GM9).