Change a4fea05a43b8fe57b9f43afeb6ed6bd88601c053, Reduce verbosity while reloading

[Andreas Pakulat]

Hi,

On Mon, Aug 20, 2012 at 2:35 AM, Aleix Pol <aleixpol at kde.org> wrote:
> On Mon, Aug 20, 2012 at 2:29 AM, Aleix Pol <aleixpol at kde.org> wrote:
>> On Fri, Aug 17, 2012 at 8:33 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>>> On Fri, Aug 17, 2012 at 6:56 PM, Milian Wolff <mail at milianw.de> wrote:
>>>> Well, I'd consider this more of a side-effect than a feature that
>>>> forces us to workaround the UI with things like Reload All. Also if
>>>> you wanted that, the only you'd have to do is to modify the file...
>>>
>>> I think we could offer this as an option to the user. We should
>>> definetly do a reload-all automatically if the user does a git
>>> checkout or something similar inside the IDE, but if files are
>>> modified outside of kdevelop you cannot know wether that was
>>> intentional or not so kdevelop shouldn't reload automatically (unless
>>> the user explicitly decided to do that by setting an option) since it
>>> means unrecoverable data loss in the worst case which is the worst
>>> thing that can happen to any of us.
>>
>> I agree, on the other hand if this happens, it's not KDevelop's
>> responsibility (if it happens outside KDevelop).
>>
>> For example, if there's data loss, it will be only recovered in the
>> opened documents not the whole project. Should we recognize "make sure
>> the data is preserved" as a use case for "opening a file"?
>
> Or maybe we could consider using KMessageWidget in Kate instead of
> QDialog as a middle-ground. :)

Thats the expanding widget on top? I don't think thats intrusive
enough for a case where data can be lost. This is ok in cases such as
a browser asking wether it should save the password or translate the
web-page. But these 'passive popups' are too easy to overlook.

And the other thing is that passive-popups allow to simply ignore
them, for the reload-dialog this is a no-go. The user must take a
decision on it, otherwise the editor can't continue.

Oh and regarding the feedback you got about KDevelop, you should make
notes about the specific points the users raise. If they just say
something like 'it sucks' or 'it doesn't work' then I'd suggest to
simply ignore them, there are always people who just want to rant.
Only precise critics can be used to improve something, everything else
is just garbage.

Andreas