[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Comment: was deleted
(was: [~aglass] Thanks for adding feedback here. I defer to [~bdellasc]'s direction wrt iconography. One concern that I have that might factor into the icon selection is the distinction between Find and Search. For this initial feature Find is scope to locating text within the canvas view and highlighting it. Conceptually this feels different to Search to me. Plus Search in DMN is reductive (so actually it's more like Filter...). And "Search" is what we currently offer on the Data Type tabs. If you perform a search there the list is reduced, if there are results:
!Screen Shot 2019-07-12 at 3.01.12 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.01.30 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.08.47 PM.png|thumbnail!
Maybe we want to rethink the Search function in data types in favor of find or something else, not sure, but I just wanted to raise the different functionality that's being supported. Based on my recollection of the icon selection, it was intended to indicate this difference.
[~karreiro] Wrt tooltip presentation/implementation issue that Amy mention, wdyt? ^^)
> [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
> -------------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, Screen Shot 2019-07-12 at 3.01.12 PM.png, Screen Shot 2019-07-12 at 3.01.30 PM.png, Screen Shot 2019-07-12 at 3.08.47 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9...
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton edited comment on DROOLS-4142 at 7/12/19 3:16 PM:
--------------------------------------------------------------------
[~aglass] Thanks for adding feedback here. I defer to [~bdellasc]'s direction wrt iconography. One concern that I have that might factor into the icon selection is the distinction between Find and Search. For this initial feature Find is scope to locating text within the canvas view and highlighting it. Conceptually this feels different to Search to me. Plus Search in DMN is reductive (so actually it's more like Filter...). And "Search" is what we currently offer on the Data Type tabs. If you perform a search there the list is reduced, if there are results:
!Screen Shot 2019-07-12 at 3.01.12 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.01.30 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.08.47 PM.png|thumbnail!
Maybe we want to rethink the Search function in data types in favor of find or something else, not sure, but I just wanted to raise the different functionality that's being supported. Based on my recollection of the icon selection, it was intended to indicate this difference.
[~karreiro] Wrt tooltip presentation/implementation issue that Amy mention, wdyt? ^^
was (Author: uxdlc):
[~aglass] Thanks for adding feedback here. I defer to [~bdellasc]'s direction wrt iconography. One concern that I have that might factor into the icon selection is the distinction between Find and Search. For this initial feature Find is scope to locating text within the canvas view and highlighting it. Conceptually this feels different to Search to me because search in DMN is reductive (so actually it's more like Filter...). And "Search" is what we currently offer on the Data Type tabs. If you perform a search there the list is reduced, if there are results:
!Screen Shot 2019-07-12 at 3.01.12 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.01.30 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.08.47 PM.png|thumbnail!
Maybe we want to rethink the Search function in data types in favor of find or something else, not sure, but I just wanted to raise the different functionality that's being supported. Based on my recollection of the icon selection, it was intended to indicate this difference.
[~karreiro] Wrt tooltip presentation/implementation issue that Amy mention, wdyt? ^^
> [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
> -------------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, Screen Shot 2019-07-12 at 3.01.12 PM.png, Screen Shot 2019-07-12 at 3.01.30 PM.png, Screen Shot 2019-07-12 at 3.08.47 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9...
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton edited comment on DROOLS-4142 at 7/12/19 3:15 PM:
--------------------------------------------------------------------
[~aglass] Thanks for adding feedback here. I defer to [~bdellasc]'s direction wrt iconography. One concern that I have that might factor into the icon selection is the distinction between Find and Search. For this initial feature Find is scope to locating text within the canvas view and highlighting it. Conceptually this feels different to Search to me because search in DMN is reductive (so actually it's more like Filter...). And "Search" is what we currently offer on the Data Type tabs. If you perform a search there the list is reduced, if there are results:
!Screen Shot 2019-07-12 at 3.01.12 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.01.30 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.08.47 PM.png|thumbnail!
Maybe we want to rethink the Search function in data types in favor of find or something else, not sure, but I just wanted to raise the different functionality that's being supported. Based on my recollection of the icon selection, it was intended to indicate this difference.
[~karreiro] Wrt tooltip presentation/implementation issue that Amy mention, wdyt? ^^
was (Author: uxdlc):
[~aglass] Thanks for adding feedback here. I defer to [~bdellasc]'s direction wrt iconography. One concern that I have that might factor into the icon selection is the distinction between Find and Search. For this initial feature Find is scope to locating text within the canvas view and highlighting it. Conceptually this feels different to Search to me because search is reductive. And Search is what we currently offer on the Data Type tabs. If you perform a search there the list is reduced, if there are results:
!Screen Shot 2019-07-12 at 3.01.12 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.01.30 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.08.47 PM.png|thumbnail!
Maybe we want to rethink the Search function in data types in favor of find, not sure, but I just wanted to raise the different functionality that's being supported. Based on my recollection of the icon selection, it was intended to indicate this difference.
[~karreiro] Wrt tooltip presentation/implementation issue that Amy mention, wdyt? ^^
> [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
> -------------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, Screen Shot 2019-07-12 at 3.01.12 PM.png, Screen Shot 2019-07-12 at 3.01.30 PM.png, Screen Shot 2019-07-12 at 3.08.47 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9...
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-4142:
-------------------------------------------
[~aglass] Thanks for adding feedback here. I defer to [~bdellasc]'s direction wrt iconography. One concern that I have that might factor into the icon selection is the distinction between Find and Search. For this initial feature Find is scope to locating text within the canvas view and highlighting it. Conceptually this feels different to Search to me because search is reductive. And Search is what we currently offer on the Data Type tabs. If you perform a search there the list is reduced, if there are results:
!Screen Shot 2019-07-12 at 3.01.12 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.01.30 PM.png|thumbnail! !Screen Shot 2019-07-12 at 3.08.47 PM.png|thumbnail!
Maybe we want to rethink the Search function in data types in favor of find, not sure, but I just wanted to raise the different functionality that's being supported. Based on my recollection of the icon selection, it was intended to indicate this difference.
[~karreiro] Wrt tooltip presentation/implementation issue that Amy mention, wdyt? ^^
> [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
> -------------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, Screen Shot 2019-07-12 at 3.01.12 PM.png, Screen Shot 2019-07-12 at 3.01.30 PM.png, Screen Shot 2019-07-12 at 3.08.47 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9...
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4142) [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4142?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4142:
--------------------------------------
Attachment: Screen Shot 2019-07-12 at 3.08.47 PM.png
> [GSS-RFE] UX design: Find feature in GDST/DMN 7.5
> -------------------------------------------------
>
> Key: DROOLS-4142
> URL: https://issues.jboss.org/browse/DROOLS-4142
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.23.0.Final
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png, Screen Shot 2019-07-12 at 3.01.12 PM.png, Screen Shot 2019-07-12 at 3.01.30 PM.png, Screen Shot 2019-07-12 at 3.08.47 PM.png
>
>
> This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation.
> h1. Requirements
> See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9...
> h1. Documentation
> - Replace picture of GDT and DMN editor where they become obsolete
> h1. Acceptance test
> - Enter to large amount of data in search box
> - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed.
> - Searching for non-existing result
> - Result appearing once
> - Result appearing multiple times
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - +
> *- Blank spaces
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ELY-1838) Differentiate actions and parameters
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/ELY-1838?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1838:
----------------------------------
Comment: was deleted
(was: Related to this I see the tool does attempt to detect if duplication options have been specified but it doesn't attempt to verify that only one "action" has been specified - the actions are however handled in an if/else set of statements so only one will be executed.)
> Differentiate actions and parameters
> ------------------------------------
>
> Key: ELY-1838
> URL: https://issues.jboss.org/browse/ELY-1838
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Command-Line Tool, Credential Store
> Reporter: Darran Lofthouse
> Assignee: Ilia Vassilev
> Priority: Major
>
> The help information in the tool lists all parameters for a specific command, however some are general parameters and some are mutually exclusive actions - the output from the tool should make this distinction clear.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ELY-1838) Differentiate actions and parameters
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/ELY-1838?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1838:
---------------------------------------
Related to this I see the tool does attempt to detect if duplication options have been specified but it doesn't attempt to verify that only one "action" has been specified - the actions are however handled in an if/else set of statements so only one will be executed.
> Differentiate actions and parameters
> ------------------------------------
>
> Key: ELY-1838
> URL: https://issues.jboss.org/browse/ELY-1838
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Command-Line Tool, Credential Store
> Reporter: Darran Lofthouse
> Assignee: Ilia Vassilev
> Priority: Major
>
> The help information in the tool lists all parameters for a specific command, however some are general parameters and some are mutually exclusive actions - the output from the tool should make this distinction clear.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months