Change a4fea05a43b8fe57b9f43afeb6ed6bd88601c053, Reduce verbosity while reloading

[Aleix Pol]

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:
>> Hi,
>>
>> On Fri, Aug 17, 2012 at 6:56 PM, Milian Wolff <mail at milianw.de> wrote:
>>> Forwarding Aleix's message to the list:
>>> On Fri, Aug 17, 2012 at 4:43 PM, Milian Wolff <mail at milianw.de> wrote:
>>>> On Friday 17 August 2012 15:33:40 Aleix Pol wrote:
>>>>> On Wed, Aug 15, 2012 at 1:17 AM, Aleix Pol <aleixpol at kde.org> wrote:
>>>>> > On Tue, Aug 14, 2012 at 7:42 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>>>>> >> Hi,
>>>>> >>
>>>>> >> On Tue, Aug 14, 2012 at 7:32 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>>>>> >>> Hi,
>>>>> >>>
>>>>> >>> On Tue, Aug 14, 2012 at 1:31 PM, Aleix Pol <aleixpol at kde.org> wrote:
>>>>> >>>> On Tue, Aug 14, 2012 at 8:24 AM, Andreas Pakulat <apaku at gmx.de> wrote:
>>>>> What about reloading automatically files modified in disk that aren't
>>>>> modified in the IDE and that are not the current document? (I think
>>>>> the dialog is fine for the current document)
>>>>
>>>> No! (see Andreas' comment on accidental git checkout -f which sometimes can
>>> be
>>>> rescued by having the files still open)
>>>>
>>>>> This would solve most of our problems there and also would make us not
>>>>> to need the "Reload All" action.
>>>>> It's not that we open documents to preserve their state...
>>>
>>> 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.
>>
>> Andreas
>>
>> --
>> KDevelop-devel mailing list
>> KDevelop-devel at kdevelop.org
>> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
> 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"?
>
> Aleix
>
> PS: I'm trying to discuss this feature, it's not that I want to change
> this but I've received a lot of negative feedback in this area and I
> fear it's not really rationalized.

Or maybe we could consider using KMessageWidget in Kate instead of
QDialog as a middle-ground. :)

Aleix