[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23134:
-------------------------------------
[~mmalina] https://wiki.eclipse.org/Links_and_Buttons
This article seems to indicate Buttons are for primary actions or actions with significant consequences. They are more prominent, and draw the user eye more. For examples of buttons, think of Print (significant action), "Save" (significant action), "Show Details" in a progress dialog, which changes the UI significantly by expanding the dialog and adding / showing more widgets.
A simple refresh viewer, in my opinion, is very insignificant.
I would categorize a simple refresh of a view as a secondary action. It has no significant consequences, and no lasting changes. It does not change the UI by adding or removing widgets in a way that would be confusing to the user without a button. It persists nothing. It is secondary to the table viewer completely.
I also personally feel a button would look out of place.
And while i disagree with [~mickael_istria]'s link in some respects (website is different than eclipse), it also defends my point:
{quote}
Actions where users won’t affect the website are where you use a link. These are actions that take users from one page to another without changing anything on the website’s back or front-end. The user is basically a spectator browsing through content. They aren’t doing any actions that require more effort than clicking and viewing. The back-end and front-end of the website remains the same. It’s these situations when you should use a link over a button.
{quote}
You can argue that I am incorrect here... you could argue that the front end has changed. But it hasn't. The widgets are all in the same places as before. And, as the article says, "The user is basically a spectator [sic] aren't doing any actions that require more effort than clicking and viewing."
Hope this clarifies my view.
> Improve UI of Deployment tab of Runtime Editor
> ----------------------------------------------
>
> Key: JBIDE-23134
> URL: https://issues.jboss.org/browse/JBIDE-23134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
> Attachments: screenshot-1.png
>
>
> - Refresh table button is really strange
> - there are some grey background around the sections
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23161) Update bundled and website schema with wf10.1 schema
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23161?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-23161:
-----------------------------------
Fix Version/s: 4.4.2.AM1
Story Points: 5
Sprint: devex #120 September 2016
Assignee: Rob Stryker
> Update bundled and website schema with wf10.1 schema
> ----------------------------------------------------
>
> Key: JBIDE-23161
> URL: https://issues.jboss.org/browse/JBIDE-23161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> WildFly 10.1 is released, so two tasks need to be done.
> 1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
> 2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
> {code}
> # Check out repos and DL new app server
> wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
> unzip wildfly-10.1.0.Final.zip
> git clone git@github.com:robstryker/jboss.org.schema.git
> git clone git@github.com:jbosstools/jbosstools-server.git
> tmpdir=`pwd`
> echo $tmpdir
> # Build the catalog plugin
> cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
> mvn clean verify -DskipTests
> cd target/classes/
> echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
> # Copy new or modified schema into the jboss.org.schema repo
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jboss.org.schema/schema_htdocs" jbossas
> # Copy new or modified schema into the catalog schema folder
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
> # Commit the changes to jboss.org.schema repo
> cd $tmpdir/jboss.org.schema/schema_htdocs
> git checkout -b wildfly101schema
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> # TODO ACTION REQUIRED, push to your own repo and initiate pull request
> cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
> git checkout -b wildfly101schema
> # Update plugin.xml for catalog
> java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
> -Doutput.mode=generateCatalog\
> org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> #TODO ACTION REQUIRED, push to your own repo and initiate a PR
>
> # run a build to verify it works
> cd $tmpdir/jbosstools-server
> mvn clean install -DskipTests
> # Now run CatalogValidationTest manually
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23161) Update bundled and website schema with wf10.1 schema
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23161?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23161.
---------------------------------
Resolution: Done
done
> Update bundled and website schema with wf10.1 schema
> ----------------------------------------------------
>
> Key: JBIDE-23161
> URL: https://issues.jboss.org/browse/JBIDE-23161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> WildFly 10.1 is released, so two tasks need to be done.
> 1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
> 2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
> {code}
> # Check out repos and DL new app server
> wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
> unzip wildfly-10.1.0.Final.zip
> git clone git@github.com:robstryker/jboss.org.schema.git
> git clone git@github.com:jbosstools/jbosstools-server.git
> tmpdir=`pwd`
> echo $tmpdir
> # Build the catalog plugin
> cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
> mvn clean verify -DskipTests
> cd target/classes/
> echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
> # Copy new or modified schema into the jboss.org.schema repo
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jboss.org.schema/schema_htdocs" jbossas
> # Copy new or modified schema into the catalog schema folder
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
> # Commit the changes to jboss.org.schema repo
> cd $tmpdir/jboss.org.schema/schema_htdocs
> git checkout -b wildfly101schema
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> # TODO ACTION REQUIRED, push to your own repo and initiate pull request
> cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
> git checkout -b wildfly101schema
> # Update plugin.xml for catalog
> java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
> -Doutput.mode=generateCatalog\
> org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> #TODO ACTION REQUIRED, push to your own repo and initiate a PR
>
> # run a build to verify it works
> cd $tmpdir/jbosstools-server
> mvn clean install -DskipTests
> # Now run CatalogValidationTest manually
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23163) Docker settings for secure Linux to be documented
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23163:
----------------------------------
Summary: Docker settings for secure Linux to be documented
Key: JBIDE-23163
URL: https://issues.jboss.org/browse/JBIDE-23163
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: website
Affects Versions: 4.4.1.Final
Reporter: Jeff MAURY
Priority: Minor
Fix For: 4.4.2.AM2
On secure Linux (or Fedora), the Docker command to run the website may have problems with the shared volumes permissions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23160) Update m2e-wtp and m2eclipse-tycho in jbosstools and jbdevstudio target platforms (4.61.0.AM1-SNAPSHOT)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23160?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-23160:
-------------------------------------
yes yes yes, I want them all
> Update m2e-wtp and m2eclipse-tycho in jbosstools and jbdevstudio target platforms (4.61.0.AM1-SNAPSHOT)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23160
> URL: https://issues.jboss.org/browse/JBIDE-23160
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM1
>
>
> The 1.3.1 version of m2e-wtp has been mirrored as well as the 0.9.0 version of m2eclipse-tycho. Please update in jbosstools-multiple for Neon. Also - please change https -> http for the locus update site URL reference.
> {code}
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <unit id="org.eclipse.m2e.wtp.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jaxrs.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jpa.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jsf.feature.feature.group" version="1.3.1.20160831-1005"/>
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.3.1.2..."/>
> </location>
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <unit id="org.sonatype.tycho.m2e.feature.feature.group" version="0.9.0.201609061714"/>
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho..."/>
> </location>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23160) Update m2e-wtp and m2eclipse-tycho in jbosstools and jbdevstudio target platforms (4.61.0.AM1-SNAPSHOT)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23160?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23160:
------------------------------------
[~fbricon] please confirm you want this new version of m2e-wtp and m2eclipse-tycho in the TPs for JBT 4.4.2 / devstudio 10.2 (that is, the Neon.1-based target platforms).
> Update m2e-wtp and m2eclipse-tycho in jbosstools and jbdevstudio target platforms (4.61.0.AM1-SNAPSHOT)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23160
> URL: https://issues.jboss.org/browse/JBIDE-23160
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM1
>
>
> The 1.3.1 version of m2e-wtp has been mirrored as well as the 0.9.0 version of m2eclipse-tycho. Please update in jbosstools-multiple for Neon. Also - please change https -> http for the locus update site URL reference.
> {code}
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <unit id="org.eclipse.m2e.wtp.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jaxrs.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jpa.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jsf.feature.feature.group" version="1.3.1.20160831-1005"/>
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.3.1.2..."/>
> </location>
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <unit id="org.sonatype.tycho.m2e.feature.feature.group" version="0.9.0.201609061714"/>
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho..."/>
> </location>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months