Open enriqueacosta opened 5 years ago
PR #1207 puts an array="form" answer in an exercise in the Showcase article. In parallel, I made an edit to the AIM WW server. If that edit is returning acceptable static PTX, then I will distribute it to WeBWorK in general, and this issue can be closed.
I think this is done. Can @Alex-Jordan confirm and I can close?
This isn't done. We didn't settle on what PTX markup should be for an array of fillin blanks. Based on that, I wasn't able to submit a commit to WeBWorK for how it should handle answer arrays for PTX output. Based on that, nothing happened with PTX, in part because we want public PTX code to work with the most recent WW release, not just development commits on the AIM WW server.
So to move forward, step 1 is to settle on the PTX markup for an array of answer blanks. Step 2 is I submit a WW pull request. Step 3 is we wait until the next WW release. Step 4 we can put an example of this in the sample-chapter or showcase article.
Should I poke on the discussion thread about the markup?
I write this at the request of Alex (who I first mentioned this issue to) so that it is not forgotten.
Short summary (Pretext-dev message thread link below):
Pretext seems to currently not be compatible with WeBWork problems using the array_ans_rule() tool. This is used in WW to blow up any response field of an arrays or a matrix into response boxes for each entry. It is particularly useful for matrix student input when giving away the size of the matrix to the student is not an issue.
The current version of the PretextGuide, however, mentions that Pretext does support this functionality, and also has a way to author problems using this with
form="array"
:It would be nice if this support comes back!
Pretext-dev forum discussion on this topic:
https://groups.google.com/forum/#!msg/pretext-dev/ZvLP3e7DzSo/JY-4JyfNAQAJ