[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2801:
---------------------------------------
[~mmalina], I'll wait on your confirmation before adding anything to docs.
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {code}
--
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, 4 months
[JBoss JIRA] (JBIDE-16142) BrowserSim: enable use of a custom skin
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16142?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-16142:
-----------------------------------------
Thanks for the response - seems fair enough.
> BrowserSim: enable use of a custom skin
> ---------------------------------------
>
> Key: JBIDE-16142
> URL: https://issues.jboss.org/browse/JBIDE-16142
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Ilya Buziuk
>
> Open BrowserSim simulated device. Right-click device and click Preferences. For devices, click Add. In last field of Add Device wizard user selects a skin from a predefined list.
> User should be able to select to upload a custom skin. For example they might have their own skin for a pink iPhone 5c or some other shiny new phone.
> I guess the issue in including this feature might be activating functionality for buttons on the front of the skin? Perhaps that's why it hasn't been done?
--
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, 4 months
[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ]
Vlado Pakan resolved JBDS-2709.
-------------------------------
Resolution: Done
> Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
> ----------------------------------------------------------
>
> Key: JBDS-2709
> URL: https://issues.jboss.org/browse/JBDS-2709
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Vlado Pakan
> Fix For: 7.1.0.GA
>
>
> As reported here:
> https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=...
> {quote}
> Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN.
> http://subclipse.tigris.org/update_1.10.x
> Local repository compatibility between these tools and JBDS is very nice to have.
> Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question.
> {quote}
> http://www.svnkit.com/download.php
> Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer 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, 4 months
[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ]
Vlado Pakan commented on JBDS-2709:
-----------------------------------
Installation from http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... to JBDS7.1.0.CR1 CR1-v20131124-0717-B560 works fine.
No issues found while testing functionality.
> Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
> ----------------------------------------------------------
>
> Key: JBDS-2709
> URL: https://issues.jboss.org/browse/JBDS-2709
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Vlado Pakan
> Fix For: 7.1.0.GA
>
>
> As reported here:
> https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=...
> {quote}
> Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN.
> http://subclipse.tigris.org/update_1.10.x
> Local repository compatibility between these tools and JBDS is very nice to have.
> Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question.
> {quote}
> http://www.svnkit.com/download.php
> Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer 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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-16135:
-----------------------------------------
Content Assist Additional Infos and Tooltips (Hovers) were made to be like in Java Content Assist (Support links, Back/Forward/Open actions, icons and so on)
The newlook works equally in JST editors and in Java Editor (for EL in Java Strings).
The following JUnit Tests were updated (in another PR) for the changes made to CA Add. Info's and Tooltip's (Hover's) content:
org.jboss.tools.jsf.jsp.ca.test.CAForELJavaAndJSTCompareTest
org.jboss.tools.jsf.jsp.ca.test.CAJsfAddInfoInELMessagesTest
org.jboss.tools.jsf.jsp.hover.ELTooltipTest
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: el-ca-add-info-javaeditor.png, hover-javaeditor.png, hover-xhtmleditor.png, html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> 3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
> !el-ca-add-info-javaeditor.png|thumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #\{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with java element links to length() and CharSequence:
> !javadoc.png|thumbnail!
> EL Content Assist in Java Strings:
> 7. Use the project created at steps 1-2.
> 8. Open User.java.
> 9. Reveal String getName() method and add the following line before the return statement:
> {code}String x = "#{user.}";{code}
> 10. Set the text cursor after 'user.' and press Ctrl-Space
> 11. Select 'name'
> 12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
> !el-ca-add-info-javaeditor.png|thumbnail!
> Tooltips in Java Editor:
> 13. Apply the 'name' proposal.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-javaeditor.png|thumbnail!
> Tooltips in JBoss Editors:
> 16. Open inputname.xhtm
> 17. Reveal '#\{user.name\}' EL in editor.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-xhtmleditor.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2709:
----------------------------------
Good catch, [~vpakan] !
I've posted an updated site, and moved the incorrect site to another URL for now (will delete it later):
http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... (good)
http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... (bad)
These three IUs are different:
{code}
- features/org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar
- plugins/org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar
- plugins/org.tmatesoft.sqljet_1.1.8.SNAPSHOT_r1300_v20130826_2110.jar
+ features/org.tmatesoft.svnkit_1.8.0.r10086_v20131126_1344.jar
+ plugins/org.tmatesoft.svnkit_1.8.0.r10086_v20131126_1344.jar
+ plugins/org.tmatesoft.sqljet_1.1.9.r1308_v20131126_1322.jar
{code}
> Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
> ----------------------------------------------------------
>
> Key: JBDS-2709
> URL: https://issues.jboss.org/browse/JBDS-2709
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Vlado Pakan
> Fix For: 7.1.0.GA
>
>
> As reported here:
> https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=...
> {quote}
> Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN.
> http://subclipse.tigris.org/update_1.10.x
> Local repository compatibility between these tools and JBDS is very nice to have.
> Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question.
> {quote}
> http://www.svnkit.com/download.php
> Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer 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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-16135:
------------------------------------
Description:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
!el-ca-add-info-javaeditor.png|thumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #\{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with java element links to length() and CharSequence:
!javadoc.png|thumbnail!
EL Content Assist in Java Strings:
7. Use the project created at steps 1-2.
8. Open User.java.
9. Reveal String getName() method and add the following line before the return statement:
{code}String x = "#{user.}";{code}
10. Set the text cursor after 'user.' and press Ctrl-Space
11. Select 'name'
12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
!el-ca-add-info-javaeditor.png|thumbnail!
Tooltips in Java Editor:
13. Apply the 'name' proposal.
14. Point the mouse cursor over 'name' in EL and wait for a second.
15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
!hover-javaeditor.png|thumbnail!
Tooltips in JBoss Editors:
16. Open inputname.xhtm
17. Reveal '#\{user.name\}' EL in editor.
14. Point the mouse cursor over 'name' in EL and wait for a second.
15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
!hover-xhtmleditor.png|thumbnail!
was:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
!el-ca-add-info-javaeditor.png|thumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with java element links to length() and CharSequence:
!javadoc.png|thumbnail!
EL Content Assist in Java Strings:
7. Use the project created at steps 1-2.
8. Open User.java.
9. Reveal String getName() method and add the following line before the return statement:
{code}String x = "#{user.}";{code}
10. Set the text cursor after 'user.' and press Ctrl-Space
11. Select 'name'
12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
!el-ca-add-info-javaeditor.png|thumbnail!
Tooltips in Java Editor:
13. Apply the 'name' proposal.
14. Point the mouse cursor over 'name' in EL and wait for a second.
15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
!hover-javaeditor.png|thumbnail!
Tooltips in JBoss Editors:
16. Open inputname.xhtm
17. Reveal '#{user.name}' EL in editor.
14. Point the mouse cursor over 'name' in EL and wait for a second.
15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
!hover-xhtmleditor.png|thumbnail!
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: el-ca-add-info-javaeditor.png, hover-javaeditor.png, hover-xhtmleditor.png, html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> 3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
> !el-ca-add-info-javaeditor.png|thumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #\{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with java element links to length() and CharSequence:
> !javadoc.png|thumbnail!
> EL Content Assist in Java Strings:
> 7. Use the project created at steps 1-2.
> 8. Open User.java.
> 9. Reveal String getName() method and add the following line before the return statement:
> {code}String x = "#{user.}";{code}
> 10. Set the text cursor after 'user.' and press Ctrl-Space
> 11. Select 'name'
> 12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
> !el-ca-add-info-javaeditor.png|thumbnail!
> Tooltips in Java Editor:
> 13. Apply the 'name' proposal.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-javaeditor.png|thumbnail!
> Tooltips in JBoss Editors:
> 16. Open inputname.xhtm
> 17. Reveal '#\{user.name\}' EL in editor.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-xhtmleditor.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-16135:
------------------------------------
Description:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
!el-ca-add-info-javaeditor.png|thumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with java element links to length() and CharSequence:
!javadoc.png|thumbnail!
EL Content Assist in Java Strings:
7. Use the project created at steps 1-2.
8. Open User.java.
9. Reveal String getName() method and add the following line before the return statement:
{code}String x = "#{user.}";{code}
10. Set the text cursor after 'user.' and press Ctrl-Space
11. Select 'name'
12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
!el-ca-add-info-javaeditor.png|thumbnail!
Tooltips in Java Editor:
13. Apply the 'name' proposal.
14. Point the mouse cursor over 'name' in EL and wait for a second.
15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
!hover-javaeditor.png|thumbnail!
Tooltips in JBoss Editors:
16. Open inputname.xhtm
17. Reveal '#{user.name}' EL in editor.
14. Point the mouse cursor over 'name' in EL and wait for a second.
15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
!hover-xhtmleditor.png|thumbnail!
was:
EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
There are two kinds of links which we should support:
1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
!html.png|thumbnail!
*Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
!javadoc.png|thumbnail!
3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
!el-ca-add-info-javaeditor.png|thumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
*Steps to test:*
1. Make sure JDK sources are available in Eclipse
2. Create a JSF 2 KickStart project.
3. Open greeting.xhtml
4. Type #{user.name.l and press Ctrl+Space
5. Select length
6. There should be a description dialog with javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: el-ca-add-info-javaeditor.png, hover-javaeditor.png, hover-xhtmleditor.png, html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> 3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
> !el-ca-add-info-javaeditor.png|thumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with java element links to length() and CharSequence:
> !javadoc.png|thumbnail!
> EL Content Assist in Java Strings:
> 7. Use the project created at steps 1-2.
> 8. Open User.java.
> 9. Reveal String getName() method and add the following line before the return statement:
> {code}String x = "#{user.}";{code}
> 10. Set the text cursor after 'user.' and press Ctrl-Space
> 11. Select 'name'
> 12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
> !el-ca-add-info-javaeditor.png|thumbnail!
> Tooltips in Java Editor:
> 13. Apply the 'name' proposal.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-javaeditor.png|thumbnail!
> Tooltips in JBoss Editors:
> 16. Open inputname.xhtm
> 17. Reveal '#{user.name}' EL in editor.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-xhtmleditor.png|thumbnail!
--
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, 4 months