Quote:
Originally Posted by ah-
It's meant to be like this, due to how nickel loads plugins. It might be possible to get the plugin loaded some other way, but for the moment it's ok and actually has some advantages. Image a fault in a plugin that automatically loads on start and causes nickel to crash. The only option to delete it would be to do a factory reset by holding home during boot, as USB and Wifi are controlled by nickel, and nickel would be dead.
|
It would be interesting to see if you could try a hybrid approach of some kind - when the plugin is first installed, make the user manually start like you do now, then provide an option in your tweaks menu to 'auto-start' ?
Another approach might be to try and write to a state file - write to the file when you start loading the plugin, before you do anything else, and again when it loads successfully. Next time you boot up the device, check that file - if the plugin didn't load properly last time, don't try and load it this time? Hopefully thereby preventing the need for the occasional factory reset...
All of this, of course, assumes that there *is* a way to have a plugin, or something similar, load automatically... I'm definitely interested in looking around, seeing what I can figure out as well, but I thought I'd see what all other people had figured out.
Also, has anyone put together any kind of package of the files needed to start developing, or is everyone setting things up manually every time?
