[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21616 at 2/1/16 4:31 PM:
------------------------------------------------------------------
I bet this is only GTK3, right?
This remembers me JBIDE-16877 where we also had to relayout the parent to correct the vertical size of the combos
was (Author: adietish):
I bet this is only GTK3, right?
This remembers me JBIDE-16877
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21616:
------------------------------------------
[~snjeza] can you please confirm the findings? This looks very much like an issue in GTK3 again, I bet we should file a bugzilla.
[~mlabuda] can you please file this to Eclipse bugzilla for SWT/GTK3?
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21616:
-------------------------------------
It displays fine on OSX
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21616:
------------------------------------------
I bet this is only GTK3, right?
This remembers me JBIDE-16877
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-62:
----------------------------
Sprint: devex #1 February 2016
> Refactor JSDT Code Completion [EBZ#486776]
> ------------------------------------------
>
> Key: ERT-62
> URL: https://issues.jboss.org/browse/ERT-62
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Labels: General, bzira
>
> The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions.
> A proposal base for the code completion engine should include, but is not necessarily limited to:
> - Keywords
> - Identifiers (declared variables and functions in currently open JS file)
> - Recently used methods of functions (currently open JS file as a bare minimum)
> All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-62:
----------------------------
Story Points: 25
> Refactor JSDT Code Completion [EBZ#486776]
> ------------------------------------------
>
> Key: ERT-62
> URL: https://issues.jboss.org/browse/ERT-62
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Labels: General, bzira
>
> The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions.
> A proposal base for the code completion engine should include, but is not necessarily limited to:
> - Keywords
> - Identifiers (declared variables and functions in currently open JS file)
> - Recently used methods of functions (currently open JS file as a bare minimum)
> All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-62:
-------------------------------
Assignee: Ian Stewart-Binks
> Refactor JSDT Code Completion [EBZ#486776]
> ------------------------------------------
>
> Key: ERT-62
> URL: https://issues.jboss.org/browse/ERT-62
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Ian Stewart-Binks
> Labels: General, bzira
>
> The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions.
> A proposal base for the code completion engine should include, but is not necessarily limited to:
> - Keywords
> - Identifiers (declared variables and functions in currently open JS file)
> - Recently used methods of functions (currently open JS file as a bare minimum)
> All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month