[ https://issues.jboss.org/browse/WFCORE-2283?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2283: ---------------------------------------------- [~brian.stansberry] something that is missing in a filtering only approach is the ability to easily (without having to go to help) answer the question: Do all the required attributes have been set? If we complement the approach with a "Double Tab" of something like 500ms, we could expose all the remaining arguments annotated with relationships/attributes. ('*', <optional>, ...) It seems that required, requires and alternatives would be doable with the filtering approach: - Alternatives should be hidden as soon as a choice has been made. - Partly typed argument name should be completed if it exists and all its dependencies are resolved, being required or not. - Argument that depends on the presence of other arguments should be hidden until all the dependencies are present. That is in line with the way Commands are exposing options. - Requires relationship overrides the required attribute. Any attribute is exposed as soon as all its dependencies (if any) are resolved. In your example, let's imagine that: D - not required, requires A and C. E - required As soon as A and C are present, D is exposed along E although D is not required. Seems that users wouldn't have to think too much. They press Tab, and choose the argument they want to set. If lost, they press Tab twice and decode the exposed relationships. If that is not enough, they go to help. Going to help requires to clear the current line and type help <my operation>, then type again the operation (generally Paste again the operation that would have been previously copied). This is very inefficient and requires too much context switching. An inline help could be designed...more thinking needed there... Double tab, could be a first step toward it. JF -- This message was sent by Atlassian JIRA (v7.2.3#72005)