Quote:
Originally Posted by jackie_w
No-one with any long-term common sense wants you to do that. It would royally p*ss-off Kobo because you'd be depriving them of potential sales of high-end devices. It's a short step from there to them deciding to devote their efforts to locking down the firmware. Everybody would lose.
|
Yes, there's a reason why I haven't ever touched Dropbox or OverDrive in the patches, and don't even mention or respond to most requests.
Quote:
|
If you have these technical skills why don't you do something more productive with them than you've managed in the last couple of days? Perhaps geek1011 has some backburner projects he could send your way.
|
I don't really have much right now except the overly complex/time-consuming ones in red in the first post (screenshots setting entry, inverted rotated options in menu, etc).
Although, if skldmf/anyone else knows how to write Go, kobopatch.patchlib does need quite a bit of refactoring, especially the zlib css minification and the unit tests (they're a gigantic mess because they were written as I was learning how the whole patching process works and as I was still working on the design of kobopatch). It's not currently a priority for me, as it works well enough as it is, it won't need much future updates (there's only so many different ways you can modify a binary), and it has enough test coverage.