Kute File Monitor: A smarter file-trigger based launcher

[petrovich]

Originally Posted by DNSB

KoboRoot.tgz should wind up in the .kobo directory. Anywhere else, it's just a waste of space.

When you safely eject your Kobo, it should return to the normal GUI for a few seconds then install the KoboRoot.tgz and then reboot.

Looking at KFMon-v1.3.3.zip file and assuming you have no remnants from a previous install, you should see 2 new directories ( icons and .adds) and two new files (koreader.png and kfmon.png) in the root directories. If you look in the .kobo directory, you should see several directories and files, one of which should be KoboRoot.tgz.

If you are on a Unix style OS (Linux, Mac OSX), you will have to enable displaying hidden files/directories ( they start with a . ).

Yesss!! Many thanks. Indeed, I've completely forgot about hidden stuff, and instead of extracting to destination just copypasted the visible content of extracted locally. Thanks a lot!

[stiivo]

Hey i just followed this on my clara and successfully created a script to "mimic" usb connection to refresh the library on nickel (i did this as i set up an ftp connection from koreader so i can download my books from there).

My question might seem stupid so apologies in advance. I noticed that the png files for koreader and plato are set to either 1% or 99% progress. The png file i created to run my script was set to finished after i ran i the first time.

Is there a way to have this like the other pngs, meaning that it will always be in progress rather than finished

thanks in advance

[NiLuJe]

@stiivo: That's because both Plato & KOReader kill nickel, and you obviously don't .

(i.e., nickel doesn't have the opportunity to set the "Finished" flag on KOReader & Plato's icons. In a similar fashion, the 1% vs. 99% thing depends purely on timing).

[stiivo]

Thanks for the reply.

So its not possible to do so?

[NiLuJe]

You can obviously flag one as Finished manually (the long-tap menu and the Details pan won't trigger the action), but that'll only hold until the next time you tap it .

So, no, not really. Not unless you mangle the db yourself outside of Nickel.

[Yonder]

When trying to install this on my kobo glo (fw 4.20) I get the following error (after unmounting)

[KFMon] Userstore unavailable, aborting!

Some apps that were running fine on my Kobo Aura One don't launch. Any idea? Can I test if KFMon was properly installed in an easy way?

[NiLuJe]

@Yonder:

That's a reboot. Which is perfectly normal when installing a KoboRoot (because, guess what: it reboots the device ).

So, going to need actual details of what exactly you think is going wrong .

The default KFMon "book" will print the tail end of the log on screen, and, more interestingly, will dump the full thing to .adds/kfmon/log/kfmon_dump.log. Attach it here, and it should tell us exactly what's happening .

[NiLuJe]

Released v1.4.0!

Besides the usual updates and a few noteworthy bugfixes, this one implements a major new feature: an IPC mechanism, allowing scripts, or even GUI frontends, to list and trigger anything registered in KFMon .

You can play with the CLI tool (kfmon-ipc) that is now shipped with KFMon to see what's available (invalid/malformed commands will prompt a reply explaining what to do).

[geek1011]

And here's the GUI frontend NiLuJe was hinting at: https://www.mobileread.com/forums/sh...d.php?t=329525.

[NiLuJe]

Released v1.4.1!

Mainly a bunch of tweaks related to the OCP bundles, which were already live in said OCP packages .

Of interest:

* Allow deleting the PNG trigger *without* KFMon dropping the watch. This makes it IPC-only, which might come in handy to get something automagically enumerated in NickelMenu without having to maintain a different set of config for each launcher, now that the KFMon generator is live in NM.

* A stupid bug that would delete a *running* watch if an update to unrelated watch configs was detected.

[NiLuJe]

Released v1.4.2!

Mainly just to tag a release to catch up with what has been shipped with the OCP bundles for a while now .

Of notable interest, besides updating the various third-party libraries:

* Configs are now parsed in alphabetical order. This should ensure consistent behavior across devices, as this affects the order in which stuff is presented in frontends, like the KFMon generator in NickelMenu .

[Elektron]

Just wondering. Why does a firmware update brutally murder nickel?

[davidfor]

Originally Posted by Elektron

Just wondering. Why does a firmware update brutally murder nickel?

Because it can and actually knows what is happening? But, where do you get the impression that it "brutally murders" nickel? It does restart the device, but, I am pretty sure it will have told nickel to save whatever is need to first.

Or are you simply referring to the fact that the firmware updated doesn't prompt before installing and restarting the device?

[NiLuJe]

Was that perhaps one of your trademark first-draft-of-a-post typo, @Elektron, and you in fact meant "KFMon", instead of "nickel"?

In which case, I can answer that:

It's by design. There's a small, but non-zero chance that a Nickel update would break KFMon's expectations, and breaking those expectations might mean getting stuck in a boot loop. Which would be bad.

So, the trade-off is a wee bit of extra effort needed after an update, which is, personally, offset by the fact that that effort was already needed for the patches, and my own patching script includes reinstalling KFMon automatically, so, eh, water off a duck's back.

[Elektron]

LOL. Yes, I was asking about KFMon and yes, that's one of my trademark first draft posts ;P. Thanks.