[JBoss JIRA] (JBIDE-16625) Long left panel covers footer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16625?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16625:
----------------------------------------
Parent: (was: JBIDE-12355)
Issue Type: Feature Request (was: Sub-task)
> Long left panel covers footer
> -----------------------------
>
> Key: JBIDE-16625
> URL: https://issues.jboss.org/browse/JBIDE-16625
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Environment: Chrome on Linux (Fedora 18, 64b)
> Reporter: Radim Hopp
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta1
>
> Attachments: website-fixed.png, website.png
>
>
> When the left panel is longer than some value and page is scrolled to the bottom, it covers part of footer making it unable to access few links from footer without scrolling back up:
> !website.png!
> Solution could be to "stuck" left panel on bottom of the page and scroll it up (like it is doing on the top of the page) so it would look like this:
> !website-fixed.png!
> And one more little thing (i don't think it deserves its own jira): The thin line just above the footer is on top of left panel and imo should be under.
--
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, 1 month
[JBoss JIRA] (JBIDE-16657) handle the case where development = stable
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16657?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16657:
----------------------------------------
Parent: (was: JBIDE-12355)
Issue Type: Feature Request (was: Sub-task)
> handle the case where development = stable
> -------------------------------------------
>
> Key: JBIDE-16657
> URL: https://issues.jboss.org/browse/JBIDE-16657
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Fix For: 4.2.0.Beta1
>
>
> once we release Final, the development updatesite actually contains final and not the latest CR1 so there is a mismatch between website and reality ;)
> Suggestion:
> Add "marker" to latest_development in products.yml that will add an alert
> to the latest active development download that the updatesite actually has stable.
> actualcontent: 4.1.0.Final
> Would give something like:
> Info: 4.1.0.Final have been released and is what you will get when installing from the development update site.
--
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, 1 month
[JBoss JIRA] (JBIDE-16122) Download Runtime task wizard has opportunity to block UI
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16122?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-16122.
---------------------------------
I didn't really succeed to cancel the progress of downloading the list of runtimes. It was too fast. This is nothing critical, so I will assume it's fixed.
> Download Runtime task wizard has opportunity to block UI
> ---------------------------------------------------------
>
> Key: JBIDE-16122
> URL: https://issues.jboss.org/browse/JBIDE-16122
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.1.2.CR1
>
>
> Several pieces of code call various methods such as RuntimeCoreActivator.getDefault().getDownloadRuntimeArray();
> These methods do not use progress monitor, and, if the list of DownloadRuntimes has not successfully completed once before, will be a long-running task.Since they are called directly from the UI, this has the potential to block the UI with no feedback to the user and no way to cancel.
--
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, 1 month