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

Implement 99th Design Meeting polls for MCP-0033 #2363

Closed
henrikt-ma opened this issue May 16, 2019 · 1 comment
Closed

Implement 99th Design Meeting polls for MCP-0033 #2363

henrikt-ma opened this issue May 16, 2019 · 1 comment
Labels
decided A decision has been made (label added before the spec is changed) MCP Generic MCP label (prefer specific MCP label for grouping of issues belonging to the same MCP)

Comments

@henrikt-ma
Copy link
Collaborator

henrikt-ma commented May 16, 2019

The following notes from the 99th Design Meeting should be implemented on the MCP/0033 branch:

Demonstrated Dymola and Wolfram Systems Modeler.
One issue is how much to add; one issue was displayUnit – in particular for time. (Axis changes also needed?) Animation is a separate issue (as a separate MCP, no overlap).

Polling:

Remove axis-range:
Favor: 1
Against: 6
Abstain: 7

Add HTML-captions (possibly several paragraphs – describing the purpose of the plot etc):
Favor: 7
Against: 0
Abstain: 7

Sub-plot title (on each plot with separate x-y axis) – note that caption may be below or on the side, so caption does not replace title:
Favor: 10
Against: 0
Abstain: 4

A separate optional identifier for each plot (in addition to title – for programmatic access, label in LaTeX):
Favor: 9
Against: 0
Abstain: 5

@HansOlsson HansOlsson added decided A decision has been made (label added before the spec is changed) MCP Generic MCP label (prefer specific MCP label for grouping of issues belonging to the same MCP) labels Jun 11, 2019
HansOlsson added a commit to HansOlsson/ModelicaSpecification that referenced this issue Jul 5, 2019
@HansOlsson
Copy link
Collaborator

Merged into branch, thus closing. (I haven't figured out how to automate this for branches.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decided A decision has been made (label added before the spec is changed) MCP Generic MCP label (prefer specific MCP label for grouping of issues belonging to the same MCP)
Projects
None yet
Development

No branches or pull requests

2 participants