[JBoss JIRA] (JBIDE-16019) Reorganize JST component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16019?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16019:
-----------------------------------
Description:
!dependencies.png!
My suggestions:
*1. Clean up (remove obsolete plugins):*
* jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
* jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
* jst.web.tiles/tiles.ui. Not sure about this one. Do we still need to support tiles framework?
*2. Fix dependency problem between jsp/html editor and other jsp/html editor related UI features (such as html5 property view) by merging all UI plugins into jst.web.ui plug-in:*
* jst.jsp (JSP/HTML editor, content assist, outline)
* jst.web.ui (palette, wizards, ...)
* jst.text.ext (Open Ons)
* jst.css (css editor)
was:
!dependencies.png!
My suggestions:
*1. Remove obsolete plugins:*
* jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
* jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
* jst.web.tiles/tiles.ui. Not sure about this one. Do we still need to support tiles framework?
*2. Merge all UI plugins into jst.web.ui plug-in:*
* jst.jsp (JSP/HTML editor)
* jst.web.ui (
> Reorganize JST component
> ------------------------
>
> Key: JBIDE-16019
> URL: https://issues.jboss.org/browse/JBIDE-16019
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core, jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
> Attachments: dependencies.gliffy, dependencies.png
>
>
> !dependencies.png!
> My suggestions:
> *1. Clean up (remove obsolete plugins):*
> * jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
> * jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
> * jst.web.tiles/tiles.ui. Not sure about this one. Do we still need to support tiles framework?
> *2. Fix dependency problem between jsp/html editor and other jsp/html editor related UI features (such as html5 property view) by merging all UI plugins into jst.web.ui plug-in:*
> * jst.jsp (JSP/HTML editor, content assist, outline)
> * jst.web.ui (palette, wizards, ...)
> * jst.text.ext (Open Ons)
> * jst.css (css editor)
--
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, 5 months
[JBoss JIRA] (JBIDE-16019) Reorganize JST component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16019?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16019:
-----------------------------------
Description:
!dependencies.png!
My suggestions:
*1. Remove obsolete plugins:*
* jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
* jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
* jst.web.tiles/tiles.ui. Not sure about this one. Do we still need to support tiles framework?
*2. Merge all UI plugins into jst.web.ui plug-in:*
* jst.jsp (JSP/HTML editor)
* jst.web.ui (
was:!dependencies.png!
> Reorganize JST component
> ------------------------
>
> Key: JBIDE-16019
> URL: https://issues.jboss.org/browse/JBIDE-16019
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core, jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
> Attachments: dependencies.gliffy, dependencies.png
>
>
> !dependencies.png!
> My suggestions:
> *1. Remove obsolete plugins:*
> * jst.firstrun (This plug-in used to initialize AS and Data drivers during the first run. Has moved to runtimes component)
> * jst.web.verification (Our old validation framework which we don't use anymore. All verification rules have been migrated to our common validation framework)
> * jst.web.tiles/tiles.ui. Not sure about this one. Do we still need to support tiles framework?
> *2. Merge all UI plugins into jst.web.ui plug-in:*
> * jst.jsp (JSP/HTML editor)
> * jst.web.ui (
--
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, 5 months
[JBoss JIRA] (JBIDE-15742) Make Content Assistant Additional Info window to support URLs.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15742?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15742:
----------------------------------
Labels: new_and_noteworthy (was: )
> Make Content Assistant Additional Info window to support URLs.
> --------------------------------------------------------------
>
> Key: JBIDE-15742
> URL: https://issues.jboss.org/browse/JBIDE-15742
> 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.0.Alpha1
>
> Attachments: html.png, javadoc.png
>
>
> 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!
> *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!
--
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, 5 months