[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-16636 at 2/27/14 5:12 PM:
----------------------------------------------------------------
[~maxandersen], I faced some troubles when I tried to read Alt key:
UBUNTU:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Shift* keys. It does not work with *Alt* key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press *Alt* and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Alt* keys. It does not work with *Shift* (called but does not change operation)
My suggestion is to use *Ctrl*.
I will check MacOs also
WDYT?
was (Author: dazarov):
[~maxandersen], I faced some troubles when I tried to read Alt key:
UBUNTU:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Shift* keys. It does not work with *Alt* key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press *Alt* and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Alt* keys. It does not work with *Shift* (called but does not change operation)
My suggestion is to use Ctrl.
I will check MacOs also
WDYT?
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16649:
-------------------------------------
The whole KeyBinding manipulation is a pretty ugly hack. For some reason, we need to modify and save the Bindings after each workspace restart. But I think we can live with it though.
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.1.2.CR1
>
>
> Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, -we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-16636 at 2/27/14 5:11 PM:
----------------------------------------------------------------
[~maxandersen], I faced some troubles when I tried to read Alt key:
UBUNTU:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Shift* keys. It does not work with *Alt* key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press *Alt* and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with *Ctrl* and *Alt* keys. It does not work with *Shift* (called but does not change operation)
My suggestion is to use Ctrl.
I will check MacOs also
WDYT?
was (Author: dazarov):
[~maxandersen], I faced some troubles when I tried to read Alt key:
There are two ways which I tried:
UBUNTU:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Shift keys. It does not work with Alt key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press Alt and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Alt keys. It does not work with Shift key at all.
My suggestion is to use Ctrl.
I will investigate how Mac works with keys.
WDYT?
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16649:
-------------------------------------
Denis, can you please review and apply the PR?
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.1.2.CR1
>
>
> Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, -we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Description:
Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, -we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
was:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.1.2.CR1
>
>
> Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, -we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Assignee: Denis Golovin (was: Fred Bricon)
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.1.2.CR1
>
>
> -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Description:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
was:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Description:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
was:
Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.
The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-16636 at 2/27/14 5:03 PM:
----------------------------------------------------------------
[~maxandersen], I faced some troubles when I tried to read Alt key:
There are two ways which I tried:
UBUNTU:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Shift keys. It does not work with Alt key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press Alt and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Alt keys. It does not work with Shift key at all.
My suggestion is to use Ctrl.
I will investigate how Mac works with keys.
WDYT?
was (Author: dazarov):
[~maxandersen], I faced some troubles when I tried to read Alt key:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Shift keys. It does not work with Alt key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press Alt and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
My suggestion is to use Shift instead.
WDYT?
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Summary: Deactivate the Maven Profile Management if m2e 1.5 is installed (was: Restrict Maven Profile Management to m2e < 1.5)
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.
> The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months