Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semantic attributes in command #3

Open
bengtmartensson opened this issue Nov 9, 2017 · 1 comment
Open

Semantic attributes in command #3

bengtmartensson opened this issue Nov 9, 2017 · 1 comment

Comments

@bengtmartensson
Copy link
Owner

bengtmartensson commented Nov 9, 2017

For the next version of Girr, there should be some possibility to (non-mandatory) express semantic of a command, for example

<command name="..." ...>
   ....
    <semantic>
          <attribute name="toggle" value="true"/>
          <attribute name="powers-on" value="true"/>
          <attribute name="delay-after" value="5000"/>
    </semantic>
    ....
</command>

Girr as such should leave the interpretation to a program. Thus, no changes in the Java code are required, just an extension of the schema.

Replacement of IrScrutinizer issue.

@bengtmartensson
Copy link
Owner Author

This can be achieved by simpler means: Just allow the (already defined) element applicationData as an (optional) child element of command and commandSet. It can be used with a value of, say, semantics for the application-attribute of applicationData. applicationData is presently allowed as a child element only for remote; let's allow it for remoteSet, commandSet and command too.

Supporting it in the code is much more work...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant