[JBoss JIRA] (JBDS-3100) JBDS 8 splash screen should be improved
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-3100?page=com.atlassian.jira.plugin.... ]
Marián Labuda updated JBDS-3100:
--------------------------------
Priority: Minor (was: Major)
> JBDS 8 splash screen should be improved
> ---------------------------------------
>
> Key: JBDS-3100
> URL: https://issues.jboss.org/browse/JBDS-3100
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 8.0.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
>
> There was a usability testing yesterday focused on OpenShift plugin. One note talked about splash screen:
> {quote}
> The 8 for JBDS spash screen looks a lot like Oracle 8 when that came out - big red 8. Probably need to do something different for the branding.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3100) JBDS 8 splash screen should be improved
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-3100?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-3100:
-------------------------------------
[~james.cobb] [~maxandersen] please take a look.
> JBDS 8 splash screen should be improved
> ---------------------------------------
>
> Key: JBDS-3100
> URL: https://issues.jboss.org/browse/JBDS-3100
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: ui/branding
> Affects Versions: 8.0.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
>
> There was a usability testing yesterday focused on OpenShift plugin. One note talked about splash screen:
> {quote}
> The 8 for JBDS spash screen looks a lot like Oracle 8 when that came out - big red 8. Probably need to do something different for the branding.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17953) Ionic palette: New Tab wizard
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-17953:
---------------------------------------------
Summary: Ionic palette: New Tab wizard
Key: JBIDE-17953
URL: https://issues.jboss.org/browse/JBIDE-17953
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.2.0.CR1
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17872) XHTML files parsed as HTML instead as XML
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17872?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-17872:
---------------------------------------
https://bugs.eclipse.org/bugs/show_bug.cgi?id=439661
> XHTML files parsed as HTML instead as XML
> -----------------------------------------
>
> Key: JBIDE-17872
> URL: https://issues.jboss.org/browse/JBIDE-17872
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.Beta3
> Reporter: Ron Šmeral
> Assignee: Daniel Azarov
> Fix For: 4.2.x
>
>
> Files with an XHTML extension which are not HTML documents (don't have any doctype) seem to be treated by JBDS as HTML files, not as XML files, despite being valid and correctly referencing namespaces.
> Specifically, this appears to happen when the root element uses the default namespace. It doesn't happen when the namespace of the root element is named.
> * The file src/main/webapp/table.xhtml triggers a lot of HTML problems, has root element in default namespace:
> {code:xml}
> <document xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns="http://jboss.org/schema/seam/pdf">
> <image alignment="right" wrap="true" value="/jboss.jpg" />
> <font size="24"><paragraph spacingAfter="50">Table Test</paragraph></font>
> ...
> </document>
> {code}
> {noformat}
> Unknown tag (document).
> table.xhtml
> /itext-web/src/main/webapp
> line 1
> HTML Problem
> {noformat}
> * src/main/webapp/whyseam.xhtml doesn't trigger HTML problems, has root element in a named namespace:
> {code:xml}
> <p:document xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:p="http://jboss.org/schema/seam/pdf"
> title="Why Seam"
> keywords="mykeyword"
> subject="seam"
> author="Seam Team"
> creator="Seam PDF example app">
> <f:facet name="header">
> <p:font size="12">
> <p:footer borderWidthTop="1" borderColorTop="blue" borderWidthBottom="0" alignment="center">Why Seam? [<p:pageNumber />]</p:footer>
> </p:font>
> </f:facet>
> ...
> </p:document>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17936) Remote deploy only server has wrong temp dir and unreadable entries in server editor
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17936?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17936:
-------------------------------------
Ah ok, I see it now.
> Remote deploy only server has wrong temp dir and unreadable entries in server editor
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17936
> URL: https://issues.jboss.org/browse/JBIDE-17936
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3b B193
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
> Attachments: deploy-only-crop.png, deploy-only-full.png, JBIDE-17936.png
>
>
> This is a follow up of JBIDE-17867. That one is now fixed. I believe this is actually a regression of that one:
> When you create a remote deploy only server and set up a deploy and temp dir and then open the server editor, you will notice two problems:
> 1. In the Server behavior section, the UI for the deploy and temp directories is unreadable unless your window is very big.
> !deploy-only-crop.png!
> See also the full JBDS window screenshot - it shows that it's not really that small. And I rarely have bigger window and never saw anything like this before.
> 2. In the Deployment page, you can see that the deploy and temp dirs are the same - both use the deploy dir. I set up two distinct dirs there.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months