[jbosstools-issues] [JBoss JIRA] (JBIDE-14333) have context sensitive parameterized commands for open file, show type etc. with proper API

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774811#comment-12774811 ] 

Snjezana Peco commented on JBIDE-14333:
---------------------------------------

{quote}
variable substitution from where ? Eclipse global variables ? should be possible to register a "cheatsheet.project" variable here would it not ? But for now \{project\} is probably fine.
{quote}

Cheatsheet variables are set within a cheatsheet. I think, we can't set this varijable since we don't know the project name when creating a cheatcheet.

{quote}
What does "profile" refer to for launchJunitTest ? junit doesn't sound like something to know about maven nor arquillian...
{quote}

The profile parameter is optional. The command will work without m2e or arquillian.
I needed that feature for the kitchensink sheatsheet.

{quote}
Can you point me to do api/docs for what you are making here ?
{quote}

There are three simple commands: OpenFileInEditorHandler, RunOnServerHandler and LaunchJUnitTestHandler

{quote}
btw. the old actions will still work, right? these are additional commands, correct?
{quote}

Correct.

{quote}
So I grok you added commands that could be invoked from cheatsheets, the JUnit test shows how you programatically invoke those commands, do you have a real cheatsheet example that would demonstrate the use for the new commands?
{quote}

No, but you can replace the actions in the existing cheatsheet (kitchensink, for instance) with the commands described in the previous message.

                
> have context sensitive parameterized commands for open file, show type etc. with proper API
> -------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14333
>                 URL: https://issues.jboss.org/browse/JBIDE-14333
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: project-examples
>            Reporter: Max Rydahl Andersen
>             Fix For: 4.1.0.Beta1, 4.1.0.Beta2
>
>
> currently our custom cheatsheet commands requires the project name(s) to be known upfront. We should make them less reliant on project names and if at all possible have the project name calculated based on the project the cheatsheet file is open in.
> The commands should also actually be commands with named parameters so the order of parameters does not matter and we should make sure these have a good and long term API so cheatsheets will continue to work well in the future.

--
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