[FEATURE] Introduce Overview HTML page and time-based navigation links

[KnugiHK]

Discussed in #96

^{Originally posted by iher1 April 23, 2024}
Hi,
another idea to make it easier to consume many conversations and very huge chats would be:

• generate an index.html page which provides links to the specific chat entry pages
• when working with the --size parameter: have some sort of index at the beginning of each html page to quickly jump to
  • a certain subpage, like page 1 2 3 4 5 6 ...
  • jump to the first chat of a specific date, e.g. have links per year: 2020 2021 2022 2023

Regards
iheri1

[connect-mahdi]

Hi @KnugiHK
Really great script !!

As a follow-up on #69 and #96 :
There are tools from another great project tmo1/sms_ie . It extracts SMS messages and is provided with python tools for scrolling extracted messages through a browser. . Is it helpful for your implementation ?

[KnugiHK]

I briefly reviewed the script you mentioned and came up with a different idea: we could build a web application that retrieves messages from the JSON file or other formats and hence, implementing lazy loading in a better way. However, it seems like the script might not be directly related to this issue (feel free to correct me if I'm wrong).

[connect-mahdi]

@

I briefly reviewed the script you mentioned and came up with a different idea: we could build a web application that retrieves messages from the JSON file or other formats and hence, implementing lazy loading in a better way. However, it seems like the script might not be directly related to this issue (feel free to correct me if I'm wrong).

I have no developper skill so my understanding of the inner working of the python script is limited.
What I understand is that the json files inside the .zip are served by the web browser.
And I sought it could be done in the same way for the .html files generated by your script

Hope I understood your question. " lazy loading" isn't clear to me.
I have around 522 conversations on WhatsApp native app. So scrolling them in one web page instead of opening each .hml file from a file manager seemed a reasonable achievement and a nice step towards a clean User Experience, isn't it ?

[KnugiHK]

Hope I understood your question. " lazy loading" isn't clear to me.

Lazy loading is a technique that improves performance by loading only the content that's necessary for immediate display, like images and text visible on the screen, while deferring the loading of other content until the user scrolls down.

I have around 522 conversations on WhatsApp native app. So scrolling them in one web page instead of opening each .hml file from a file manager seemed a reasonable achievement and a nice step towards a clean User Experience, isn't it ?

Yeah. This issue is exactly for addressing the chat selection feature. The chat selection is designed at #97 (comment).