Instructions for patching firmware 3.18.0

[PeterT]

Gui in python? Leverage the calibre command line to run a python script maybe?? See http://manual.calibre-ebook.com/gene...bre-debug.html

[sherman]

Originally Posted by PeterT

Gui in python? Leverage the calibre command line to run a python script maybe?? See http://manual.calibre-ebook.com/gene...bre-debug.html

Hmm, maybe.

I was just going to use python with Tkinter.

Both require an external dependency (python or calibre).

I have used neither PyQT or Tkinter, although it wouldn't exactly be a complex GUI. Just some checkboxes/radiobuttons and maybe text input if required.

EDIT: And no, QT Creater/designer wouldn't be much use, as the idea is to create the GUI elements dynamically.

[Nick_1964]

Originally Posted by sherman

I would probably be willing to come up with some sort of GUI, if Geoff would be willing to standardise on a way of being able to determine mutually exclusive options, and determine which help text belongs with which patch.

EDIT: Basically, the idea would be to read the patch file(s) and dynamically create a GUI based on the contents of said file(s). That way a new GUI version would not need to be created for every new patch release.

It probably won't be pretty to look at though

I have totally no program skills,but a GUI in this case need to read the config files because the values change every time (hex address) and also there are very much added and changed patches,so in my idea, it would not be very simple...

[sherman]

Originally Posted by Nick_1964

I have totally no program skills,but a GUI in this case need to read the config files because the values change every time (hex address) and also there are very much added and changed patches,so in my idea, it would not be very simple...

I already have a Tkinter frame showing a whole bunch of checkboxes, as read in from the patch file(s).

At this stage, I'm concentrating on just enabling/disabling patches, and not setting any custom values.

Of course, the gui can't actually DO anything yet at this stage...

[Nick_1964]

Originally Posted by sherman

I already have a Tkinter frame showing a whole bunch of checkboxes, as read in from the patch file(s).

At this stage, I'm concentrating on just enabling/disabling patches, and not setting any custom values.

Of course, the gui can't actually DO anything yet at this stage...

Thats Nice, but u are aware that there is new firmware, and new patches ?
https://www.mobileread.com/forums/sho...d.php?t=268351

Patches:
https://www.mobileread.com/forums/sho...d.php?t=268407

[sherman]

Originally Posted by Nick_1964

Thats Nice, but u are aware that there is new firmware, and new patches ?
https://www.mobileread.com/forums/sho...d.php?t=268351

Patches:
https://www.mobileread.com/forums/sho...d.php?t=268407

Yes!!

The program reads the patch file(s), and creates a GUI based on the contents of said file(s). The idea is that such a program would work for any version of the patches.

[GeoffR]

What needs to be added to the patch files to allow for mutually axclusive alternatives?

Would ie be enough if I added a tag such as

patch_group = `Group name`

to each patch that was part of a mutually exclusive group?

Edit: But it would have to be commented out, unless I change the patch32lsb program to allow for it. So:

# patch_group = `Group name`

[sherman]

Originally Posted by GeoffR

What needs to be added to the patch files to allow for mutually axclusive alternatives?

Would ie be enough if I added a tag such as

patch_group = `Group name`

to each patch that was part of a mutually exclusive group?

Yeah, I could probably get that to work.

The hardest element will be obtaining help. I could dump everything inside the <patch> tags into the help system (the thought was to use tooltips), but that doesn't work when some of the help text is outside the patch tags.

Maybe have a [HELP patch_name1|patch_name2]...[/HELP] inside comments to mark the start and end of help text. Wouldn't hurt if it included any of the patching comments etc, just to make things simpler for everyone.

[JSWolf]

Originally Posted by sherman

Yeah, I could probably get that to work.

The hardest element will be obtaining help. I could dump everything inside the <patch> tags into the help system (the thought was to use tooltips), but that doesn't work when some of the help text is outside the patch tags.

Maybe have a [HELP patch_name1|patch_name2]...[/HELP] inside comments to mark the start and end of help text. Wouldn't hurt if it included any of the patching comments etc, just to make things simpler for everyone.

For any GUI to be useful to me, I need it to do a diff with another patch file so I can migrate my custom settings. Otherwise, it's not going to be useful at all.

[PeterT]

Why not write a configuration file out that shows what patches were selected on the previous run?

[sherman]

Originally Posted by PeterT

Why not write a configuration file out that shows what patches were selected on the previous run?

That's what I'm going to try out. More than just enabled/disabled settings as well if I can.

[Nick_1964]

Originally Posted by PeterT

Why not write a configuration file out that shows what patches were selected on the previous run?

The problem with that is that more patches come out and some patches changes, recently 3 or 4 patches are replaced by others..

[sherman]

Originally Posted by Nick_1964

The problem with that is that more patches come out and some patches changes, recently 3 or 4 patches are replaced by others..

It's not that hard.

In it's high level form, the logic could be something like this:

if saved_patch in current_patch_file:
    # use saved_patch data
else:
    # discard saved_patch data

Of course there are a number of details that need to be worked out, but that's the gist of it.

EDIT: Saving and restoring the enabled/disabled status of a patch is easy. I'm hoping to also be able to save and restore settings such as margins/font sizes that people may modify as well, but that is a much more difficult problem to solve without breaking the patches.

[poldroid]

Hi GeoffR, just a question.. I have Kobo Mini with software version (3.4.1), patching firmware of below is the correct patch?

Mark 4 Hardware: Mini !!!!
(31 Dec 2015)
96.2 MB - 98,517 KB - 100,881,356 bytes
http://download.kobobooks.com/firmwa...-3.19.5761.zip

Thanks in advanced,
POL

[DNSB]

Originally Posted by poldroid

Hi GeoffR, just a question.. I have Kobo Mini with software version (3.4.1), patching firmware of below is the correct patch?

Mark 4 Hardware: Mini !!!!
(31 Dec 2015)
96.2 MB - 98,517 KB - 100,881,356 bytes
http://download.kobobooks.com/firmwa...-3.19.5761.zip

Thanks in advanced,
POL

That would be the correct version for the Mini. Once it is updated, you can apply the patches for 3.19.5761.