<div dir="ltr"><div dir="ltr">> Exactly, auto save is just not how desktop software generally works.<br>><br>> Cheers,<br>> Albert<br></div>Could we implement the backup method for Okular?<div><br></div><div>Best,</div><div>Wen<br><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><<a href="mailto:okular-devel-request@kde.org">okular-devel-request@kde.org</a>> 於 2024年7月18日 週四 下午7:00寫道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Okular-devel mailing list submissions to<br>
<a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:okular-devel-owner@kde.org" target="_blank">okular-devel-owner@kde.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Okular-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [okular] [Bug 490337] Allow to get PDF passwords from a<br>
org.freedesktop.secrets service (yan12125)<br>
2. [okular] [Bug 490337] Allow to get PDF passwords from a<br>
org.freedesktop.secrets service (Albert Astals Cid)<br>
3. Re: Add autosave function to Okular (Albert Astals Cid)<br>
4. Re: Add autosave function to Okular (Wen Chang)<br>
5. [okular] [Bug 490435] New: printing from the selected range<br>
of pages does not work correctly (Nazar)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 17 Jul 2024 13:59:53 +0000<br>
From: yan12125 <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: [okular] [Bug 490337] Allow to get PDF passwords from a<br>
org.freedesktop.secrets service<br>
Message-ID: <<a href="http://bug-490337-85596-IgPGCqe1St@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490337-85596-IgPGCqe1St@http.bugs.kde.org/</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=490337" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490337</a><br>
<br>
--- Comment #2 from yan12125 <<a href="mailto:yu3actxt2tttfimx@chyen.cc" target="_blank">yu3actxt2tttfimx@chyen.cc</a>> ---<br>
Ah, I forgot the main point: I use neither KDE nor kwalletd. Instead, I use<br>
KeePassXC as a cross-platform solution to manage all my secrets. That program<br>
also provides org.freedesktop.secrets service like kwalletd. If Okular supports<br>
org.freedesktop.secrets, I can just use KeePassXC instead of setting up another<br>
secrets service for PDF passwords.<br>
<br>
-- <br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 17 Jul 2024 20:19:56 +0000<br>
From: "Albert Astals Cid" <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: [okular] [Bug 490337] Allow to get PDF passwords from a<br>
org.freedesktop.secrets service<br>
Message-ID: <<a href="http://bug-490337-85596-yNCrJ0qU5B@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490337-85596-yNCrJ0qU5B@http.bugs.kde.org/</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=490337" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490337</a><br>
<br>
--- Comment #3 from Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>> ---<br>
Ok, i guess that makes some sense, I wouldnt' be against such feature.<br>
<br>
-- <br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 17 Jul 2024 23:22:41 +0200<br>
From: Albert Astals Cid <<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: Re: Add autosave function to Okular<br>
Message-ID: <2416547.6LXrqp22Eu@xps15><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
El dimecres, 17 de juliol del 2024, a les 7:26:20 (CEST), Laura David Hurka va <br>
escriure:<br>
> On Wed, 17 Jul 2024 11:01:53 +0800 Wen Chang wrote:<br>
> > I can do it that way by saving the changes in a backup file.<br>
> > <br>
> > I would like to know why modifying the file on disk without user<br>
> > interaction is a bad idea based on your experience.<br>
> > <br>
> > Also, I noticed that VSCode automatically saves changes once they are<br>
> > made.<br>
> > To my knowledge, only the file that the user is working on will be<br>
> > modified.<br>
> > <br>
> > What drawbacks would there be if a file is directly modified without user<br>
> > interaction?<br>
> <br>
> Drawback would be that it is unusual and unexpected for many users (unless<br>
> the user explicitly configured it that way).<br>
> <br>
> Imagine you have a form that you need to fill out often, and then just print<br>
> once.<br>
> If changes are saved automatically, you can’t use the file the next time<br>
> anymore, because it is already filled.<br>
> <br>
> It would also not make much sense with “Open...”, “Save”, and “Save As...”.<br>
<br>
Exactly, auto save is just not how desktop software generally works.<br>
<br>
Cheers,<br>
Albert<br>
<br>
> <br>
> Laura<br>
<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 18 Jul 2024 11:28:31 +0800<br>
From: Wen Chang <<a href="mailto:changyaowen19980629@gmail.com" target="_blank">changyaowen19980629@gmail.com</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: Re: Add autosave function to Okular<br>
Message-ID:<br>
<<a href="mailto:CAKPy6qvpTJeYnfT6v_qB0pB1TJEpkUE8gProHN-mrGxEz_rA9w@mail.gmail.com" target="_blank">CAKPy6qvpTJeYnfT6v_qB0pB1TJEpkUE8gProHN-mrGxEz_rA9w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
That's indeed the concern of the autosave method.<br>
Thanks for letting me know.<br>
About your concern, I provide my suggestion as follows:<br>
<br>
> Drawback would be that it is unusual and unexpected for many users<br>
(unless the<br>
> user explicitly configured it that way).<br>
<br>
The autosave function is disabled by default. Once the user clicks the<br>
button to turn it on, changes will be saved automatically. This ensures<br>
that users are aware they are in autosave mode. Additionally, autosave will<br>
remain enabled the next time the user opens Okular.<br>
<br>
Does implementing the method this way make more sense? Feel free to let me<br>
know.<br>
> If changes are saved automatically, you can’t use the file the next time<br>
> anymore, because it is already filled.<br>
<br>
In this situation, I suggest saving a backup file whenever the user closes<br>
Okular. This would create a list of backup files in a folder located in the<br>
same directory as the document. Users would then be able to roll back by<br>
checking different versions of the backup files.<br>
<br>
To my understanding, the current policy in Okular does not allow users to<br>
revert to the original version of a file once they have saved it manually,<br>
right? Please correct me if I am mistaken. Thanks.<br>
<br>
Best,<br>
Wen<br>
<<a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a>> 於 2024年7月17日 週三 下午7:00寫道：<br>
<br>
> Send Okular-devel mailing list submissions to<br>
> <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:okular-devel-request@kde.org" target="_blank">okular-devel-request@kde.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:okular-devel-owner@kde.org" target="_blank">okular-devel-owner@kde.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of Okular-devel digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: Add autosave function to Okular (Laura David Hurka)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Wed, 17 Jul 2024 07:26:20 +0200<br>
> From: Laura David Hurka <<a href="mailto:laura.stern@mailbox.org" target="_blank">laura.stern@mailbox.org</a>><br>
> To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
> Subject: Re: Add autosave function to Okular<br>
> Message-ID: <6009722.DvuYhMxLoT@doro><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> On Wed, 17 Jul 2024 11:01:53 +0800 Wen Chang wrote:<br>
> > I can do it that way by saving the changes in a backup file.<br>
> ><br>
> > I would like to know why modifying the file on disk without user<br>
> > interaction is a bad idea based on your experience.<br>
> ><br>
> > Also, I noticed that VSCode automatically saves changes once they are<br>
> made.<br>
> > To my knowledge, only the file that the user is working on will be<br>
> modified.<br>
> ><br>
> > What drawbacks would there be if a file is directly modified without user<br>
> > interaction?<br>
><br>
> Drawback would be that it is unusual and unexpected for many users (unless<br>
> the<br>
> user explicitly configured it that way).<br>
><br>
> Imagine you have a form that you need to fill out often, and then just<br>
> print<br>
> once.<br>
> If changes are saved automatically, you can’t use the file the next time<br>
> anymore, because it is already filled.<br>
><br>
> It would also not make much sense with “Open...”, “Save”, and “Save As...”.<br>
><br>
> Laura<br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> Okular-devel mailing list<br>
> <a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of Okular-devel Digest, Vol 214, Issue 22<br>
> *********************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.kde.org/pipermail/okular-devel/attachments/20240718/0caf1ab8/attachment-0001.htm" rel="noreferrer" target="_blank">http://mail.kde.org/pipermail/okular-devel/attachments/20240718/0caf1ab8/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 18 Jul 2024 07:21:26 +0000<br>
From: Nazar <<a href="mailto:bugzilla_noreply@kde.org" target="_blank">bugzilla_noreply@kde.org</a>><br>
To: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Subject: [okular] [Bug 490435] New: printing from the selected range<br>
of pages does not work correctly<br>
Message-ID: <<a href="http://bug-490435-85596@http.bugs.kde.org/" rel="noreferrer" target="_blank">bug-490435-85596@http.bugs.kde.org/</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
<a href="https://bugs.kde.org/show_bug.cgi?id=490435" rel="noreferrer" target="_blank">https://bugs.kde.org/show_bug.cgi?id=490435</a><br>
<br>
Bug ID: 490435<br>
Summary: printing from the selected range of pages does not<br>
work correctly<br>
Classification: Applications<br>
Product: okular<br>
Version: 23.08.1<br>
Platform: Microsoft Windows<br>
OS: Other<br>
Status: REPORTED<br>
Severity: normal<br>
Priority: NOR<br>
Component: printing<br>
Assignee: <a href="mailto:okular-devel@kde.org" target="_blank">okular-devel@kde.org</a><br>
Reporter: <a href="mailto:nazar2692@gmail.com" target="_blank">nazar2692@gmail.com</a><br>
Target Milestone: ---<br>
<br>
SUMMARY<br>
printing from the selected range of pages does not work correctly<br>
<br>
STEPS TO REPRODUCE<br>
1. File<br>
2. Printing<br>
3. Pages: page range 1,3,5<br>
4. Button - Print<br>
<br>
OBSERVED RESULT<br>
prints only the currently displayed page, rather than the selected page range<br>
<br>
EXPECTED RESULT<br>
<br>
<br>
SOFTWARE/OS VERSIONS<br>
Windows: Windows 11 Home<br>
macOS: <br>
Linux/KDE Plasma: <br>
(available in About System)<br>
KDE Plasma Version: <br>
KDE Frameworks Version: 5.109.0<br>
Qt Version: 5.15.10<br>
<br>
ADDITIONAL INFORMATION<br>
<br>
-- <br>
You are receiving this mail because:<br>
You are the assignee for the bug.<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Okular-devel mailing list<br>
<a href="mailto:Okular-devel@kde.org" target="_blank">Okular-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/okular-devel" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/okular-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Okular-devel Digest, Vol 214, Issue 23<br>
*********************************************<br>
</blockquote></div></div></div>