Desktop App KoboPatchFan - a GUI application for Kobo patches

[Sirtel]

Originally Posted by Tommalka

But that's so much stuff again and somehow I don't feel it. Maybe I'll just implement a comparison of the complete .yaml files in a new tab? Then you could see at a glance what has changed. Maybe that would also be clearer?

I would be happy with this solution too. Many thanks.

[Tommalka]

Originally Posted by Skydog

How is that possible when the patches are not yet available?

The Kobo devices available for selection in Kobopatchfan are currently still hard-coded, so I have to release a new update for a new device. This has nothing to do with the availability of patches.

However I am currently working on fetching a list of all Kobos from Pgaskin's kfw.js, so that the devices are no longer hard-coded and can be updated using the "Update database" option in Kobopatchfan.

[Skydog]

Originally Posted by Tommalka

The Kobo devices available for selection in Kobopatchfan are currently still hard-coded, so I have to release a new update for a new device. This has nothing to do with the availability of patches.



However I am currently working on fetching a list of all Kobos from Pgaskin's kfw.js, so that the devices are no longer hard-coded and can be updated using the "Update database" option in Kobopatchfan.

Oh, I see. Thank you!

[codychan]

If it can upgrade the firmware as well, it would be perfect, although it is KOBOPATCHfan.

Ever consider merging upgrading firmware and patch into this one tool?

[InStim]

Thank you for the tool. I too avoided patching before, and your tool made it easy and removed any intimidation.

I have two suggestions that came to mind from my use.

In light of the long lists of patches I often found myself doubting what I have chosen. Two approaches to help come to mind. A button to toggle showing only the currently selected patches. Another approach might be to have a confirmation with the Run button to list the selected patches with Cancel/Continue buttons, before the patch is generated. I know there is the skip/applied in the generation output. I'd appreciate knowing easily while working.

When using the Export File button, after selecting the directory if it could state in the output something such as: "Please wait: Copy started." In my initial use I almost ejected the reader in my eagerness before the copy completed.

Thanks for the consideration, and thanks again for your work!

[InStim]

Another quick thought. An Eject Device button on the Generate Patch tab might be convenient.

[Tommalka]

Originally Posted by codychan

If it can upgrade the firmware as well, it would be perfect, although it is KOBOPATCHfan.

Ever consider merging upgrading firmware and patch into this one tool?

I have actually thought of this before (that's where the "Extract files after download"-checkbox in the download field originates from), but I found it unnecessary because it should be easier and faster via the https://pgaskin.net/KoboStuff/kobofirmware.html website. But since the Kobopatchfan always downloads the firmware as well, you can of course simply steal the file from the Kobopatch folder. Maybe I will add an export button for the firmware only.

[Tommalka]

Originally Posted by InStim

Thank you for the tool. I too avoided patching before, and your tool made it easy and removed any intimidation.

I have two suggestions that came to mind from my use.

In light of the long lists of patches I often found myself doubting what I have chosen. Two approaches to help come to mind. A button to toggle showing only the currently selected patches. Another approach might be to have a confirmation with the Run button to list the selected patches with Cancel/Continue buttons, before the patch is generated. I know there is the skip/applied in the generation output. I'd appreciate knowing easily while working.

When using the Export File button, after selecting the directory if it could state in the output something such as: "Please wait: Copy started." In my initial use I almost ejected the reader in my eagerness before the copy completed.

Thanks for the consideration, and thanks again for your work!

Originally Posted by InStim

Another quick thought. An Eject Device button on the Generate Patch tab might be convenient.

Thanks for the insights, these are great ideas that I definitely want to implement! I don't know to what extent I can access the eject function under Windows and Linux, but will have a look at it.

[geek1011]

Originally Posted by Tommalka

However I am currently working on fetching a list of all Kobos from Pgaskin's kfw.js, so that the devices are no longer hard-coded and can be updated using the "Update database" option in Kobopatchfan.

I would still keep a hard-coded copy around if I were you, as that part is likely to change on my next update (although that won't be for a while). The kfw.db.js format should remain the same forever though, as it's the most compact and compressible way to store it.