View Single Post
Old 04-27-2018, 02:48 PM   #15
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,808
Karma: 7423683
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by jackie_w View Post
I'm going to assume that your aim is for the creator/maintainer of each patch to have as little work to do as possible (ideally none at all) for each new firmware. If so the 3rd option is the one least likely to change between firmwares, assuming one chooses the unique string wisely, of course.


Yes - for those who create/maintain patches. Not necessary for the average user, though.
OK. And yes, I'm trying to make the patching process as easy as possible for everyone. The only thing is I'm not going to make a feature to put the css back. For that, you'll need to make a patch and apply that instead.

Also, can someone who knows about the internals of the CSS patches like @oren64 or @GeoffR tell me a bit about how to extract it? I've been getting stuck on properly finding the right Zlib streams.
geek1011 is offline   Reply With Quote