[jboss-jira] [JBoss JIRA] (DROOLS-4086) [GSS-RFE] Search feature in GDST

[Michael Anstis (Jira)]

    [ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740108#comment-13740108 ] 

Michael Anstis commented on DROOLS-4086:
----------------------------------------

[~jfomin] Hi, I'd like to understand:-
#  _What_ text needs to be searchable? Header content? Cell content? Visible content or _all_ header content (e.g. a GDT's header only contains a couple of words, but these words are used to generate a much longer piece of text that can be seen on "hover over").
# _How_ should search be invoked? Popup? Dock? Keyboard shortcut? If some form of widget, how and where is the widget accessible?
# _Where_ are results to be shown? In a results panel? With link to _actual_ text? In-place? How do you iterate through matches?
# What about other assets?

[~davidredhat] Are there plans for anything like this in AppFormer? It seems a foundation type of requirement? For the two specific asset types listed I can walk the models "at search time" or I can index them at save time (although that means you can only search _saved_ files and not ones actively being edited). I think walking may be most reliable however it's likely to be the slowest too. Any plans for any form of indexing of dynamic content other than the Lucene/ES indexes we build atm?

[~uxdlc] This is likely to need UX involvement too.

> [GSS-RFE] Search feature in GDST
> --------------------------------
>
>                 Key: DROOLS-4086
>                 URL: https://issues.jboss.org/browse/DROOLS-4086
>             Project: Drools
>          Issue Type: Epic
>          Components: DMN Editor
>    Affects Versions: 7.23.0.Final
>            Reporter: Yevgeniy Fomin
>            Assignee: Yevgeniy Fomin
>            Priority: Major
>              Labels: drools-tools
>
> 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_H7dv4oPcdeA-cAXGo/edit#heading=h.cvb851c4kvxe] that advices what needs to be agreed before each feature implementation.
> h1. Requirement
> - The user would like to have additional search for text in *Guided Decision Table* and *Decision Model and Notation (DMN)* editor because standard browser search not allows to do it.
> - We may add auto-suggestion mechanism
> - Do we need search history?
> - 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.
> - The example text in the input field disappears when you enter the first character, and appears again, if the input field is empty. 
> h1. UX design
> - Add magnifying-glass icon.
> - Search-box can be popup window after clicking on icon or just pop field
> - The simple way is just create search inside of "Expression editor" or we can make search from "Graph editor" which return result from both "Expression editor" and "Graph editor" as a list, so it may looks as search we do in DMN data types tab. Also we can make separate search for both.
> 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.
> - Set of inputs:
> *- A-Z
> *- a-z
> *- 0-9
> *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + 
> *- Blank spaces



--
This message was sent by Atlassian Jira
(v7.12.1#712002)