[JBoss JIRA] (JBIDE-13814) centralize all jboss tools build doc into a single place, using a single tech/markup
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13814?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13814:
----------------------------------
Description:
Currently we have doc in many places:
https://community.jboss.org/en/tools/dev?view=documents
https://community.jboss.org/wiki/JBossToolsFAQ
https://github.com/jbosstools/jbosstools-target-platforms/wiki
https://github.com/jbosstools/jbosstools-build/wiki
http://www.jboss.org/tools/docs/
http://www.jboss.org/tools/docs/faq
http://www.jboss.org/tools/docs/testing.html
http://docs.jboss.org/tools/
http://docs.jboss.org/tools/movies/
https://docs.jboss.org/author/display/JBIDE/Home
We should have doc in 1 place. Need to clean up, update, centralize, etc.
was:
Currently we have doc in many places:
https://community.jboss.org/en/tools/dev?view=documents
https://community.jboss.org/wiki/JBossToolsFAQ
https://github.com/jbosstools/jbosstools-target-platforms/wiki
https://github.com/jbosstools/jbosstools-build/wiki
http://www.jboss.org/tools/docs/
http://www.jboss.org/tools/docs/faq
http://www.jboss.org/tools/docs/testing.html
http://docs.jboss.org/tools/
http://docs.jboss.org/tools/movies/
We should have doc in 1 place. Need to clean up, update, centralize, etc.
> centralize all jboss tools build doc into a single place, using a single tech/markup
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-13814
> URL: https://issues.jboss.org/browse/JBIDE-13814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> Currently we have doc in many places:
> https://community.jboss.org/en/tools/dev?view=documents
> https://community.jboss.org/wiki/JBossToolsFAQ
> https://github.com/jbosstools/jbosstools-target-platforms/wiki
> https://github.com/jbosstools/jbosstools-build/wiki
> http://www.jboss.org/tools/docs/
> http://www.jboss.org/tools/docs/faq
> http://www.jboss.org/tools/docs/testing.html
> http://docs.jboss.org/tools/
> http://docs.jboss.org/tools/movies/
> https://docs.jboss.org/author/display/JBIDE/Home
> We should have doc in 1 place. Need to clean up, update, centralize, etc.
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13819) include latest openshift-java-client in JBoss Tools
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13819:
----------------------------------------
Summary: include latest openshift-java-client in JBoss Tools
Key: JBIDE-13819
URL: https://issues.jboss.org/browse/JBIDE-13819
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Alpha2
There were many changes in the openshift-java-client and we have to switch to the latest version (see linked issues)
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration updated JBIDE-13818:
--------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=923369
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {code}
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13818:
-------------------------------------
Bugzilla Update: (was: Perform)
> openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
> -------------------------------------------------------------------------
>
> Key: JBIDE-13818
> URL: https://issues.jboss.org/browse/JBIDE-13818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
> In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
> https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
> {code}
> Fehlermeldung
> Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> Stacktrace
> com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
> Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
> at com.openshift.internal.client.RestService.request(RestService.java:106)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:76)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
> at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
> at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
> at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:24)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
> at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
> at com.openshift.internal.client.RestService.request(RestService.java:144)
> at com.openshift.internal.client.RestService.request(RestService.java:98)
> ... 69 more
> Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
> ... 73 more
> Standard Ausgabe (STDOUT)
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> 2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
> {code}
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13818) openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13818:
----------------------------------------
Summary: openshift-java-client: cannot restart stopped application (WATCHER ISSUE)
Key: JBIDE-13818
URL: https://issues.jboss.org/browse/JBIDE-13818
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Alpha2
This is a watcher issue that helps us tracking the progress of https://bugzilla.redhat.com/show_bug.cgi?id=923369
In the openshift-java-client integration tests, restarting a stopped application is failing since a few hours (very latest OpenShift origin code):
https://ci.dev.openshift.redhat.com/jenkins/job/openshift-java-client-dev...
{code}
Fehlermeldung
Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: " Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
Stacktrace
com.openshift.client.OpenShiftEndpointException: Could not request https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...: Operation failed.Reason given: "
Reference ID: 877bbfd174ddd2b8fec93e4fb560b17a"
at com.openshift.internal.client.RestService.request(RestService.java:106)
at com.openshift.internal.client.RestService.request(RestService.java:91)
at com.openshift.internal.client.RestService.request(RestService.java:76)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:124)
at com.openshift.internal.client.ApplicationResource$StopApplicationRequest.execute(ApplicationResource.java:739)
at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:245)
at com.openshift.internal.client.ApplicationResource.stop(ApplicationResource.java:238)
at com.openshift.internal.client.ApplicationResourceIntegrationTest.shouldRestartStoppedApplication(ApplicationResourceIntegrationTest.java:237)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:24)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:74)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:194)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:135)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"errors":{},"messages":[{"exit_code":-1,"field":null,"severity":"error","text":"\nReference ID: 877bbfd174ddd2b8fec93e4fb560b17a"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.0"}
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:193)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:165)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:135)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:131)
at com.openshift.internal.client.RestService.request(RestService.java:144)
at com.openshift.internal.client.RestService.request(RestService.java:98)
... 69 more
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1403)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:163)
... 73 more
Standard Ausgabe (STDOUT)
2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/api
2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/user
2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains
2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting GET on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
2013-03-19 11:53:33|INFO |[main]| com.openshift.internal.client.RestService. request | Requesting POST on https://ec2-23-22-202-226.compute-1.amazonaws.com/broker/rest/domains/136...
{code}
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13778) Descriptions for jQuery Widget Palette elements
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13778?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13778:
----------------------------------
Description:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
2. Page
The *page* is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the *AJAX* navigation system will load additional pages on demand into the *DOM* as users navigate around. Alternatively, a *HTML* document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any *page* can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
4. Popup
To create a *popup*, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
5. Grid
*Grids* are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
Flexible by design, *panels* can be used for navigation, forms, inspectors and more.
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
The *reflow table* mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
*Collapsibles* are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Collapsible sets* start with the exact same markup as individual *collapsibles*. By adding a parent wrapper with a *data-role="collapsible-set"* attribute around a number of *collapsibles*, the framework will style these to looks like a visually grouped widget and make it behave like an accordion so only one section can be open at a time.
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Radio buttons* are used to provide a list of options where only a single option can be selected.
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Checkboxes* are used to provide a list of options where more than one can be selected.
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
was:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
2. Page
The *page* is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the *AJAX* navigation system will load additional pages on demand into the *DOM* as users navigate around. Alternatively, a *HTML* document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any *page* can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
4. Popup
To create a *popup*, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
5. Grid
*Grids* are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
Flexible by design, *panels* can be used for navigation, forms, inspectors and more.
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
The *reflow table* mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
*Collapsibles* are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Radio buttons* are used to provide a list of options where only a single option can be selected.
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Checkboxes* are used to provide a list of options where more than one can be selected.
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
> Descriptions for jQuery Widget Palette elements
> -----------------------------------------------
>
> Key: JBIDE-13778
> URL: https://issues.jboss.org/browse/JBIDE-13778
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
>
> We need to have palette elements descriptions and we need to show them in tooltips.
> 1. JS/CSS
> Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
> *Syntax:*
> {code}
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
> </head>
> {code}
> 2. Page
> The *page* is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the *AJAX* navigation system will load additional pages on demand into the *DOM* as users navigate around. Alternatively, a *HTML* document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
> *Syntax:*
> {code}
> <div data-role="page" id="page-1">
> <div data-role="header">
> <h1>Page Title</h1>
> </div>
> <div data-role="content">
> <p>Page content goes here.</p>
> </div>
> <div data-role="footer">
> <h4>Page Footer</h4>
> </div>
> {code}
> 3. Dialog
> Any *page* can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
> *Syntax:*
> {code}
> <div data-role="dialog" id="dialog-1">
> <div data-role="header">
> <h1>Dialog</h1>
> </div>
> <div data-role="content">
> <h6>Dialog content.</h6>
> <a href="#dialog-1" data-role="button" data-rel="back">OK</a>
> </div>
> </div>
> {code}
> 4. Popup
> To create a *popup*, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
> *Syntax:*
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a>
> <div data-role="popup" id="popupBasic">
> <p>This is a completely basic popup, no options set.<p>
> </div>
> {code}
> 5. Grid
> *Grids* are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
> *Syntax:*
> {code}
> <div class="ui-grid-b">
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> </div>
> {code}
> 6. Field Container
> To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> </div>
> {code}
> 7. Panel
> Flexible by design, *panels* can be used for navigation, forms, inspectors and more.
> *Syntax:*
> {code}
> <div data-role="panel" id="mypanel">
> <!-- panel content goes here -->
>
> </div><!-- /panel -->
> {code}
> 8. Table
> The *reflow table* mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
> *Syntax:*
> {code}
> <table data-role="table" id="my-table" data-mode="reflow">
> <thead>
> <tr>
> <th>Header 1</th>
> <th>Header 2</th>
> </tr>
> </thead>
> <tbody>
> <tr>
> <th>1</th>
> <td>Item 1</td>
> <td>Item 2</td>
> </tr>
> </tbody>
> </table>
> {code}
> 9. Collapsible
> *Collapsibles* are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
> *Syntax:*
> {code}
> <div data-role="collapsible">
> <h3>I'm a header</h3>
> <p>I'm the collapsible content.</p>
>
> </div>
> {code}
> 10. Collapsible Set
> *Collapsible sets* start with the exact same markup as individual *collapsibles*. By adding a parent wrapper with a *data-role="collapsible-set"* attribute around a number of *collapsibles*, the framework will style these to looks like a visually grouped widget and make it behave like an accordion so only one section can be open at a time.
> *Syntax:*
> {code}
> <div data-role="collapsible-set">
>
> </div>
> {code}
> 11. Header Bar
> The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
> *Syntax:*
> {code}
> <div data-role="header">
> <a href="#" data-icon="delete">Cancel</a>
> <h1>Edit Contact</h1>
> <a href="#" data-icon="check">Save</a>
> </div>
> {code}
> 12. Footer Bar
> The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
> *Syntax:*
> {code}
> <div data-role="footer" class="ui-bar">
> <a href="#" data-icon="plus">Add</a>
> <a href="#" data-icon="arrow-u">Up</a>
> <a href="#" data-icon="arrow-d">Down</a>
> </div>
> {code}
> 13. Navbar
> *jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
> *Syntax:*
> {code}
> <div data-role="navbar">
> <ul>
> <li><a href="#">A</a></li>
> <li><a href="#">B</a></li>
> <li><a href="#">C</a></li>
> </ul>
> </div>
> {code}
> 14. Select
> The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
> *Syntax:*
> {code}
> <label for="select-choice-0" class="select">Shipping method:</label>
> <select name="select-choice-0" id="select-choice-0">
> <option value="standard">Standard: 7 day</option>
> <option value="rush">Rush: 3 days</option>
> <option value="express">Express: next day</option>
> <option value="overnight">Overnight</option>
> </select>
> {code}
> 15. Listview
> A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
> *Syntax:*
> {code}
> <ul data-role="listview">
> <li><a href="item1.html">Item 1</a></li>
> <li><a href="item2.html">Item 2</a></li>
> </ul>
> {code}
> 16. Button
> *Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
> *Syntax:*
> {code}
> <a href="" data-role="button">Link button</a>
> {code}
> 17. Buttons
> *Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
> *Syntax:*
> {code}
> <div data-role="controlgroup">
> <a href="index.html" data-role="button">Yes</a>
> <a href="index.html" data-role="button">No</a>
> <a href="index.html" data-role="button">Maybe</a>
> </div>
> {code}
> 18. Link
> *jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
> *Syntax:*
> {code}
> <a href="">Link</a>
> {code}
> 19. Toggle
> *Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="flip-1">Switch:</label>
> <select name="flip-1" id="flip-1" data-role="slider">
> <option value="off">Off</option>
> <option value="on">On</option>
> </select>
> </div>
> {code}
> 20. Radio
> *Radio buttons* are used to provide a list of options where only a single option can be selected.
> *Syntax:*
> {code}
> <fieldset data-role="controlgroup">
> <legend>Choose a pet:</legend>
> <input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
> <label for="radio-choice-1">Cat</label>
> <input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
> <label for="radio-choice-2">Dog</label>
> <input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
> <label for="radio-choice-3">Hamster</label>
> </fieldset>
> {code}
> 21. Checkbox
> *Checkboxes* are used to provide a list of options where more than one can be selected.
> *Syntax:*
> {code}
> <label><input type="checkbox" name="checkbox-1"/>I agree</label>
> {code}
> 22. Checkboxes
> To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <fieldset data-role="controlgroup">
> <legend>Choose as many snacks as you'd like:</legend>
> <input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
> <label for="checkbox-1a">Cheetos</label>
> <input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
> <label for="checkbox-2a">Doritos</label>
>
> <input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
> <label for="checkbox-3a">Fritos</label>
> </fieldset>
> </div>
> {code}
> 23. Slider
> *Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
> *Syntax:*
> {code}
> <label for="range-1">Slider:</label>
> <input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
> {code}
> 24. Text Input
> *Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="text-1">Input:</label>
> <input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
> </div>
> {code}
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13778) Descriptions for jQuery Widget Palette elements
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13778?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13778:
----------------------------------
Description:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
2. Page
The *page* is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the *AJAX* navigation system will load additional pages on demand into the *DOM* as users navigate around. Alternatively, a *HTML* document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any *page* can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
4. Popup
To create a *popup*, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
5. Grid
*Grids* are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
Flexible by design, *panels* can be used for navigation, forms, inspectors and more.
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
The *reflow table* mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
*Collapsibles* are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Radio buttons* are used to provide a list of options where only a single option can be selected.
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Checkboxes* are used to provide a list of options where more than one can be selected.
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
was:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <code><head></code>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
2. Page
The page is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the AJAX navigation system will load additional pages on demand into the DOM as users navigate around. Alternatively, a HTML document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
4. Popup
To create a popup, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
5. Grid
Grids are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
Flexible by design, panels can be used for navigation, forms, inspectors and more.
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
The reflow table mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
Collapsibles are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Radio buttons* are used to provide a list of options where only a single option can be selected.
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Checkboxes* are used to provide a list of options where more than one can be selected.
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
> Descriptions for jQuery Widget Palette elements
> -----------------------------------------------
>
> Key: JBIDE-13778
> URL: https://issues.jboss.org/browse/JBIDE-13778
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
>
> We need to have palette elements descriptions and we need to show them in tooltips.
> 1. JS/CSS
> Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
> *Syntax:*
> {code}
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
> </head>
> {code}
> 2. Page
> The *page* is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the *AJAX* navigation system will load additional pages on demand into the *DOM* as users navigate around. Alternatively, a *HTML* document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
> *Syntax:*
> {code}
> <div data-role="page" id="page-1">
> <div data-role="header">
> <h1>Page Title</h1>
> </div>
> <div data-role="content">
> <p>Page content goes here.</p>
> </div>
> <div data-role="footer">
> <h4>Page Footer</h4>
> </div>
> {code}
> 3. Dialog
> Any *page* can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
> *Syntax:*
> {code}
> <div data-role="dialog" id="dialog-1">
> <div data-role="header">
> <h1>Dialog</h1>
> </div>
> <div data-role="content">
> <h6>Dialog content.</h6>
> <a href="#dialog-1" data-role="button" data-rel="back">OK</a>
> </div>
> </div>
> {code}
> 4. Popup
> To create a *popup*, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
> *Syntax:*
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a>
> <div data-role="popup" id="popupBasic">
> <p>This is a completely basic popup, no options set.<p>
> </div>
> {code}
> 5. Grid
> *Grids* are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
> *Syntax:*
> {code}
> <div class="ui-grid-b">
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> </div>
> {code}
> 6. Field Container
> To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> </div>
> {code}
> 7. Panel
> Flexible by design, *panels* can be used for navigation, forms, inspectors and more.
> *Syntax:*
> {code}
> <div data-role="panel" id="mypanel">
> <!-- panel content goes here -->
>
> </div><!-- /panel -->
> {code}
> 8. Table
> The *reflow table* mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
> *Syntax:*
> {code}
> <table data-role="table" id="my-table" data-mode="reflow">
> <thead>
> <tr>
> <th>Header 1</th>
> <th>Header 2</th>
> </tr>
> </thead>
> <tbody>
> <tr>
> <th>1</th>
> <td>Item 1</td>
> <td>Item 2</td>
> </tr>
> </tbody>
> </table>
> {code}
> 9. Collapsible
> *Collapsibles* are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
> *Syntax:*
> {code}
> <div data-role="collapsible">
> <h3>I'm a header</h3>
> <p>I'm the collapsible content.</p>
>
> </div>
> {code}
> 10. Collapsible Set
> *Syntax:*
> {code}
> <div data-role="collapsible-set">
>
> </div>
> {code}
> 11. Header Bar
> The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
> *Syntax:*
> {code}
> <div data-role="header">
> <a href="#" data-icon="delete">Cancel</a>
> <h1>Edit Contact</h1>
> <a href="#" data-icon="check">Save</a>
> </div>
> {code}
> 12. Footer Bar
> The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
> *Syntax:*
> {code}
> <div data-role="footer" class="ui-bar">
> <a href="#" data-icon="plus">Add</a>
> <a href="#" data-icon="arrow-u">Up</a>
> <a href="#" data-icon="arrow-d">Down</a>
> </div>
> {code}
> 13. Navbar
> *jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
> *Syntax:*
> {code}
> <div data-role="navbar">
> <ul>
> <li><a href="#">A</a></li>
> <li><a href="#">B</a></li>
> <li><a href="#">C</a></li>
> </ul>
> </div>
> {code}
> 14. Select
> The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
> *Syntax:*
> {code}
> <label for="select-choice-0" class="select">Shipping method:</label>
> <select name="select-choice-0" id="select-choice-0">
> <option value="standard">Standard: 7 day</option>
> <option value="rush">Rush: 3 days</option>
> <option value="express">Express: next day</option>
> <option value="overnight">Overnight</option>
> </select>
> {code}
> 15. Listview
> A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
> *Syntax:*
> {code}
> <ul data-role="listview">
> <li><a href="item1.html">Item 1</a></li>
> <li><a href="item2.html">Item 2</a></li>
> </ul>
> {code}
> 16. Button
> *Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
> *Syntax:*
> {code}
> <a href="" data-role="button">Link button</a>
> {code}
> 17. Buttons
> *Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
> *Syntax:*
> {code}
> <div data-role="controlgroup">
> <a href="index.html" data-role="button">Yes</a>
> <a href="index.html" data-role="button">No</a>
> <a href="index.html" data-role="button">Maybe</a>
> </div>
> {code}
> 18. Link
> *jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
> *Syntax:*
> {code}
> <a href="">Link</a>
> {code}
> 19. Toggle
> *Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="flip-1">Switch:</label>
> <select name="flip-1" id="flip-1" data-role="slider">
> <option value="off">Off</option>
> <option value="on">On</option>
> </select>
> </div>
> {code}
> 20. Radio
> *Radio buttons* are used to provide a list of options where only a single option can be selected.
> *Syntax:*
> {code}
> <fieldset data-role="controlgroup">
> <legend>Choose a pet:</legend>
> <input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
> <label for="radio-choice-1">Cat</label>
> <input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
> <label for="radio-choice-2">Dog</label>
> <input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
> <label for="radio-choice-3">Hamster</label>
> </fieldset>
> {code}
> 21. Checkbox
> *Checkboxes* are used to provide a list of options where more than one can be selected.
> *Syntax:*
> {code}
> <label><input type="checkbox" name="checkbox-1"/>I agree</label>
> {code}
> 22. Checkboxes
> To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <fieldset data-role="controlgroup">
> <legend>Choose as many snacks as you'd like:</legend>
> <input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
> <label for="checkbox-1a">Cheetos</label>
> <input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
> <label for="checkbox-2a">Doritos</label>
>
> <input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
> <label for="checkbox-3a">Fritos</label>
> </fieldset>
> </div>
> {code}
> 23. Slider
> *Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
> *Syntax:*
> {code}
> <label for="range-1">Slider:</label>
> <input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
> {code}
> 24. Text Input
> *Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="text-1">Input:</label>
> <input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
> </div>
> {code}
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBIDE-13778) Descriptions for jQuery Widget Palette elements
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13778?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13778:
----------------------------------
Description:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <code><head></code>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
2. Page
The page is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the AJAX navigation system will load additional pages on demand into the DOM as users navigate around. Alternatively, a HTML document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
4. Popup
To create a popup, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
5. Grid
Grids are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
Flexible by design, panels can be used for navigation, forms, inspectors and more.
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
The reflow table mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
Collapsibles are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Radio buttons* are used to provide a list of options where only a single option can be selected.
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Checkboxes* are used to provide a list of options where more than one can be selected.
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
was:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to <b>jQuery</b>, <b>jQuery Mobile</b> JS and CSS to <code><head></code>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
2. Page
The page is the primary unit of interaction in jQuery Mobile and is used to group content into logical views that can be animated in and out of view with page transitions. A HTML document may start with a single "page" and the AJAX navigation system will load additional pages on demand into the DOM as users navigate around. Alternatively, a HTML document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
4. Popup
To create a popup, add the data-role="popup" attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute data-rel="popup" to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
5. Grid
Grids are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the data-role="fieldcontain" attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
Flexible by design, panels can be used for navigation, forms, inspectors and more.
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
The reflow table mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
Collapsibles are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
The header is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
The footer is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to navbars.
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
<b>jQuery Mobile</b> has a very basic <b>navbar</b> widget that is useful for providing up to 5 buttons with optional icons in a bar.
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
The <b>select menu</b> is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
A <b>listview</b> is coded as a simple <b>unordered list (ul)</b> or <b>ordered list (ol)</b> with a <b>data-role="listview"</b> attribute and has a wide range of features.
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
Buttons are core widgets in jQuery Mobile and are used within a wide range of other plugins. The button markup is flexible and can be created from links or form buttons.
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
Controlgroups are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
jQuery Mobile is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
Flip switches are used for boolean style inputs like true/false or on/off in a compact UI element.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
Radio buttons are used to provide a list of options where only a single option can be selected.
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
Checkboxes are used to provide a list of options where more than one can be selected.
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the data-role="fieldcontain" attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
Sliders are used to enter numeric values along a continuum and can also be dual handle range sliders or flip switches.
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
Text inputs and textareas are coded with standard HTML elements, then enhanced by jQuery Mobile to make them more attractive and useable on a mobile device.
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
> Descriptions for jQuery Widget Palette elements
> -----------------------------------------------
>
> Key: JBIDE-13778
> URL: https://issues.jboss.org/browse/JBIDE-13778
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
>
> We need to have palette elements descriptions and we need to show them in tooltips.
> 1. JS/CSS
> Add references to *jQuery*, *jQuery Mobile* JS and CSS to <code><head></code>
> *Syntax:*
> {code}
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
> </head>
> {code}
> 2. Page
> The page is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the AJAX navigation system will load additional pages on demand into the DOM as users navigate around. Alternatively, a HTML document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
> *Syntax:*
> {code}
> <div data-role="page" id="page-1">
> <div data-role="header">
> <h1>Page Title</h1>
> </div>
> <div data-role="content">
> <p>Page content goes here.</p>
> </div>
> <div data-role="footer">
> <h4>Page Footer</h4>
> </div>
> {code}
> 3. Dialog
> Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
> *Syntax:*
> {code}
> <div data-role="dialog" id="dialog-1">
> <div data-role="header">
> <h1>Dialog</h1>
> </div>
> <div data-role="content">
> <h6>Dialog content.</h6>
> <a href="#dialog-1" data-role="button" data-rel="back">OK</a>
> </div>
> </div>
> {code}
> 4. Popup
> To create a popup, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
> *Syntax:*
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a>
> <div data-role="popup" id="popupBasic">
> <p>This is a completely basic popup, no options set.<p>
> </div>
> {code}
> 5. Grid
> Grids are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
> *Syntax:*
> {code}
> <div class="ui-grid-b">
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> </div>
> {code}
> 6. Field Container
> To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> </div>
> {code}
> 7. Panel
> Flexible by design, panels can be used for navigation, forms, inspectors and more.
> *Syntax:*
> {code}
> <div data-role="panel" id="mypanel">
> <!-- panel content goes here -->
>
> </div><!-- /panel -->
> {code}
> 8. Table
> The reflow table mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
> *Syntax:*
> {code}
> <table data-role="table" id="my-table" data-mode="reflow">
> <thead>
> <tr>
> <th>Header 1</th>
> <th>Header 2</th>
> </tr>
> </thead>
> <tbody>
> <tr>
> <th>1</th>
> <td>Item 1</td>
> <td>Item 2</td>
> </tr>
> </tbody>
> </table>
> {code}
> 9. Collapsible
> Collapsibles are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
> *Syntax:*
> {code}
> <div data-role="collapsible">
> <h3>I'm a header</h3>
> <p>I'm the collapsible content.</p>
>
> </div>
> {code}
> 10. Collapsible Set
> *Syntax:*
> {code}
> <div data-role="collapsible-set">
>
> </div>
> {code}
> 11. Header Bar
> The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
> *Syntax:*
> {code}
> <div data-role="header">
> <a href="#" data-icon="delete">Cancel</a>
> <h1>Edit Contact</h1>
> <a href="#" data-icon="check">Save</a>
> </div>
> {code}
> 12. Footer Bar
> The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
> *Syntax:*
> {code}
> <div data-role="footer" class="ui-bar">
> <a href="#" data-icon="plus">Add</a>
> <a href="#" data-icon="arrow-u">Up</a>
> <a href="#" data-icon="arrow-d">Down</a>
> </div>
> {code}
> 13. Navbar
> *jQuery Mobile* has a very basic *navbar* widget that is useful for providing up to 5 buttons with optional icons in a bar.
> *Syntax:*
> {code}
> <div data-role="navbar">
> <ul>
> <li><a href="#">A</a></li>
> <li><a href="#">B</a></li>
> <li><a href="#">C</a></li>
> </ul>
> </div>
> {code}
> 14. Select
> The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
> *Syntax:*
> {code}
> <label for="select-choice-0" class="select">Shipping method:</label>
> <select name="select-choice-0" id="select-choice-0">
> <option value="standard">Standard: 7 day</option>
> <option value="rush">Rush: 3 days</option>
> <option value="express">Express: next day</option>
> <option value="overnight">Overnight</option>
> </select>
> {code}
> 15. Listview
> A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
> *Syntax:*
> {code}
> <ul data-role="listview">
> <li><a href="item1.html">Item 1</a></li>
> <li><a href="item2.html">Item 2</a></li>
> </ul>
> {code}
> 16. Button
> *Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
> *Syntax:*
> {code}
> <a href="" data-role="button">Link button</a>
> {code}
> 17. Buttons
> *Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
> *Syntax:*
> {code}
> <div data-role="controlgroup">
> <a href="index.html" data-role="button">Yes</a>
> <a href="index.html" data-role="button">No</a>
> <a href="index.html" data-role="button">Maybe</a>
> </div>
> {code}
> 18. Link
> *jQuery Mobile* is designed to work with standard page link conventions and layers the AJAX navigation on top for maximum compatibility.
> *Syntax:*
> {code}
> <a href="">Link</a>
> {code}
> 19. Toggle
> *Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="flip-1">Switch:</label>
> <select name="flip-1" id="flip-1" data-role="slider">
> <option value="off">Off</option>
> <option value="on">On</option>
> </select>
> </div>
> {code}
> 20. Radio
> *Radio buttons* are used to provide a list of options where only a single option can be selected.
> *Syntax:*
> {code}
> <fieldset data-role="controlgroup">
> <legend>Choose a pet:</legend>
> <input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
> <label for="radio-choice-1">Cat</label>
> <input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
> <label for="radio-choice-2">Dog</label>
> <input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
> <label for="radio-choice-3">Hamster</label>
> </fieldset>
> {code}
> 21. Checkbox
> *Checkboxes* are used to provide a list of options where more than one can be selected.
> *Syntax:*
> {code}
> <label><input type="checkbox" name="checkbox-1"/>I agree</label>
> {code}
> 22. Checkboxes
> To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element. This framework aligns the input and associated label side-by-side, and breaks to stacked block-level elements below ~480px. The framework will also add a thin bottom border to act as a field separator.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <fieldset data-role="controlgroup">
> <legend>Choose as many snacks as you'd like:</legend>
> <input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
> <label for="checkbox-1a">Cheetos</label>
> <input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
> <label for="checkbox-2a">Doritos</label>
>
> <input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
> <label for="checkbox-3a">Fritos</label>
> </fieldset>
> </div>
> {code}
> 23. Slider
> *Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
> *Syntax:*
> {code}
> <label for="range-1">Slider:</label>
> <input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
> {code}
> 24. Text Input
> *Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="text-1">Input:</label>
> <input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
> </div>
> {code}
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBDS-2494) Cannot install GWT Designer - missing org.eclipse.wb.core.xml
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2494?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2494.
-------------------------------
Already verified - closing.
> Cannot install GWT Designer - missing org.eclipse.wb.core.xml
> -------------------------------------------------------------
>
> Key: JBDS-2494
> URL: https://issues.jboss.org/browse/JBDS-2494
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyDependencies, Build
> Affects Versions: 7.0.0.Alpha1
> Environment: JBDS 7.0.0.Alpha1c
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 7.0.0.Alpha1
>
>
> I am unable to install GWT plugins including GWT Designer.
> Because of JBDS-2469 I am trying to use normal update sites and not JBoss Central.
> I have these update sites added:
> http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/4...
> http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.c...
> https://devstudio.jboss.com/updates/7.0-staging/extras/
> Then I go to Help -> Install New Software... and select the extras update site.
> I uncheck "Group items by category" and manually select all Google/GWT and Window Builder (which is needed for Google Designer).
> Then I am given this error:
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919)
> Missing requirement: WindowBuilder Core for XML GUI's 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml 1.5.2.r42x201302111919) requires 'bundle org.eclipse.wb.core.java 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919)
> To: org.eclipse.wb.core.xml [1.5.2.r42x201302111919]
> {code}
> So the missing dependency is org.eclipse.wb.core.xml. Shouldn't that be on the target platform? Am I doing something wrong?
--
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
13 years
- 1
- 0
[JBoss JIRA] (JBDS-2478) JBDS 7 features point to JBDS 6 update sites
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2478?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-2478:
--------------------------------
Fix Version/s: (was: 7.0.0.Alpha1)
Removing Alpha1 from fix version so this can be properly verified in Alpha2.
> JBDS 7 features point to JBDS 6 update sites
> --------------------------------------------
>
> Key: JBDS-2478
> URL: https://issues.jboss.org/browse/JBDS-2478
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rdPartyDependencies, central
> Affects Versions: 7.0.0.Alpha1
> Environment: Version: 7.0.0.Alpha1
> Build id: Alpha1-v20130219-1732-B10
> Build date: 20130219-1732
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Labels: respin-b
> Fix For: 7.0.0.Alpha2
>
>
> Installing the Mylyn connectors results in this version being installed:
> JBoss Tools Common - Mylyn
> 3.4.0.Final-v20121206-1757-B38 org.jboss.tools.common.mylyn.feature.feature.group
> After JBDS is restarted, the user is prompted that this version is available to be installed:
> JBoss Tools Common - Mylyn
> 3.5.0.Alpha1-v20130216-0701-B10
> from http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1a.c...
--
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
13 years
- 1
- 0