[JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi... ]
Catherine Robson commented on JBIDE-16876:
------------------------------------------
I definitely agree that the fields for the selection that is not enabled should be grayed out. This makes it clear to the user what option they are selecting, and acts as a either/or decision which this screen certainly is.
> New Application wizard: page#1 needs fields disabled based on user actions
> --------------------------------------------------------------------------
>
> Key: JBIDE-16876
> URL: https://issues.jboss.org/browse/JBIDE-16876
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.0.Beta2
>
> Attachments: create-new-application.png, import-existing-application.png, out-3.ogv
>
>
> In the New OpenShift Application wizard, user has two choices 1) use existing app or 2) create new app.
> * If user clicks 'Use my existing OpenShift application', then list of cartridges should be disabled. I was able to give name of app to import and then select cartridge which was meaningless as app was imported with original cartridge (as expected) and not the new one I had selected.
> * If user clicks 'Create a new OpenShift application', the field for app name and browse button should be disabled.
> But this also raises the question for me as to why these two choices are shared on the same wizard page. I wonder if it would be cleaner to separate them.
> * So when in OpenShift Explorer view a user right-clicks an application and clicks 'Import Application' they would just see the wizard starting from the page 'Set up project for new OpenShift Application'. They've already decided they want to import so offering fields about creating a new OpenShift app isn't useful.
> * Similarly, when a user selects 'New > Application' then they don't need to be offered the information about using an existing OpenShift application. To me as a user, the action 'New > Application' makes me thing that I am creating a new OpenShift Application so having fields about using an existing OpenShift app is confusing.
--
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
[JBoss JIRA] (JBIDE-16938) Source code formatting is not working
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-16938:
-----------------------------------
Summary: Source code formatting is not working
Key: JBIDE-16938
URL: https://issues.jboss.org/browse/JBIDE-16938
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.2.0.Beta1
Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78 Linux
Reporter: Vlado Pakan
Priority: Minor
Fix For: 4.2.0.Beta2
1. Create HTML page with this content
{code}
<!DOCTYPE html>
<html ng-app="dsd">
<body>
textbody
<h1>texth1</h1>
</body>
</html>
{code}
0. Double click on "texth1"
ASSERT: Formatting buttons are enabled
1. Click within text "textbody"
ERROR: Formatting toolbar buttons are disabled
2. Click within text "texth1"
3. Click button Italic
ASSERT: "texth1" is surrounded by <i> tags
4. Repeat step 2. and click on button bold
ERROR: "texth1" is not surrounded by <b> tags. Text <b></b> is added after "texth1"
5. Double click on "texth1"
ERROR: Formatting buttons are disabled
--
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
[JBoss JIRA] (JBTIS-260) Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/JBTIS-260?page=com.atlassian.jira.plugin.... ]
Barry LaFond commented on JBTIS-260:
------------------------------------
Fix was checked into 8.3.x, 8.3.2 was rebuilt and updated my JBDS 7.1.1.GA + DV. Preview and Execute VDB now work as designed.
> Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2
> --------------------------------------------------------------------------------
>
> Key: JBTIS-260
> URL: https://issues.jboss.org/browse/JBTIS-260
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: teiid
> Environment: JBDS 7.1.1.GA, JBDSIS 7.0.1.CR2, server DV6 GA
> Reporter: Lucie Fabrikova
> Assignee: Paul Richardson
> Priority: Blocker
> Attachments: DriverValidator-1.2.11
>
>
> In teiid designer, start server latest DV6 GA and create new model project. Create some source model.
> - preview of data in table causes error with empty stack trace, development perspective is not opened
> - create and execute vdb: development perspective is opened, but vdb is not connected; trying to connect causes NPE:
> java.lang.NullPointerException
> at org.eclipse.datatools.connectivity.drivers.DriverValidator.validateJarListFiles(DriverValidator.java:161)
> at org.eclipse.datatools.connectivity.drivers.DriverValidator.isValid(DriverValidator.java:92)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getDriverDefinitionJarPaths(JDBCConnection.java:217)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getJdbcDriverJars(JDBCConnection.java:169)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.<init>(JDBCConnection.java:67)
> at org.teiid.datatools.connectivity.TeiidJDBCConnection.<init>(TeiidJDBCConnection.java:31)
> at org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:21)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:705)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38)
> at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45)
> at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114)
> at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163)
> at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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