[JBoss JIRA] (JBIDE-10219) Migrate org.eclipse.core.runtime.contentTypes extension points to org.eclipse.core.contenttype.contentTypes
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10219?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-10219:
----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-hibernate/pull/22, https://github.com/jbosstools/jbosstools-server/pull/133, https://github.com/jbosstools/jbosstools-javaee/pull/125, https://github.com/jbosstools/jbosstools-jbpm/pull/16, https://github.com/jbosstools/jbosstools-jst/pull/203 (was: https://github.com/jbosstools/jbosstools-hibernate/pull/22, https://github.com/jbosstools/jbosstools-server/pull/133, https://github.com/jbosstools/jbosstools-javaee/pull/125, https://github.com/jbosstools/jbosstools-jbpm/pull/16)
> Migrate org.eclipse.core.runtime.contentTypes extension points to org.eclipse.core.contenttype.contentTypes
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-10219
> URL: https://issues.jboss.org/browse/JBIDE-10219
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: archives, common/jst/core, hibernate, jbpm, Seam 2, server
> Affects Versions: 3.3.0.M4
> Reporter: Denis Golovin
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Alpha1
>
> Attachments: JBIDE-10219.patch
>
>
> ||Module|| PR || Status ||
> |[Hibernate|https://github.com/jbosstools/jbosstools-hibernate]| https://github.com/jbosstools/jbosstools-hibernate/pull/22 | |
> |[Server|https://github.com/jbosstools/jbosstools-server]| https://github.com/jbosstools/jbosstools-server/pull/133 | Merged |
> |[JST|https://github.com/jbosstools/jbosstools-jst]| not affected | |
> |[Java EE|https://github.com/jbosstools/jbosstools-javaee]| https://github.com/jbosstools/jbosstools-javaee/pull/125 | Merged |
> |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| https://github.com/jbosstools/jbosstools-jbpm/pull/16 | |
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15379) Hyperlink on CSS file links works only for Dynamic Web Projects
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-15379:
-------------------------------------
Summary: Hyperlink on CSS file links works only for Dynamic Web Projects
Key: JBIDE-15379
URL: https://issues.jboss.org/browse/JBIDE-15379
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.1.0.Final
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Now we have WTP hyperlink "Open 'filename ' with CSS Editor" which works on every kind of projects.
We need just delete our hyperlink org.jboss.tools.jst.text.ext.hyperlink.JSPStylesheetRelLinkHyperlink
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15378) Basic content assist for static AngularJS ng-* attributes
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15378?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15378:
----------------------------------------
{quote}
Directives have camel cased names such as ngBind. The directive can be invoked by translating the camel case name into snake case with these special characters :, -, or _
Optionally the directive can be prefixed with x-, or data- to make it HTML validator compliant.
{quote}
http://docs.angularjs.org/guide/directive
It means that for example for *ngTrueValue* parameter of input [select] directive we have the following list of all possible combinations:
{code}
<input ng-true-value="..." >
<input ng-true_value="..." >
<input ng-true:value="..." >
<input ng_true-value="..." >
<input ng_true_value="..." >
<input ng-true:value="..." >
<input ng:true-value="..." >
<input ng:true_value="..." >
<input ng:true:value="..." >
<input data-ng-true-value="..." >
<input data-ng-true_value="..." >
<input data-ng-true:value="..." >
<input data-ng_true-value="..." >
<input data-ng_true_value="..." >
<input data-ng-true:value="..." >
<input data-ng:true-value="..." >
<input data-ng:true_value="..." >
<input data-ng:true:value="..." >
<input x-ng-true-value="..." >
<input x-ng-true_value="..." >
<input x-ng-true:value="..." >
<input x-ng_true-value="..." >
<input x-ng_true_value="..." >
<input x-ng-true:value="..." >
<input x-ng:true-value="..." >
<input x-ng:true_value="..." >
<input x-ng:true:value="..." >
{code}
So there are 18!!! correct ways of using ngTrueValue directive. It would be a mess if we support all the options and show 18 proposals just for one attribute. IMO we should support only the most used style ng-* (i.g. ng-true-value="...") and probably the HTML5 specification friendly way: data-ng-true-value:
{code}
<input ng-true-value="..." >
<input data-ng-true-value="..." >
{code}
[~maxandersen] what do you think?
> Basic content assist for static AngularJS ng-* attributes
> ---------------------------------------------------------
>
> Key: JBIDE-15378
> URL: https://issues.jboss.org/browse/JBIDE-15378
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.x, 4.2.0.Alpha1
>
>
--
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
10 years, 10 months
[JBoss JIRA] (JBIDE-15378) Basic content assist for static AngularJS ng-* attributes
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15378?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15378:
-----------------------------------
Description:
We can't fix eclipse validation markers of ng-app in Kepler but we can at least make it easier to write them by adding content assist for them as done for jquery data.
It won't include dynamic content though - that will have to wait for next major release.
> Basic content assist for static AngularJS ng-* attributes
> ---------------------------------------------------------
>
> Key: JBIDE-15378
> URL: https://issues.jboss.org/browse/JBIDE-15378
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.1.x, 4.2.0.Alpha1
>
>
> We can't fix eclipse validation markers of ng-app in Kepler but we can at least make it easier to write them by adding content assist for them as done for jquery data.
> It won't include dynamic content though - that will have to wait for next major release.
--
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
10 years, 10 months