[Okular-devel] [Bug 301774] Wish: New option to save embedded annotation upon change/document close

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=301774

--- Comment #9 from Till Schäfer <till2.schaefer at uni-dortmund.de> ---
OK we might all come down a bit and stay on technical discussion. The goal
should be to get the best software...

@Albert Astals Cid: 
well every feature can have bugs. so if this is not experimental or in
development, what does it make different from saving a file in kate,
libreoffice or any other tool that is out there? I think this was a little bit
confusing. 

At least you may acknowledge that if you save your file very often the save as
gets realy anoing, since once you have saved one annotation internaly you have
to save every change also internaly. So you will end up with 50 different file
versions.. always check if it correctly saves everything and than delete them.
This does not seem to be a propper, matured and productive workflow.  The
question is how we can get safety and a good workflow together. 

if hte poppler backend is not reliable, "save as" does not prevent me from
overwriting files. I used it this way and where not warned that this may cause
data loss in any way by okular. So maybe it is better to introduce a "save"
function but inform the user in a dialog that this is still some kind of
experimental and he should keep backups. If there is an option to disable the
disalog, this solution would not stay in the way, but still gives the user all
information he/she needs. if the poppler feature is matured you can remove that
dialog at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.