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

Planviz to provide the (non-default) option of verbose display of TPN activities #60

Open
dcerys opened this issue Mar 29, 2017 · 1 comment

Comments

@dcerys
Copy link
Member

dcerys commented Mar 29, 2017

In the future, PLANVIZ will be the one that manages the verbosity of the activity name, where it will default to :display-name with args (see #55 )
Optionally, PLANVIZ (based on a user setting) can display the verbose version (intended to be used by a developer working on her plant implementation).

Let’s pick a simple layout for this verbose string.
If we have a plant-part, we must also have a plant-id defined for the activity. However, it is possible to have an activity with a plant-id, without a plant-part. Also, we’ll always have an interface if we have a plant-id. Finally, I suppose we can have an interface without a plant-id.
However, there are some default values that we may or may not want to make explicit at the Pamela TPN-generation level: The default value of plant-id is “plant”, and the default value of interface is “RMQ”.
So the possible combinations are:
<activity> <plant-part> <plant-id> <interface>
<activity> <plant-id> <interface>

Since there is a natural concept hierarchy here, let’s keep the delimiters simple, and use email and DNS conventions (“@" and “.” delimiters). This gives us:
<activity>@<plant-part>.<plant-id>.<interface> (e.g., "rotate-wheel(200)@left-front-wheel.vehicle1.RMQ”)
<activity>@<plant-id>.<interface> (e.g., “move-to(2,3)@vehicle1.RMQ”)

@dcerys
Copy link
Member Author

dcerys commented Jun 29, 2017

Some of this capability (e.g., plant-id) is available on the ToolTip, minimizing the priority of this enhancement.

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

2 participants