Desktop App KoboPatchFan - a GUI application for Kobo patches

[JSWolf]

I thought 1.1 was also supposed to handle customization to patches. So when is 1.2 coming out that handles this?

[Tommalka]

Originally Posted by JSWolf

I thought 1.1 was also supposed to handle customization to patches. So when is 1.2 coming out that handles this?

You can already customise patches since version 1.0 by clicking on Open Edit Mode in Tab (2). Or do you mean something else?

For the next version, I plan to check whether all backup-patches are actually included in the current patch files. Patches that are not (or no longer) present will then be displayed orange in the Backup-Patches tab with a warning and will be automatically deactivated, or something like that. Currently in version 1.1, there is simply an error message when generating if a backup patch is not available.

[JSWolf]

Originally Posted by Tommalka

You can already customise patches since version 1.0 by clicking on Open Edit Mode in Tab (2). Or do you mean something else?

For the next version, I plan to check whether all backup-patches are actually included in the current patch files. Patches that are not (or no longer) present will then be displayed orange in the Backup-Patches tab with a warning and will be automatically deactivated, or something like that. Currently in version 1.1, there is simply an error message when generating if a backup patch is not available.

I mean keeping track of the patches edited and what's been changed. Then we can see what's changed and if we want, we can do it again. And keep track of the changed patches in history.

[Tommalka]

Originally Posted by JSWolf

I mean keeping track of the patches edited and what's been changed. Then we can see what's changed and if we want, we can do it again. And keep track of the changed patches in history.

Although that would of course be cool, I think that's kind of overkill. I also simply don't have the time now to implement that

[Sirtel]

Originally Posted by Tommalka

Although that would of course be cool, I think that's kind of overkill. I also simply don't have the time now to implement that

It's not overkill if you use a lot of patches (I use more than 20). Sometimes it's hard to remember which ones you edited and how.

[JSWolf]

Originally Posted by Sirtel

It's not overkill if you use a lot of patches (I use more than 20). Sometimes it's hard to remember which ones you edited and how.

I agree. It's not overkill. Without this, this patch GUI is not useful at all (IMHO).

[Asawi]

Originally Posted by JSWolf

I agree. It's not overkill. Without this, this patch GUI is not useful at all (IMHO).

Maybe not for everyone. But certainly for some of us that only use a few patches.
I appreciate it. Those that don't can just not use it.
Having said that, I'm sure the developer appreciates feedback and maybe at some later point can implement these wishes!

[JSWolf]

Originally Posted by Asawi

Maybe not for everyone. But certainly for some of us that only use a few patches.
I appreciate it. Those that don't can just not use it.
Having said that, I'm sure the developer appreciates feedback and maybe at some later point can implement these wishes!

They aren't wishes. They are features that without makes this program not at all useful.

[Tomifonication]

Just to say I find your application extremely useful and it allowed me to do in minutes what would've taken me likely an hour, if not more.

Ignore the negativity in this thread; this is great work for a new app and I look forward to using it more.

Thanks!

[Asawi]

Originally Posted by JSWolf

They aren't wishes. They are features that without makes this program not at all useful.

Maybe not for you. But here's something that might come as a surprise: Different people have different needs.
Not useful for you (and others) can still be useful for somone else.

[DNSB]

I would have to agree. That your work does not have all the features that it could have does not make it less useful for those who do not need those features or are willing to wait for them to be implemented.

[dreambeat]

I agree, I find this GUI is very helpful. Thank you for making it!

[Tommalka]

Thank you for the feedback! I will release a small update in the next few days to support the new Kobo Elipsa 2E.

Originally Posted by JSWolf

I agree. It's not overkill. Without this, this patch GUI is not useful at all (IMHO).

I understand your frustration. Maybe you can explain again in detail and in detail and maybe with a layout diagram how you imagine it best.

My approach would be like this:

• Add a checkbox "Keep track of this patch" for each patch.
• If checked, the code of the patch is written to a separate file.
• The patches saved in this way are displayed in a new tab. There is a button "Compare this patch with the fresh patch". The changes... I don't know how to show the changes. The old code on the left and the new code on the right?
• There must be an option to edit the saved patch code directly to adapt it to the fresh patch if necessary. And then there is a button "Overwrite fresh patch file" to write the saved patch into the fresh patch file and thus overwrite the fresh patch with your own patch.

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?

[JSWolf]

Originally Posted by Tommalka

I understand your frustration. Maybe you can explain again in detail and in detail and maybe with a layout diagram how you imagine it best.

My approach would be like this:

• Add a checkbox "Keep track of this patch" for each patch.
• If checked, the code of the patch is written to a separate file.
• The patches saved in this way are displayed in a new tab. There is a button "Compare this patch with the fresh patch". The changes... I don't know how to show the changes. The old code on the left and the new code on the right?
• There must be an option to edit the saved patch code directly to adapt it to the fresh patch if necessary. And then there is a button "Overwrite fresh patch file" to write the saved patch into the fresh patch file and thus overwrite the fresh patch with your own patch.

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?

That does sound good. Thank you.

[Skydog]

Originally Posted by Tommalka

Thank you for the feedback! I will release a small update in the next few days to support the new Kobo Elipsa 2E.

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