[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=12775126#comment-12775126 ] 

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

I have implemented the getProjectForCheatsheet command.
The following is an example:

{code}
<?xml version="1.0" encoding="UTF-8"?> 
<cheatsheet title="test">
  <intro>
    <description>Test cheatsheet</description>
    
  </intro>
  <item
        skip="false"
        title="Start">
     <description>Start cheatsheet</description>
     <command
		required="true"
		returns="currentProject"
		serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet"/>
  </item>
  <item
        skip="true"
        title="MemberController.java">
     <description>Open File</description>
     <command
	    required="false"
	    serialization="org.jboss.tools.project.examples.cheatsheet.openFileInEditor(path=/${currentProject}/src/main/java/org/jboss/as/quickstarts/kitchensink/controller/MemberController.java,fromLine=43,toLine=45)"/>
  </item>
</cheatsheet>

{code}

I have had to add the required "Start" item containing the required "Start cheatsheet" command.
The user has to run the "Click to Begin/Click to Restart" command and the "Start cheatsheet" command for every cheatsheet.
\{project\} syntax has been removed.
To test this example, add it to the kitchensink project.
                
> 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