[scribus-dev] 0013867: Autosave triggers a comment to STDOUT (visible if we invoked Scribus from CLI)

[ale rimoldi]

hey

On 31/03/16 10:14, Juraj Fedel wrote:
> It is easy to printout message to console when autosave is done.
> I send patch to mantis for this.
> I also slightly changed the message showed on status bar.
>
> But i think this should be used only when you debug autosave behavior.
> It is really not that useful to have STDOUT cluttered with debugging
> messages in released program. I already found on console more debuging
> messages than i would like.
>
> Not sure really how useful for user is message printed in status bar
> (bug #13815) either. For user it should be transparent when autosave
> occur. To that end i do not think that autosave countdown widget is
> useful at all. I do not recall of any other program that have this
> feature. Scribus implementation of countdown widget is kind of nice but
> in my opinion too much eye catching, almost hypnotizing. Why should user
> be interested when file will be autosaved? Even worse is when countdown
> is not synchronized with actual autosaving time: this is not reliably
> reproduced but it occur sometimes - autosave is done couple seconds
> before of after countdown is done. Disclaimer: i tested it always only
> with 1 min interval, do not know how it behave with longer time
> interval.

thanks juraj.

i 100% agree with you.

we had a discussion about it a few days ago on irc, and the counter 
seems to make some people more confident that they won't be losing their 
work.

my stance is that, even if the counter and the messages might be 
fostering trust, that trust will disappear very soon, if the autosave 
mechanism almost never rescues your lost work.

the new dialog popping up when a documents is to be rescued is imo much 
more important. and if it works correctly in most cases, this is what 
will make the user more comfortable when working with experimental features!
then, you don't need any messages or widgets hypnotizing the user...

i'm also for removing the clock from the code and refraining from 
rendering status messages to the user.
every line of code that is not there, is a bug-free line of code :-)

ciao a.l.e