[JBoss JIRA] (JBIDE-17807) index.html of HTML5 kitchensink example is not displayed in VPE visual part
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17807?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17807:
------------------------------------------------
Moreover, it is reproducible also for preview. Make it small enough and put refresh button. Empty screen must appear.
> index.html of HTML5 kitchensink example is not displayed in VPE visual part
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17807
> URL: https://issues.jboss.org/browse/JBIDE-17807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3-v20140706-0939-B172
> Linux
> SWT_GTK3=0
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: snapshot11.png, snapshot12.png, snapshot6.png, snapshot7.png, snapshot9.png, vpepreviewblank.png
>
>
> 1. Import HTML5 kitchensink project from JBoss Central
> 2. Open index.html in VPE
> ERROR: Visual part of VPE is blank
> HTML Preview is showing page properly.
> 3. Run JBT with arguments -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false
> ASSERT: Page is displayed correctly in Visual part of VPE
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3099) No Early Access features in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3099?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3099:
--------------------------------
Assignee: Nick Boldt
> No Early Access features in Central
> -----------------------------------
>
> Key: JBDS-3099
> URL: https://issues.jboss.org/browse/JBDS-3099
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Affects Versions: 8.0.0.Beta3
> Environment: JBDS 8.0.0.Beta3b
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Priority: Critical
>
> There are no Early Access features in Central and there is error in error log:
> {noformat:title=Provisioning exception}
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta....
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.jboss.tools.central.editors.xpl.P2CachedRepoUtil.getRepoForConnector(P2CachedRepoUtil.java:41)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveConnectorUnits(ConnectorDescriptorItemUi.java:428)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$3(ConnectorDescriptorItemUi.java:427)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:309)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> JBT 4.2.0.Beta3b seems not to be affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3099) No Early Access features in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3099?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3099 at 7/21/14 10:25 AM:
------------------------------------------------------------
Seems like when [~mickael_istria] released JBDS 8.0.0.Beta3b to QE staging he forgot to create the target platform folder.
I've fixed that so https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta... now exists.
[~rhopp], please try again.
was (Author: nickboldt):
Seems like when [~mickael_istria] released JBDS 8.0.0.Beta3b to QE staging he forgot to create the target platform folder.
I've fixed that so https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta... now exists.
Please try again.
> No Early Access features in Central
> -----------------------------------
>
> Key: JBDS-3099
> URL: https://issues.jboss.org/browse/JBDS-3099
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Affects Versions: 8.0.0.Beta3
> Environment: JBDS 8.0.0.Beta3b
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Priority: Critical
>
> There are no Early Access features in Central and there is error in error log:
> {noformat:title=Provisioning exception}
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta....
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.jboss.tools.central.editors.xpl.P2CachedRepoUtil.getRepoForConnector(P2CachedRepoUtil.java:41)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveConnectorUnits(ConnectorDescriptorItemUi.java:428)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$3(ConnectorDescriptorItemUi.java:427)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:309)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> JBT 4.2.0.Beta3b seems not to be affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3099) No Early Access features in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3099?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3099:
----------------------------------
Seems like when [~mickael_istria] released JBDS 8.0.0.Beta3b to QE staging he forgot to create the target platform folder.
I've fixed that so https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta... now exists.
Please try again.
> No Early Access features in Central
> -----------------------------------
>
> Key: JBDS-3099
> URL: https://issues.jboss.org/browse/JBDS-3099
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Affects Versions: 8.0.0.Beta3
> Environment: JBDS 8.0.0.Beta3b
> Reporter: Radim Hopp
> Priority: Critical
>
> There are no Early Access features in Central and there is error in error log:
> {noformat:title=Provisioning exception}
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta....
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.jboss.tools.central.editors.xpl.P2CachedRepoUtil.getRepoForConnector(P2CachedRepoUtil.java:41)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveConnectorUnits(ConnectorDescriptorItemUi.java:428)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$3(ConnectorDescriptorItemUi.java:427)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:309)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> JBT 4.2.0.Beta3b seems not to be affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17807) index.html of HTML5 kitchensink example is not displayed in VPE visual part
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17807?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17807:
------------------------------------------------
What actually must be if screen is too small for 2013 html5kickstart(and what happens on windows and on Linux with gtk3) - mobile version of this index page must be shown. Unfortunately, there is something which old xulrunner does not supports. So you get absolute empty screen.
> index.html of HTML5 kitchensink example is not displayed in VPE visual part
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17807
> URL: https://issues.jboss.org/browse/JBIDE-17807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3-v20140706-0939-B172
> Linux
> SWT_GTK3=0
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: snapshot11.png, snapshot12.png, snapshot6.png, snapshot7.png, snapshot9.png, vpepreviewblank.png
>
>
> 1. Import HTML5 kitchensink project from JBoss Central
> 2. Open index.html in VPE
> ERROR: Visual part of VPE is blank
> HTML Preview is showing page properly.
> 3. Run JBT with arguments -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false
> ASSERT: Page is displayed correctly in Visual part of VPE
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17939) Move JMX Navigator location to bottom left
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17939?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-17939:
---------------------------------------
Probably the ones we own would be a good start - JBoss and Web Development.
> Move JMX Navigator location to bottom left
> ------------------------------------------
>
> Key: JBIDE-17939
> URL: https://issues.jboss.org/browse/JBIDE-17939
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jmx, server
> Affects Versions: 4.2.0.Beta3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
>
> I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view.
> It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once.
> Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work.
> We need it to work for both scenarios:
> 1. Server -> Shown in JMX Navigator
> 2. Open the JMX Navigator using Window -> Show view
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17807) index.html of HTML5 kitchensink example is not displayed in VPE visual part
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17807?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-17807 at 7/21/14 10:10 AM:
--------------------------------------------------------------------------
[~vpakan] I play with editor and looks like I found the reason. If visual editor is small enough - I have the empty screen, but only for 2013 kickstart project(with display:none). Could you please enlarge editor you have in !vpepreviewblank.png|thumbnail!(hide palette block for example)?
was (Author: kmarmaliykov):
[~vpakan] I play with editor and looks like I found the reason. If visual editor is small enough - I have the empty screen, but only for 2013 kickstart project(with display:none). Could you please enlarge editor you have in !vpepreviewblank.png|thumbnail!?
> index.html of HTML5 kitchensink example is not displayed in VPE visual part
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17807
> URL: https://issues.jboss.org/browse/JBIDE-17807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3-v20140706-0939-B172
> Linux
> SWT_GTK3=0
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: snapshot11.png, snapshot12.png, snapshot6.png, snapshot7.png, snapshot9.png, vpepreviewblank.png
>
>
> 1. Import HTML5 kitchensink project from JBoss Central
> 2. Open index.html in VPE
> ERROR: Visual part of VPE is blank
> HTML Preview is showing page properly.
> 3. Run JBT with arguments -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false
> ASSERT: Page is displayed correctly in Visual part of VPE
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17807) index.html of HTML5 kitchensink example is not displayed in VPE visual part
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17807?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-17807:
------------------------------------------------
[~vpakan] I play with editor and looks like I found the reason. If visual editor is small enough - I have the empty screen, but only for 2013 kickstart project(with display:none). Could you please enlarge editor you have in !vpepreviewblank.png|thumbnail!?
> index.html of HTML5 kitchensink example is not displayed in VPE visual part
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17807
> URL: https://issues.jboss.org/browse/JBIDE-17807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3-v20140706-0939-B172
> Linux
> SWT_GTK3=0
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: snapshot11.png, snapshot12.png, snapshot6.png, snapshot7.png, snapshot9.png, vpepreviewblank.png
>
>
> 1. Import HTML5 kitchensink project from JBoss Central
> 2. Open index.html in VPE
> ERROR: Visual part of VPE is blank
> HTML Preview is showing page properly.
> 3. Run JBT with arguments -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false
> ASSERT: Page is displayed correctly in Visual part of VPE
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17939) Move JMX Navigator location to bottom left
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17939?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17939:
-------------------------------------
It seems a view's default location can only be declared in the context of a perspective. So I'd need to know which perspectives we want the jmx view to move to the bottom left for.
> Move JMX Navigator location to bottom left
> ------------------------------------------
>
> Key: JBIDE-17939
> URL: https://issues.jboss.org/browse/JBIDE-17939
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jmx, server
> Affects Versions: 4.2.0.Beta3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
>
> I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view.
> It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once.
> Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work.
> We need it to work for both scenarios:
> 1. Server -> Shown in JMX Navigator
> 2. Open the JMX Navigator using Window -> Show view
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17878) Wrong alignment of elements when accepting $0 T&C
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17878?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17878:
-------------------------------------
Currently, all 3 widgets are set to have their bottom sides attached to a point 5 pixels above the bottom of the parent composite. It looks 'off' because a button is larger than a combo, which is larger than a label.
I have adjusted the code so that the button has its bottom attached 3 pixels from the bottom, and the combo 4 pixels from the bottom.
> Wrong alignment of elements when accepting $0 T&C
> -------------------------------------------------
>
> Key: JBIDE-17878
> URL: https://issues.jboss.org/browse/JBIDE-17878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3a B178
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.0.CR1
>
> Attachments: tc-misalignment.png
>
>
> When accepting the $0 T&C, the line at the bottom where you select country and accept is slightly misaligned.
> There are three elements - the caption on the left, then the drop-down menu which is slightly higher, and then the Accept Now button which is even higher.
> !tc-misalignment.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months