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

Parameterize decision on how to render indexed vectors #1226

Open
bmaclach opened this issue Apr 24, 2019 · 1 comment
Open

Parameterize decision on how to render indexed vectors #1226

bmaclach opened this issue Apr 24, 2019 · 1 comment
Assignees
Labels
artifacts design-variability 'choices': For software families, we need design variabilities, not just requirements variabilities.

Comments

@bmaclach
Copy link
Collaborator

Based on discussion in the comments of #1222:

Currently when we index a vector in Drasil, the symbol retains the vector typeface. An alternative display option would be to render the indexed version of the vector without the vector typeface. For example, for vector P at index i, we currently render it as \bf{P}_i but another valid notation is P_i. This display decision should be parameterized in Drasil.

@smiths
Copy link
Collaborator

smiths commented Apr 25, 2019

Sounds good @bmaclach. We won't make this a priority right now, so I've labelled it as an enhancement. When the time comes, @JacquesCarette will also need to be assigned to this issue.

@balacij balacij added design-variability 'choices': For software families, we need design variabilities, not just requirements variabilities. artifacts and removed enhancement labels Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
artifacts design-variability 'choices': For software families, we need design variabilities, not just requirements variabilities.
Projects
None yet
Development

No branches or pull requests

3 participants