On 12/21/2012 06:28 AM, Pavel Sanda wrote:
... Let's move the discussion to the devel list ...
Jean-Marc Lasgouttes wrote:
Le 21/12/2012 11:32, Scott Kostyshak a écrit :
On Fri, Dec 21, 2012 at 5:07 AM, Liviu Andronic <landronim...@gmail.com>
wrote:
I would suggest that we _always_ have a warning when, after opening a
LyX file, the user activates a dangerous converter for the _1st time_.
It shouldn't be possible to "don't ask me again". The logic of this
would be that the warning is sufficiently intrusive to catch the
attention of casual or hardcore users of the dangerous converter, but
it is not intrusive enough to become a pain for those hardcore users:
The warning will pop up only once, when first trying to compile a
file. On the 2nd compilation this warning will be disabled, etc. If
the user closes and re-opens the file, the 1st time
activation-of-dangerous-converter warning should pop up again.
This is a good suggestion; I didn't think about this possibility. I'm
guessing that most users will find it too intrusive (although much
less than if it popped up on every compilation). I personally would be
fine with this though.
I would personnally find it too intrusive...
No strong opinions, but from the proposals I find the most convenient:
1. add 'dangerous' flag in converter(s) as proposed by JMarc
2. config option to disable warnings.
3. pop-up with warning after file opening - it can be even without
don't ask me again, but there should be information 'You can disable
these warnings in Preferences'. This way we assure that people really
read the whole message without blind clicking and yet we offer
possibility for geeks not to be obtrused.
I think we need two kinds of "disabling" options: global, and per file.
Otherwise, too many people will be tempted to disable globally, only
because they do not want to be warned every time they open a certain
sort of file.
My suggestion was that the per-file disabling should be done on the
basis of a per-user UUID we generate at installation, or some such time
(and, as Scott suggests, can re-generate if need be). This is not
perfect. If someone had your UUID, they could put that into the file,
etc. But it would be better than disabling globally.
If it didn't seem good enough, there are more complicated things we
could do. E.g., calculate a hash of the file contents each time we save
it, and then encode that hash using a per-user key. Then if the file
were externally modified, you'd get warned again, and no-one would be
able to send you files marked as safe for you.
Richard
