or just make it even simpler - if connection failed add a marker on the
connection but don't empty the model.
When clicking Refresh it will try again and if connection succeeds it
goes back to refreshing regularly.
No need for a second "Enable Connection" option in that IMO ?
/max
I would propose another option:
when the refresh detects that the docker daemon is not reachable, it
does
not stop refreshing but rather switch to a failed state and increase
the
refresh timer (following a kind of fibonnacci or exponentioal factor).
If
the user expand and connection is in failed state, then we should
reset the
timer and try to fetch data.
WDYT ?
Jeff
On Wed, Jun 8, 2016 at 2:03 PM, Martin Malina <mmalina(a)redhat.com>
wrote:
> Thanks for the suggestion. Yes, it's not a bad idea I think. I do
> understand why they came up with the disabled state - when you have
> Docker
> images view open, the view will keep being refreshed periodically, so
> disabling the connection when the docker daemon is down makes some
> sense.
> But yes, perhaps it could still be expandable in the Docker Explorer
> and
> expanding would enable the connection. I will suggest this in the BZ.
>
> -Martin
>
>
>> On 7. 6. 2016, at 18:29, Alexey Kazakov <alkazako(a)redhat.com> wrote:
>>
>> What if you make a docker connection always expandable and try to
>> enable
>> the connection when you are trying to expand it?
>>
>> On 06/07/2016 10:04 AM, Martin Malina wrote:
>>> Hi all,
>>>
>>> We are looking into ways to improve the Docker Tooling UI in
>>> Eclipse
> and would like to ask for help.
>>>
>>> Xavier and I discussed one scenario which is currently quite
>>> confusing,
> it is described here:
>>>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=495600
>>>
>>> In short, this is the use case:
>>> 1. Start CDK
>>> 2. Connect to Docker
>>> 3. Stop CDK
>>> 4. Start CDK
>>> 5. Connect to Docker
>>> - here I was failing for a long time until Xavier told me I needed
>>> to
> click this "Enable Connection" button, to make the connection work
> again.
>>> This issue was previously discussed here:
>
https://issues.jboss.org/browse/JBDS-3739
>>>
>>> We would appreciate if any of you had any suggestions how to
>>> improve
> this.
>>>
>>> Thanks
>>> Martin
>>>
>>> --
>>> Martin Malina
>>> JBoss QA Engineer
>>> Red Hat Czech s.r.o.
>>> Purkynova 99
>>> 612 45 Brno, Czech Republic
>>>
>>> Tel.: +420 532 294 265
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev >
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev