[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2032:
--------------------------------------------
[~dgolovin] yes your PR is similar to what I thought. I would put it in foundation though and I'm wondering if there is a way to provide a more dynamic doc installation - one that link these to different docs based on what product are installed.
What happens if the docs bundle is not installed ? will there be some nontangible error ?
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2032:
--------------------------------------------
[~mmurray] and this is one of the reasons why we haven't solved this yet ;/ we would have to double maintain these.
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2635:
-------------------------------------------
[~dgolovin] are you suggesting we implement our own izpack on top of this ?
Why do we need this rcp app to solve this issue ?
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16220:
---------------------------------------------
I think you mean "map" files in eclipse.
And yes, this is why and where I think this repo would make sense but the release producing
Btw. if we had this submodule instead one could argue you dont need uniform tags across all repositories since the pointers in the submodules would define what is in jbosstools 4.1.0.GA ....but that might be taking it too far since its nice not having to git checkout for different named branches.
> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
> Key: JBIDE-16220
> URL: https://issues.jboss.org/browse/JBIDE-16220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.x
>
> Attachments: buildlog_maven311.txt
>
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
> "git submodule" started learning a new mode to integrate with the
> tip of the remote branch (as opposed to integrating with the commit
> recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, 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
12 years, 5 months
[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-2868:
----------------------------------------
We discussed this in the last syncup with the OpenShift team and it turns out that there's OS v3.0 coming up in the beginning of 2015. OS v3.0 will most likely deprecate protocol v1.2 and thus require us to support multiple protocols at this point.
> Support multiple protocols when talking to OpenShift servers
> ------------------------------------------------------------
>
> Key: JBDS-2868
> URL: https://issues.jboss.org/browse/JBDS-2868
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Andre Dietisheim
>
> The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ]
Mickael Istria commented on JBIDE-3937:
---------------------------------------
Ok. But a performance test must be "static", ie the content of the test mustn't change over time or it invalidates the time trend. So, if it's about performance test, it's necessary to have a dedicated test case or test suite that won't move with time. I don't think integration tests fit well.
I know [~vpakan] is currently working on setting up some performance tests for JBoss Tools.
> Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-3937
> URL: https://issues.jboss.org/browse/JBIDE-3937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, qa
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Why we need this?
> The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems.
> It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16347) New Tabs wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16347?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16347:
------------------------------------------
Description:
Tabs widget can be implemented as navbar
{code}
<div data-role="tabs" id="tabs">
<div data-role="navbar">
<ul>
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
</ul>
</div>
<div id="one" class="ui-body-d ui-content">
</div>
<div id="two">
</div>
</div>
{code}
or as listview
{code}
<div data-role="tabs">
<style scoped="scoped">
.tablist-left {width: 35%; display: inline-block;}
.tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
</style>
<ul data-role="listview" data-inset="true" class="tablist-left">
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
<li><a href="ajax-content.html" data-ajax="false">three</a></li>
</ul>
<div id="one" class="ui-body-d tablist-content">
</div>
<div id="two" class="ui-body-d tablist-content">
</div>
</div>
{code}
Some features are not supported by data-* attributes but can be set with script
Collapsible
{code}
<script>
$("#tabs").tabs({collapsible: true});
</script>
{code}
Initially collapsed
{code}
<script>
$("#tabs").tabs({collapsible: true, active: false});
</script>
{code}
Specifying initially active tab
{code}
<script>
$("#tabs").tabs({active: 1});
</script>
{code}
Tab disablement
{code}
<script>
$("#tabs").tabs({disabled: [2]});
</script>
{code}
Animation of panel showing/hiding
{code}
<script>
$("#tabs").tabs({show: true, hide: true});
</script>
{code}
Tab activation on mouse hover
{code}
<script>
$("#tabs").tabs({event: "mouseover"});
</script>
{code}
was:
Tabs widget can be implemented as navbar
{code}
<div data-role="tabs" id="tabs">
<div data-role="navbar">
<ul>
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
</ul>
</div>
<div id="one" class="ui-body-d ui-content">
</div>
<div id="two">
</div>
</div>
{code}
or as listview
{code}
<div data-role="tabs">
<style scoped="scoped">
.tablist-left {width: 35%; display: inline-block;}
.tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
</style>
<ul data-role="listview" data-inset="true" class="tablist-left">
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
<li><a href="ajax-content.html" data-ajax="false">three</a></li>
</ul>
<div id="one" class="ui-body-d tablist-content">
</div>
<div id="two" class="ui-body-d tablist-content">
</div>
</div>
{code}
Some features are not supported by data-* attributes but can be set with script
Collapsible
{code}
<script>
$("#tabs").tabs({collapsible: true});
</script>
{code}
Initially collapsed
{code}
<script>
$("#tabs").tabs({collapsible: true, active: false});
</script>
{code}
Tab disablement
{code}
<script>
$("#tabs").tabs({collapsible: true, disabled: [2]});
</script>
{code}
Animation of panel showing/hiding
{code}
<script>
$("#tabs").tabs({collapsible: true, show: true, hide: true,
disabled: [2]});
</script>
{code}
> New Tabs wizard for JQM 1.4
> ---------------------------
>
> Key: JBIDE-16347
> URL: https://issues.jboss.org/browse/JBIDE-16347
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: Tabs.png, TabsWizBan.png
>
>
> Tabs widget can be implemented as navbar
> {code}
> <div data-role="tabs" id="tabs">
> <div data-role="navbar">
> <ul>
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> </ul>
> </div>
> <div id="one" class="ui-body-d ui-content">
> </div>
> <div id="two">
> </div>
> </div>
> {code}
> or as listview
> {code}
> <div data-role="tabs">
> <style scoped="scoped">
> .tablist-left {width: 35%; display: inline-block;}
> .tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
> </style>
> <ul data-role="listview" data-inset="true" class="tablist-left">
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> <li><a href="ajax-content.html" data-ajax="false">three</a></li>
> </ul>
> <div id="one" class="ui-body-d tablist-content">
> </div>
> <div id="two" class="ui-body-d tablist-content">
> </div>
> </div>
> {code}
> Some features are not supported by data-* attributes but can be set with script
> Collapsible
> {code}
> <script>
> $("#tabs").tabs({collapsible: true});
> </script>
> {code}
> Initially collapsed
> {code}
> <script>
> $("#tabs").tabs({collapsible: true, active: false});
> </script>
> {code}
> Specifying initially active tab
> {code}
> <script>
> $("#tabs").tabs({active: 1});
> </script>
> {code}
> Tab disablement
> {code}
> <script>
> $("#tabs").tabs({disabled: [2]});
> </script>
> {code}
> Animation of panel showing/hiding
> {code}
> <script>
> $("#tabs").tabs({show: true, hide: true});
> </script>
> {code}
> Tab activation on mouse hover
> {code}
> <script>
> $("#tabs").tabs({event: "mouseover"});
> </script>
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Michelle Murray commented on JBIDE-2032:
----------------------------------------
We will need to have different links for JBT [1] and JBDS [2] documentation.
[1] for example, http://www.jboss.org/tools/docs/reference
[2] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16347) New Tabs wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16347?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16347:
------------------------------------------
Description:
Tabs widget can be implemented as navbar
{code}
<div data-role="tabs" id="tabs">
<div data-role="navbar">
<ul>
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
</ul>
</div>
<div id="one" class="ui-body-d ui-content">
</div>
<div id="two">
</div>
</div>
{code}
or as listview
{code}
<div data-role="tabs">
<style scoped="scoped">
.tablist-left {width: 35%; display: inline-block;}
.tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
</style>
<ul data-role="listview" data-inset="true" class="tablist-left">
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
<li><a href="ajax-content.html" data-ajax="false">three</a></li>
</ul>
<div id="one" class="ui-body-d tablist-content">
</div>
<div id="two" class="ui-body-d tablist-content">
</div>
</div>
{code}
Some features are not supported by data-* attributes but can be set with script
Collapsible
{code}
<script>
$("#tabs-2").tabs({collapsible: true});
</script>
{code}
Initially collapsed
{code}
<script>
$("#tabs-2").tabs({collapsible: true, active: false});
</script>
{code}
Tab disablement
{code}
<script>
$("#tabs-2").tabs({collapsible: true, disabled: [2]});
</script>
{code}
Animation of panel showing/hiding
{code}
<script>
$("#tabs-2").tabs({collapsible: true, show: true, hide: true,
disabled: [2]});
</script>
{code}
was:
Tabs widget can be implemented as navbar
{code}
<div data-role="tabs" id="tabs">
<div data-role="navbar">
<ul>
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
</ul>
</div>
<div id="one" class="ui-body-d ui-content">
</div>
<div id="two">
</div>
</div>
{code}
or as listview
{code}
<div data-role="tabs">
<ul data-role="listview" data-inset="true" class="tablist-left">
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
<li><a href="ajax-content.html" data-ajax="false">three</a></li>
</ul>
<div id="one" class="ui-body-d tablist-content">
</div>
<div id="two" class="ui-body-d tablist-content">
</div>
</div>
{code}
> New Tabs wizard for JQM 1.4
> ---------------------------
>
> Key: JBIDE-16347
> URL: https://issues.jboss.org/browse/JBIDE-16347
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: Tabs.png, TabsWizBan.png
>
>
> Tabs widget can be implemented as navbar
> {code}
> <div data-role="tabs" id="tabs">
> <div data-role="navbar">
> <ul>
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> </ul>
> </div>
> <div id="one" class="ui-body-d ui-content">
> </div>
> <div id="two">
> </div>
> </div>
> {code}
> or as listview
> {code}
> <div data-role="tabs">
> <style scoped="scoped">
> .tablist-left {width: 35%; display: inline-block;}
> .tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
> </style>
> <ul data-role="listview" data-inset="true" class="tablist-left">
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> <li><a href="ajax-content.html" data-ajax="false">three</a></li>
> </ul>
> <div id="one" class="ui-body-d tablist-content">
> </div>
> <div id="two" class="ui-body-d tablist-content">
> </div>
> </div>
> {code}
> Some features are not supported by data-* attributes but can be set with script
> Collapsible
> {code}
> <script>
> $("#tabs-2").tabs({collapsible: true});
> </script>
> {code}
> Initially collapsed
> {code}
> <script>
> $("#tabs-2").tabs({collapsible: true, active: false});
> </script>
> {code}
> Tab disablement
> {code}
> <script>
> $("#tabs-2").tabs({collapsible: true, disabled: [2]});
> </script>
> {code}
> Animation of panel showing/hiding
> {code}
> <script>
> $("#tabs-2").tabs({collapsible: true, show: true, hide: true,
> disabled: [2]});
> </script>
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-16347) New Tabs wizard for JQM 1.4
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16347?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-16347:
------------------------------------------
Description:
Tabs widget can be implemented as navbar
{code}
<div data-role="tabs" id="tabs">
<div data-role="navbar">
<ul>
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
</ul>
</div>
<div id="one" class="ui-body-d ui-content">
</div>
<div id="two">
</div>
</div>
{code}
or as listview
{code}
<div data-role="tabs">
<style scoped="scoped">
.tablist-left {width: 35%; display: inline-block;}
.tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
</style>
<ul data-role="listview" data-inset="true" class="tablist-left">
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
<li><a href="ajax-content.html" data-ajax="false">three</a></li>
</ul>
<div id="one" class="ui-body-d tablist-content">
</div>
<div id="two" class="ui-body-d tablist-content">
</div>
</div>
{code}
Some features are not supported by data-* attributes but can be set with script
Collapsible
{code}
<script>
$("#tabs").tabs({collapsible: true});
</script>
{code}
Initially collapsed
{code}
<script>
$("#tabs").tabs({collapsible: true, active: false});
</script>
{code}
Tab disablement
{code}
<script>
$("#tabs").tabs({collapsible: true, disabled: [2]});
</script>
{code}
Animation of panel showing/hiding
{code}
<script>
$("#tabs").tabs({collapsible: true, show: true, hide: true,
disabled: [2]});
</script>
{code}
was:
Tabs widget can be implemented as navbar
{code}
<div data-role="tabs" id="tabs">
<div data-role="navbar">
<ul>
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
</ul>
</div>
<div id="one" class="ui-body-d ui-content">
</div>
<div id="two">
</div>
</div>
{code}
or as listview
{code}
<div data-role="tabs">
<style scoped="scoped">
.tablist-left {width: 35%; display: inline-block;}
.tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
</style>
<ul data-role="listview" data-inset="true" class="tablist-left">
<li><a href="#one" data-ajax="false">one</a></li>
<li><a href="#two" data-ajax="false">two</a></li>
<li><a href="ajax-content.html" data-ajax="false">three</a></li>
</ul>
<div id="one" class="ui-body-d tablist-content">
</div>
<div id="two" class="ui-body-d tablist-content">
</div>
</div>
{code}
Some features are not supported by data-* attributes but can be set with script
Collapsible
{code}
<script>
$("#tabs-2").tabs({collapsible: true});
</script>
{code}
Initially collapsed
{code}
<script>
$("#tabs-2").tabs({collapsible: true, active: false});
</script>
{code}
Tab disablement
{code}
<script>
$("#tabs-2").tabs({collapsible: true, disabled: [2]});
</script>
{code}
Animation of panel showing/hiding
{code}
<script>
$("#tabs-2").tabs({collapsible: true, show: true, hide: true,
disabled: [2]});
</script>
{code}
> New Tabs wizard for JQM 1.4
> ---------------------------
>
> Key: JBIDE-16347
> URL: https://issues.jboss.org/browse/JBIDE-16347
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: Tabs.png, TabsWizBan.png
>
>
> Tabs widget can be implemented as navbar
> {code}
> <div data-role="tabs" id="tabs">
> <div data-role="navbar">
> <ul>
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> </ul>
> </div>
> <div id="one" class="ui-body-d ui-content">
> </div>
> <div id="two">
> </div>
> </div>
> {code}
> or as listview
> {code}
> <div data-role="tabs">
> <style scoped="scoped">
> .tablist-left {width: 35%; display: inline-block;}
> .tablist-content {width: 50%; display: inline-block;vertical-align: top;margin-left: 5%;}
> </style>
> <ul data-role="listview" data-inset="true" class="tablist-left">
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> <li><a href="ajax-content.html" data-ajax="false">three</a></li>
> </ul>
> <div id="one" class="ui-body-d tablist-content">
> </div>
> <div id="two" class="ui-body-d tablist-content">
> </div>
> </div>
> {code}
> Some features are not supported by data-* attributes but can be set with script
> Collapsible
> {code}
> <script>
> $("#tabs").tabs({collapsible: true});
> </script>
> {code}
> Initially collapsed
> {code}
> <script>
> $("#tabs").tabs({collapsible: true, active: false});
> </script>
> {code}
> Tab disablement
> {code}
> <script>
> $("#tabs").tabs({collapsible: true, disabled: [2]});
> </script>
> {code}
> Animation of panel showing/hiding
> {code}
> <script>
> $("#tabs").tabs({collapsible: true, show: true, hide: true,
> disabled: [2]});
> </script>
> {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
12 years, 5 months