mkgtu

joined 1 year ago
6
submitted 1 year ago* (last edited 1 year ago) by mkgtu to c/hermit
 

Is there a way to get the reader View icon permanently into the address bar for easy access? Seems to me there used to be a way this happened.

I recall opening the settings sidebar to turn on the reader view for an article displayed on the screen. That opened the reader view, and after closing that article the Reader icon remained in the address bar so you could easily access it again. It would be great if it could always be there, at least on pages with eligible text.

One of my major complaints about the Chrome browser is that the invitation to use "simplified view" only appears for a few seconds when you first open an eligible article. But once it's gone you can't get it back. There is a setting in Chrome to "always" show the icon in the address bar. But in effect "always" becomes an unpredictable "sometimes".

I use Edge as my default Android (and Windows) browser partly because it consistently shows the "Reader" icon in the address bar on any page with convertible text. The Yandex browser does the same.

I wish Hermit did also so you don't have to keep opening the sidebar to get at the reader icon.

[–] mkgtu 1 points 1 year ago

Ok. I figured it out. I used collections to get this extension installed on both Firefox Beta and Firefox Nightly on Android. And the extension seems to work fine till it gets stuck on "downloading zip". All the files were processed and "completed" but it gets stalled at the actual zip.

Any ideas why this may be happening? I tried the same book on FF desktop on PC and it worked perfectly.

[–] mkgtu -1 points 1 year ago (3 children)

Very good extension, but it would be even better if you could make one for Chrome (and therefore for other chromium based browsers as well).

Firefox is not as widely used and this extension is also limited to the desktop FF browser because mobile Firefox can't install this extension.

On the other hand, a chromium extension would work on a variety of desktop chromium based browsers, most prominently Chrome and Edge. But it could also be installed on the two mobile chromium based browsers, KIWI and YANDEX for Android, both of which can install full desktop extensions from the Chrome WebStore.

Of note, LIBBY AUDIOBOOK EXPORTER is a very good, simple and fast Chrome extension that works in all the above platforms. But it creates multiple mp3 files instead of a single one, and the resulting book does not display chapters in as many players.

[–] mkgtu 1 points 1 year ago

Noting the edit in my previous comment about the Chrome extension LIBBY AUDIOBOOK EXPORTER.

It also works in the KIWI and YANDEX android mobile browsers, both of which are the only chromium based mobile browsers that can install full desktop extensions from the Chrome WebStore website.

This is great if you are like me and prefer to keep all these processes on your phone and not have to hop back and forth between computer and phone. And I found this extension works even smoother on my phone. (Could it be that my phone has a much faster processor and more CPU cores than my computer?)

[–] mkgtu 2 points 1 year ago

PROBLEM SOLVED Somebody must have heard the cries. CONNECT was just updated today July 31 2023 from the Play Store. I tried out the updated version and in another thread, and in this one also, I am able to type as much as I want. And as the typing nears the bottom of the typing box, it automatically scrolls visibly to a new line so you can always see what you're typing. Nothing goes under the keyboard anymore.

Excellent 👍 Kudos and karma to the attentive, responsive developer for fixing this. I can now stick with CONNECT rather than Jerboa.

[–] mkgtu 3 points 1 year ago

Unfortunately I have to consider myself an addict. I do read (and listen) a lot, but I seem to "collect" more than I'll ever be able to get to. And I keep on adding to the collection. From Libby mostly, I tend to add (permanently by many means) just about anything I see recommended in reviews, on Reddit, etc.

I'm 78. I'll ever get to even 2% of them 😠 I'm sick in the head 🤣

[–] mkgtu 1 points 1 year ago* (last edited 1 year ago) (1 children)

Another method I've tried, and it seems to work well, uses the extension LIBBY AUDIOBOOK EXPORTER in Chrome. I suppose it would also work in other chromium based browsers, like Edge, Brave etc It also works in the chromium based MOBILE browsers KIWI and YANDEX, which can both install Chrome desktop extensions from the Chrome WebStore.

It works much like the Firefox extension in that you don't have to play or scan the book. just open the Libby audioboooks on the Libby website. You might need to refresh the Libby page at least once, maybe a couple of times to engage the extension. It then displays at the top of the webpage and after it scans the book in the background you just hit the EXPORT button and it begins downloading all the files. There's a green progress bar that shows the downloading.

Unlike the Libby Download extension in Firefox, this extension downloads multiple files. As each one gets downloaded the "Save" box opens and you pick where to save each file. The default is the computer's default Download folder. You can choose another, like your books folder, but sadly this extension won't remember that choice on the next file, so you'd have to change it each time. A bit of a pain. So I just let everything go to the Download folder. When everything was finished, I moved all the files to a folder I had created for the book.

One of the files that gets created and downloaded is called "openbook.json" This is similar to the .CUE file that you get with the Firefox extension. It contains metadata, chapter break location info, etc. The trouble is all the current Android 3rd party players can't read this JSON file. The book will play ok, but you'll just see "parts", not chapters.

HOWEVER, if you use LISTEN audiobook player, you will soon find that it will be able to decipher the info in the JSON file and will be able to display chapters. The current version 5.0.15 cannot read the JSON file info. But I emailed the developer yesterday (July 30 2023) and explained the issue. In less than an hour he had reworked some of the code he wrote to deal with similar metadata files so that it could also read and use the JSON file info. He added it to the LISTEN app and sent me a copy of the updated app (now version 5.0.16). I don't know when the new version will appear in the Play Store. The last update was only a week ago, but I presume this new, or an even newer, update should come along in the next week or so. Look for any version greate than 5.0.15.

[–] mkgtu 1 points 1 year ago

Sorry to keep droning on, but I'm now typing another reply in the reply/comment box, but this is being typed in Jerboa and I can type as much as I want and am still able to see all the text I am typing. Unfortunately even in Jerboa the text gets hidden under the keyboard at about 9 lines, but you can manuallly nudge the screen up a bit to see new lines. I cannot do that in Connect.

[–] mkgtu 1 points 1 year ago

The font size is larger as you type, so you get 6½ lines before it gets hidden. That's about 4½ of the smaller sized font in the published reply.

[–] mkgtu 1 points 1 year ago* (last edited 1 year ago) (1 children)

Experiment failed. In the above reply the reply box auto scrolled for about 4⅐ of those lines. The everything else got hidden under the keyboard and I could type no more. Well, I could keep on typing, I just couldn't see what I was writing. However, strangely enough, I've added these last several lines to my original reply by using the "edit" function, and using "edit" you can keep typing and at least manually scroll down to see text that gets hidden under the keyboard.

[–] mkgtu 1 points 1 year ago (3 children)

I do reboot every morning. But I did as you suggested right now and cleared the cache, restarted the phone and am now typing this reply in Connect. Sorry to keep typing but I wanted to see how far I can type.

[–] mkgtu 1 points 1 year ago (5 children)

Actually I think I'm seeing something like that also. I think when I type an original post or even a regular comment, then it's possible to scroll down and see what you're typing. But doesn't work for "replies". In those, after five or six lines everything echoes hidden under the keyboard.

May be a Lemmy problem that the connect app can't overcome. I'm typing this in Jerboa. The reply box here hides text under the keyboard also. Doesn't automatically scroll as it should, but at least in Jerboa you an manually scroll down. In Connect for Lemmy you can't.

2
can't see text while typing (self.lemmyconnect)
submitted 1 year ago by mkgtu to c/[email protected]
 

When typing replies the text box does not scroll down as you type. So after a few lines the text starts getting buried under the keyboard. You can't even manually scroll down the page to bring your typing into view.

For me, this renders the whole app useless.

 

Even at the "larger" size I have to squint to see the comnents. Way too small.

view more: next ›