Quote:
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.
|
The Problem with that is that to do anything like it we need to get nickel to load our code. Nickel tries to load plugins for scanning the files on the internal storage and viewers for different file formats. It only does that when they're potentially needed, for example upon opening the library. Before that, the plugin isn't loaded at all and can't execute any code.
It might be possible to get it loaded sooner by posing as a Qt plugin, but I'm not sure if it's worth the effort.
Quote:
|
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?
|
You have to do that manually at the moment. But it's not too difficult, you mainly need three things: The koboplugins source (just clone the github repository), the codesourcery arm toolchain and the rest of the kobo development environment (see
http://blog.ringerc.id.au/2011/01/pr...nment-for.html). Note that you need to change the compile flags for qt, as described on the first page of this thread.
I hope that's all, if you need more assistance I'd be happy to help.