[JBoss JIRA] (JBDS-2923) Verify whether JBDS really needs PDE
by Mickael Istria (JIRA)
Mickael Istria created JBDS-2923:
------------------------------------
Summary: Verify whether JBDS really needs PDE
Key: JBDS-2923
URL: https://issues.jboss.org/browse/JBDS-2923
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build
Reporter: Mickael Istria
Fix For: 8.0.0.Beta1
It looks like by default, JBDS embeds PDE and its UI contributions, which are totally off-topic.
We should consider removing PDE. For this we need to check what depends on it first.
--
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, 2 months
[JBoss JIRA] (JBIDE-16625) Long left panel covers footer
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16625?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-16625:
-------------------------------
Attachment: website.png
website-fixed.png
> Long left panel covers footer
> -----------------------------
>
> Key: JBIDE-16625
> URL: https://issues.jboss.org/browse/JBIDE-16625
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Environment: Chrome on Linux (Fedora 18, 64b)
> Reporter: Radim Hopp
> Fix For: 4.2.0.Alpha2
>
> 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, 2 months
[JBoss JIRA] (JBIDE-16625) Long left panel covers footer
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-16625:
----------------------------------
Summary: Long left panel covers footer
Key: JBIDE-16625
URL: https://issues.jboss.org/browse/JBIDE-16625
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: website
Environment: Chrome on Linux (Fedora 18, 64b)
Reporter: Radim Hopp
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, 2 months
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-12355 at 2/20/14 1:06 AM:
----------------------------------------------------------------
It looks pretty nice. I have just few suggestions:
1) While I am viewing some specific feature, left navigate bar offer to jump to another feature. I think that order of features in left menu could be in alphabetic order. I understand, that it covers order from features site http://tools-stg.jboss.org/features/ but I think that alphabetic order is more user friendly.
2) Headings are cut off (tested in Firefox 22.0). See this image: !http://oi59.tinypic.com/2weau1h.jpg!
I would like to see something like this instead of that first one image (it it is possible): !http://oi61.tinypic.com/nq32j6.jpg!
was (Author: mlabuda):
It looks pretty nice. I have just few suggestions:
1) While I am viewing some specific feature, left navigate bar offer to jump to another feature. I think that order of features in left menu could be in alphabetic order. I understand, that it covers order from features site http://tools-stg.jboss.org/features/ but I think that alphabetic order is more user friendly.
2) Headings are cut (Firefox 22.0). See this image: !http://oi59.tinypic.com/2weau1h.jpg!
I would like to see something like this instead of that first one image (it it is possible): !http://oi61.tinypic.com/nq32j6.jpg!
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha2
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://tools-stg.jboss.org/ <-- current staged version
--
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, 2 months
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-12355:
---------------------------------------
It looks pretty nice. I have just few suggestions:
1) While I am viewing some specific feature, left navigate bar offer to jump to another feature. I think that order of features in left menu could be in alphabetic order. I understand, that it covers order from features site http://tools-stg.jboss.org/features/ but I think that alphabetic order is more user friendly.
2) Headings are cut (Firefox 22.0). See this image: !http://oi59.tinypic.com/2weau1h.jpg!
I would like to see something like this instead of that first one image (it it is possible): !http://oi61.tinypic.com/nq32j6.jpg!
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha2
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://tools-stg.jboss.org/ <-- current staged version
--
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, 2 months
[JBoss JIRA] (JBIDE-15837) Improve the CordovaJS library provider
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15837?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15837:
--------------------------------------
1. Correct empty cordova is not very useful.
2. Sounds right. I actually see them as globals which is definitely incorrect
3. Actually I have not event looked at the outline so consider the current behaviour as a side effect.
4. Yes, cordova.js and friends ( plugin files) but the module definition use on all of them are same.
5. Not a priority but if we can that would be awesome
6. Not a priority.
I agree that this solution can work because it is not trying to achieve a general solution to JSDT problems and just concentrating on Cordova. I think it is enough if the infer engine only deals with the Cordova JS library ( cordova.js and plugin js files) since this is a library all other user files will automatically get the code assist so that we do not need to track the references to cordova.js
> Improve the CordovaJS library provider
> --------------------------------------
>
> Key: JBIDE-15837
> URL: https://issues.jboss.org/browse/JBIDE-15837
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Denis Golovin
>
> The default inference engine fails to infer cordova types properly therefore most of them are not available for code assist.
> JS library provider is not scanning for changes to runtime or the added/removed plugins. It should adjust to those changes.
--
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, 2 months