-
Notifications
You must be signed in to change notification settings - Fork 5
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
Flash Cards - Add in Math Equation support #2
Comments
Needs QA before pull request. See issue/562-math-equation-support on materia, clu Known issues:
|
QAing |
Incoming issue dump:
|
The above issues are fixed. Consider the following quirks:
|
If we can clean up the output in your example that would be cool, but it's not a deal-breaker IMO. Disabling math input when an image is included seems like a reasonable solution. Here's what I found:
These issues from last time are still occuring to me:
Importing: Perhaps what I'm describing could be a good direction but we could spawn it into another issue if needed. The current behavior isn't a deal breaker - if someone imports a question and they get a bunch of junk HTML instead of an expected equation they'll be annoyed but they can just delete the question or HTML and replace it manually. |
I checked off issues 2, 4 and 5. 2 only happened to questions created on a previous version of this branch. 4 and 5 were because I hadn't pulled T_T |
|
In an effort to add Math symbol support in Materia let's start by adding Math equations into Flash Cards.
Faculty should be able to add in math equations fairly easily, but since this will most likely not be the dominate use case I'd want to make sure the UI/UX to add in a math equation minimally disrupts the interface.
Depending on the difficulty of entering in math equations we may need additional help or explanation on how this is done.
Ideally the library used to add in math equation support should be loaded conditionally when needed, so we don't need to bake it in to every Flash Cards instance. I'm not sure how difficult this is with our current setup.
The text was updated successfully, but these errors were encountered: