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