[JBoss JIRA] (ERT-71) Create Relevant Methods Completion Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-71?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-71:
-------------------------------
Assignee: Gorkem Ercan (was: Ian Stewart-Binks)
> Create Relevant Methods Completion Engine
> -----------------------------------------
>
> Key: ERT-71
> URL: https://issues.jboss.org/browse/ERT-71
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Gorkem Ercan
>
> If a user invokes code completion when trying to write an object's method, relevant methods of that object *that have already been used* in the current JS file should be proposed. This should be extensible enough such that relevant methods used outside of the file can be suggested in the future as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-66) Create Identifier Completion Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-66?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-66:
-------------------------------
Assignee: Gorkem Ercan (was: Ian Stewart-Binks)
> Create Identifier Completion Engine
> -----------------------------------
>
> Key: ERT-66
> URL: https://issues.jboss.org/browse/ERT-66
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Gorkem Ercan
>
> When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-65) Create Keyword Completion Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-65?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-65:
-------------------------------
Assignee: Ian Stewart-Binks
> Create Keyword Completion Engine
> --------------------------------
>
> Key: ERT-65
> URL: https://issues.jboss.org/browse/ERT-65
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Ian Stewart-Binks
>
> When a user invokes code completion, a list of contextually practical keywords should be suggested.
> * After a user has typed a few characters and invoked code completion, keywords prefixed by those few characters should be suggested. For instance, if the user has just typed 'del', 'delete' should be suggested. Similarly, if the user has just typed 'd', all of the keywords that start with the letter 'd' should be suggested.
> * Keywords based on relevance should also be suggested. For instance, consider the case when a user has begun a *do while* block. If the user writes the *do* and the *block* and invokes code completion, *while(<CR>);* should be one of the suggestions. A similar functionality for an *if else* should be implemented, as well.
> Questions:
> * Should keywords that match templates be suggested even though their template counterpart is in the list of suggestions?
> * Should keywords be suggested within JSDocs?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-66) Create Identifier Completion Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-66?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-66:
-------------------------------
Assignee: Ian Stewart-Binks
> Create Identifier Completion Engine
> -----------------------------------
>
> Key: ERT-66
> URL: https://issues.jboss.org/browse/ERT-66
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Ian Stewart-Binks
>
> When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-71) Create Relevant Methods Completion Engine
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-71?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-71:
-------------------------------
Assignee: Ian Stewart-Binks
> Create Relevant Methods Completion Engine
> -----------------------------------------
>
> Key: ERT-71
> URL: https://issues.jboss.org/browse/ERT-71
> Project: Eclipse Release Train
> Issue Type: Sub-task
> Components: JSDT
> Reporter: Ian Stewart-Binks
> Assignee: Ian Stewart-Binks
>
> If a user invokes code completion when trying to write an object's method, relevant methods of that object *that have already been used* in the current JS file should be proposed. This should be extensible enough such that relevant methods used outside of the file can be suggested in the future as well.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21669) Enable easy scaling of OpenShift 3 applications
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21669?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21669:
-----------------------------------------------
Looks like a duplicate of JBIDE-21634. [~mlabuda], please check it.
> Enable easy scaling of OpenShift 3 applications
> -----------------------------------------------
>
> Key: JBIDE-21669
> URL: https://issues.jboss.org/browse/JBIDE-21669
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: explorer, openshift_v3
>
> In Web-UI there is a spinner to set amount of running pods and we don't have something similar and user friendly in our tooling. At the moment to scale up/down an OpenShift 3 application, it is required to modify replication controller (which is a bit buggy see JBIDE-21665 and whole work flow is not quite user friendly). It would be nice to have a context menu item in context menu of a service, something like "Scale Up" enabled all the time and "Scale Down" in case there are at least 2 pods running. Or it could be "Add Pod" "Remove Pod" or something similar.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month