You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Kalinin (JIRA)" <ji...@apache.org> on 2019/01/17 07:23:00 UTC

[jira] [Commented] (IGNITE-10538) Make ignite-grid component for handling missing agent and cluster

    [ https://issues.apache.org/jira/browse/IGNITE-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744750#comment-16744750 ] 

Alexander Kalinin commented on IGNITE-10538:
--------------------------------------------

[~Klaster_1] I've implemented a prototype for no-data component. Please share you thoughts upon current realisation. https://github.com/apache/ignite/pull/5844/files

> Make ignite-grid component for handling missing agent and cluster
> -----------------------------------------------------------------
>
>                 Key: IGNITE-10538
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10538
>             Project: Ignite
>          Issue Type: Task
>          Components: wizards
>            Reporter: Vasiliy Sisko
>            Assignee: Alexander Kalinin
>            Priority: Major
>
> Currently we have such an aproach: When agent  or cluster is not availibe we block the whole screen and show a modal window with instructions (like in Notebooks screen). This approach is a bad UX case as it frustrates user with blocking and forcing to change state.
> We should implement a less obtrusive aproach by showing message in body of ignite-grid table, allowing user to stay on current state and not blocking the whole UI.
> This component should comply for following requirements: 
> 1) It sholuld be universal - applicable in context of any ignite-grid table usage.
> 2) Should handle common cases like missing agent or cluster under the hood.
> 3) Should have a possibility of enhancing for other special cases in different components.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)