[JBoss JIRA] (JBIDE-18960) Content assist for value of attribute list of html5 tag input
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18960?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18960:
-----------------------------------
Comment: was deleted
(was: !datalistca.png!)
> Content assist for value of attribute list of html5 tag input
> -------------------------------------------------------------
>
> Key: JBIDE-18960
> URL: https://issues.jboss.org/browse/JBIDE-18960
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> List attribute refers to a <datalist> element that contains pre-defined options for an <input> element
> 1. Create an html file
> 2. Add the following code:
> {code:html}
> <datalist id="browsers">
> <option value="Internet Explorer">
> <option value="Firefox">
> <option value="Chrome">
> <option value="Safari">
> </datalist>
>
> <datalist id="os">
> <option value="Windows">
> <option value="Linux">
> <option value="Mac">
> </datalist>
>
> <input list="" name="browser">
> {code}
> 3. Ctrl+Space for <input list="|"> should propose "os" and "browsers":
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18960) Content assist for value of attribute list of html5 tag input
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18960?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18960:
-----------------------------------
Description:
List attribute refers to a <datalist> element that contains pre-defined options for an <input> element
1. Create an html file
2. Add the following code:
{code:html}
<datalist id="browsers">
<option value="Internet Explorer">
<option value="Firefox">
<option value="Chrome">
<option value="Safari">
</datalist>
<datalist id="os">
<option value="Windows">
<option value="Linux">
<option value="Mac">
</datalist>
<input list="" name="browser">
{code}
3. Ctrl+Space for <input list="|"> should propose "os" and "browsers":
was:List attribute refers to a <datalist> element that contains pre-defined options for an <input> element
> Content assist for value of attribute list of html5 tag input
> -------------------------------------------------------------
>
> Key: JBIDE-18960
> URL: https://issues.jboss.org/browse/JBIDE-18960
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
> Attachments: datalistca.png
>
>
> List attribute refers to a <datalist> element that contains pre-defined options for an <input> element
> 1. Create an html file
> 2. Add the following code:
> {code:html}
> <datalist id="browsers">
> <option value="Internet Explorer">
> <option value="Firefox">
> <option value="Chrome">
> <option value="Safari">
> </datalist>
>
> <datalist id="os">
> <option value="Windows">
> <option value="Linux">
> <option value="Mac">
> </datalist>
>
> <input list="" name="browser">
> {code}
> 3. Ctrl+Space for <input list="|"> should propose "os" and "browsers":
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3208:
-----------------------------
Description:
Be it resolved - we should reorg directories for consistency across JBT/JBDS:
Latest suggestion:
* /\{mars,9.0}/
** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
*** /*updates*/
**** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
*** /*builds*/
**** /<job-name>/
***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
---
Older idea:
{code}
<download.jboss.org,devstudio.redhat.com>
<earlyaccess,updates,discovery>/<mars,9.0>
/snapshots [replace nightly]
/staging [rename content for QE, moves to development when approved]
/development
/stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
drop /integration (not used)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last N builds
targetplatforms/<type>/<version>
{code}
Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was:
Be it resolved - we should reorg directories for consistency across JBT/JBDS:
Latest suggestion:
* /\{mars,9.0}/
** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
*** /*updates*/
**** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
*** /*builds*/
**** /<job-name>/
***** /{*<pull-request-version = PR123, PR124, PR125...>*, <build-version = B123, B124, B125...>}/
---
Older idea:
{code}
<download.jboss.org,devstudio.redhat.com>
<earlyaccess,updates,discovery>/<mars,9.0>
/snapshots [replace nightly]
/staging [rename content for QE, moves to development when approved]
/development
/stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
drop /integration (not used)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last N builds
targetplatforms/<type>/<version>
{code}
Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3208:
-----------------------------
Description:
Be it resolved - we should reorg directories for consistency across JBT/JBDS:
Latest suggestion:
* /\{mars,9.0}/
** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
*** /*updates*/
**** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
*** /*builds*/
**** /<job-name>/
***** /{*<pull-request-version = PR123, PR124, PR125...>*, <build-version = B123, B124, B125...>}/
---
Older idea:
{code}
<download.jboss.org,devstudio.redhat.com>
<earlyaccess,updates,discovery>/<mars,9.0>
/snapshots [replace nightly]
/staging [rename content for QE, moves to development when approved]
/development
/stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
drop /integration (not used)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last N builds
targetplatforms/<type>/<version>
{code}
Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
was:
Be it resolved - we should reorg directories for consistency across JBT/JBDS:
{code}
download.jboss.org
<earlyaccess,updates,discovery>/mars
/snapshots [replace nightly]
/staging [rename content for QE, moves to development when approved]
/development
/stable (updates/mars/stable is a pointer back into updates/mars)
drop /integration (not used)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last 2 builds
targetplatforms/<type>/<version>
{code}
and
{code}
devstudio.redhat.com
<earlyaccess,updates,discovery>/9.0
/snapshots
/staging
/development
/stable (updates/9.0/stable is a pointer back into updates/9.0)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last 2 builds
targetplatforms/<type>/<version>
{code}
Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
[2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{*<pull-request-version = PR123, PR124, PR125...>*, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18961) Simplify the release process wrt link to blog announcement in products.yml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18961?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18961:
--------------------------------------
Assignee: Xavier Coulon
> Simplify the release process wrt link to blog announcement in products.yml
> --------------------------------------------------------------------------
>
> Key: JBIDE-18961
> URL: https://issues.jboss.org/browse/JBIDE-18961
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: website
> Affects Versions: 4.2.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
>
> We could change the way the blog announcement is link to the release by adding specific attributes in the blog file, which avoid having to link to it from the products.yml file, which happens to be a bit tricky in term of flow, because the blog author should not really care about the products.yml, which is rather the responsability of the release engineers.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18961) Simplify the release process wrt link to blog announcement in products.yml
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18961:
-------------------------------------
Summary: Simplify the release process wrt link to blog announcement in products.yml
Key: JBIDE-18961
URL: https://issues.jboss.org/browse/JBIDE-18961
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: website
Affects Versions: 4.2.1.Final
Reporter: Xavier Coulon
We could change the way the blog announcement is link to the release by adding specific attributes in the blog file, which avoid having to link to it from the products.yml file, which happens to be a bit tricky in term of flow, because the blog author should not really care about the products.yml, which is rather the responsability of the release engineers.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-17058) Add new widgets to HTML 5.0 Palette
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17058?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-17058:
-----------------------------------------------
For content assist in list="| ", new issue is created: JBIDE-18960.
> Add new widgets to HTML 5.0 Palette
> -----------------------------------
>
> Key: JBIDE-17058
> URL: https://issues.jboss.org/browse/JBIDE-17058
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.x
>
>
> Now HTML5 has only 5 elements: <form>, <label>, <audio>, <image>, <video>.
> However, there are a lot of new elements in HTML 5.0 (http://www.w3schools.com/html/html5_new_elements.asp) <canvas>, <embed>, <datalist>, <keygen>, <output>, <header>, <nav>, <section>, <main>, <article>, <aside>, <footer>, <details>, <summary>, <figure>, <mark>, <time>, <bdi>, <wbr>, <dialog>, <meter>, <progress>.
> Besides, some old elements, like <table> also can be added to the palette.
> [~burrsutter], [~maxandersen], could you please advise, which elements may be nice to add to the HTML 5.0 palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18960) Content assist for value of attribute list of html5 tag input
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18960:
---------------------------------------------
Summary: Content assist for value of attribute list of html5 tag input
Key: JBIDE-18960
URL: https://issues.jboss.org/browse/JBIDE-18960
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
List attribute refers to a <datalist> element that contains pre-defined options for an <input> element
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18959) New Datalist wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18959?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-18959 at 12/15/14 5:21 PM:
-------------------------------------------------------------------------
[~dazarov], please create icons for Datalist palette item and wizard.
was (Author: scabanovich):
Daniel Azarov, please create icons for Datalist palette item and wizard.
> New Datalist wizard for HTML5 palette
> -------------------------------------
>
> Key: JBIDE-18959
> URL: https://issues.jboss.org/browse/JBIDE-18959
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months