[jira] [Commented] (NETBEANS-5680) Create ProjectActions API

2021-05-17 Thread Svatopluk Dedic (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17345937#comment-17345937
 ] 

Svatopluk Dedic commented on NETBEANS-5680:
---

Hm, what was the original reason NOT to having the project actions presented as 
(abstract) j.s.Action  or ContextAwareAction ?
{quote}e.g. have a way to obtain *BUILD*, *RUN*, *DEBUG* project actions as
{quote}
You mean having some global actions for these, with ContextAware interface to 
bind them to a particular Project ? Or still a project-provided factory to 
obtain the action instances ?

> Create ProjectActions API
> -
>
> Key: NETBEANS-5680
> URL: https://issues.apache.org/jira/browse/NETBEANS-5680
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure
>Affects Versions: 12.4
>Reporter: Svatopluk Dedic
>Priority: Major
>  Labels: VSNetBeans
>
> In [https://github.com/apache/netbeans/pull/2948] surfaced a long-standing 
> issue, that clients are asked to use a SPI interface directly. This 
> complicates adding optional functionaliy to SPI as it requires *API clients* 
> to maneuver around old/new SPI impl differences.
> A proper API counterpart for *ActionProvider*, *ActionProgress* (and maybe 
> *ProjectConfiguration*) should be created.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



[jira] [Commented] (NETBEANS-5680) Create ProjectActions API

2021-05-17 Thread Jaroslav Tulach (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17345927#comment-17345927
 ] 

Jaroslav Tulach commented on NETBEANS-5680:
---

I agree that the mixing of [API|http://wiki.apidesign.org/wiki/APIvsSPI] in 
*ActionProvider* is a real problem. Another thing that bothers me when working 
with *ActionProvider* is the difference between working with regular NetBeans 
actions and project actions. My preferred API for both would be 
[ContextAwareAction|https://bits.netbeans.org/12.3/javadoc/org-openide-util-ui/org/openide/util/ContextAwareAction.html]
 - e.g. have a way to obtain *BUILD*, *RUN*, *DEBUG* project actions as 
*ContextAwareAction* instances and then just prepare *Lookup* for them 
(including instance of ***Project*, *FileObject*, etc.) and invoke them. 
Consistency achieved. Helper methods possible.

> Create ProjectActions API
> -
>
> Key: NETBEANS-5680
> URL: https://issues.apache.org/jira/browse/NETBEANS-5680
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Generic Infrastructure
>Affects Versions: 12.4
>Reporter: Svatopluk Dedic
>Priority: Major
>  Labels: VSNetBeans
>
> In [https://github.com/apache/netbeans/pull/2948] surfaced a long-standing 
> issue, that clients are asked to use a SPI interface directly. This 
> complicates adding optional functionaliy to SPI as it requires *API clients* 
> to maneuver around old/new SPI impl differences.
> A proper API counterpart for *ActionProvider*, *ActionProgress* (and maybe 
> *ProjectConfiguration*) should be created.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists