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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-14333:
---------------------------------------------

About cheatsheet variables: 
I looked around and it seems these are evaluated from the return values of commands.
Thus it seems you can do this without introducing a new syntax.

In the cheatsheet have:

<command
	result="currentProject"
	serialization="org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet()"/>


Now you can refer to currentProject in commands AND the content (which is rather brilliant) as ${currentProject}

No need to do this custom {project} replacement - we just need a command that will return the project for the cheatsheet.

Then content authors can even have conditionals on this variable wether it is found or not.

About "profile" and the commands:
Please point me to the javadoc/API for these - i.e. where is the code for these. The commands should have meaningful names. launchJUnit is *not* expected to mess with users profiles or arquillian enablement.

And as Fred asks, please provide an example cheatsheet that uses these commands.
                
> 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