[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21719:
--------------------------------------
Assignee: Viacheslav Kabanovich
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21719:
----------------------------------------
{quote}default width of right lower part is increased to make more space for Properties view and to let user see that he can adjust it without changing editor area.{quote}
I like this idea.
So it will look like on this screenshot?
!JBossPerspective_PropertiesMayBeWider.png|thumbnail!
I'm voting +1 to the proposed PR (need to be tested though, cc: [~ldimaggio]), [~maxandersen] WDYT?
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21863) WatchManager makes multiple callbacks for same event
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21863 at 3/14/16 4:50 PM:
------------------------------------------------------------------------
When WatchManager.stopWatch is called in the context of DeploymentResourceMapper.buildDeployments(), it seems buildDeployments() does not want that watch for this project be restarted until it explicitly calls in finally block WatchManager.getInstance().startWatch(project). So, maybe in this context a flag may be set on WatchManager and calls to WatchListener for the project may be just ignored until buildDeployments() explicitly restarts the watch and remove the flag?
was (Author: scabanovich):
When WatchManager.stopWatch is called in the context of DeploymentResourceMapper.buildDeployments(), it seems buildDeployments(project) does not want that watch for this project be restarted until it explicitly calls in finally block WatchManager.getInstance().startWatch(project). So, maybe in this context a flag may be set on WatchManager and calls to WatchListener for the project may be just ignored until buildDeployments() explicitly restarts the watch and remove the flag?
> WatchManager makes multiple callbacks for same event
> ----------------------------------------------------
>
> Key: JBIDE-21863
> URL: https://issues.jboss.org/browse/JBIDE-21863
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21863) WatchManager makes multiple callbacks for same event
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21863:
-----------------------------------------------
When WatchManager.stopWatch is called in the context of DeploymentResourceMapper.buildDeployments(), it seems buildDeployments(project) does not want that watch for this project be restarted until it explicitly calls in finally block WatchManager.getInstance().startWatch(project). So, maybe in this context a flag may be set on WatchManager and calls to WatchListener for the project may be just ignored until buildDeployments() explicitly restarts the watch and remove the flag?
> WatchManager makes multiple callbacks for same event
> ----------------------------------------------------
>
> Key: JBIDE-21863
> URL: https://issues.jboss.org/browse/JBIDE-21863
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years