Feature Requests

[glaucon1984]

Hi,

I would like to request some features that would make this project very useful, probably you are already aware, and I guess this is not as easy as it seems to implement, but just in case:

• Option to remember the position you were in the FAQ last time you opened it: Some FAQs are quite big and it's really hard to scroll all the way to the correct location of the document.

• Option to search within the FAQ: this might mitigate the issues above, but it's also a great functionality within itself.

• Option to cash/save FAQs locally, this could present a list of "recent FAQs" to make it easier to go back to them, also would allow to keep following a guide when internet is not available.

• I'm aware there could be some legal road bumps downloading guides, so an alternative for this would be to be able to load .txt files from a specific folder, maybe at /home/deck/something, this would bypass any issues related to the point above as it's the user who will download and store FAQs and this would still enable offline access to read them.

• I see you are working on supporting full-screen visualization of the guides, this would be great, I would suggest an option to use fixed-width fonts and 80 columns so ASCII art is properly visualized, sometimes it's just some fancy title, but sometimes it's a detailed map.

[hulkrelax]

Hi just wanted to update on these requests.

Regarding saving your position within a guide, if you don't close DeckFAQs, the guide does keep its last scrolled position. Obviously, if you close DeckFAQs, the position is no longer saved. I've thought about ways to save guide position and possibly at a later date I will implement something. At the moment, hopefully built-in search will ease the pain especially with the plain text guides (see next paragraph).

I am working on search for plain-text guides at the moment, and it should be available in the next release of DeckFAQs. Releases of DeckFAQs since v1.0.0 are only compatibility with the new pre-release of Plugin Loader (now called Decky Loader) so just keep that in mind. In addition to search, I'm also adding scrolling with the d-pad or analog stick so you can navigate through the guide without using the touch screen. Prior releases since you made this feature request have also added some new features like a table of contents for HTML guides, dark mode, and improved full screen guide support.

Regarding caching/saving guides locally, as you mentioned, it is a bit of a grey area so I'd rather not touch that right now. Even then, HTML guides span multiple pages so you can't necessarily just cache the entire guide without traversing every page for the guide. Plain-text guides obviously are easier because they are self-contained on one page but even then, it's not that much data to download.

As I mentioned before, I've improved full screen guides and the rendering of guides in general (in the quick access menu too). The formatting of plain-text guides in full screen mode is basically the same as you would see on the real site so hopefully that will satisfy your request. Obviously, there is only so much I can do rendering guides in the quick access menu but they mostly legible (with the exception of ASCII art)

Be on the lookout for the next release of DeckFAQs (probably v1.3.0) which should have scrolling with the gamepad and built-in search (as well as the other features I've added since)!

[theCroh]

Regarding saving your position within a guide, if you don't close DeckFAQs, the guide does keep its last scrolled position. Obviously, if you close DeckFAQs, the position is no longer saved. I've thought about ways to save guide position and possibly at a later date I will implement something. At the moment, hopefully built-in search will ease the pain especially with the plain text guides (see next paragraph).

Just an idea: Maybe you could utilize Chrome's (Chromium's?) "link to highlight" function for saving the location. I do this manually on mobile Vivaldi (i.e. when I stop using the guide, I create a link to the latest position and put that in the URL field). This way the guide opens from roughly correct position next time (as long as I keep the tab open).