[JBoss JIRA] Created: (JBIDE-8216) jsf-tags breaks wtp-capibilites
by nimo stephan (JIRA)
jsf-tags breaks wtp-capibilites
-------------------------------
Key: JBIDE-8216
URL: https://issues.jboss.org/browse/JBIDE-8216
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Environment: JSF, JbossTools
Reporter: nimo stephan
With Eclipse WTP, I can click a css-class within a html-editor to jump automatically to that css-class.
This only works, when referencing the html with the stylesheet:
<link rel="stylesheet" href="style.css" type="text/css"/>
But when using the jsf-tag:
<h:outputStylesheet name="style.css" type="text/css"/>
then the linking between html and css does no more work!
So it would be nice, if jboss-tools does resolve such an issue.
In generally, Jboss Tools should be aware of JSF-Tags and involve them nicely so that the capabilites of WTP are not cut.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8090) Missing dialog titles
by Libor Zoubek (JIRA)
Missing dialog titles
---------------------
Key: JBIDE-8090
URL: https://issues.jboss.org/browse/JBIDE-8090
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Libor Zoubek
Assignee: Andre Dietisheim
Priority: Minor
I ve found several dialogs where are missing dialog titles. It should be fixed. It is good convention to have titled dialogs and it is goot for bot tests too.
* New/Edit Connection
* Launch Instance
* Setting up filters
* Selecting EC2 key
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
by Denis Golovin (JIRA)
VPE Part should not show exceptions but readable explanation why it cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Maxim Areshkau
Fix For: 3.2.0.Beta2
Exceptions related to loading xulrunner should be handled right way. Human friendly messages would be good here for usecases we know. VPE should check for current platform and if it is not supported do not scary users with exceptions. It should try to load XL just in case path to XL injected outside through System property, but show explanation instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported platforms and possible workarounds. please read this article on JBoss Tools Community Portal". If someone is trying to inject XULRunner implementation using system property it can say, That "Visual Editor tried to load XL from provided loaction ${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months