-
Notifications
You must be signed in to change notification settings - Fork 21
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
Video solutions (design discussion) #188
Comments
I'm not sure if I like the idea of separating out the video presentation into a different solution. For example, in my custom version, I've added a second solution to some examples in the applications sections that redo the same problem using trigonometry-based coordinate systems. The way I have it set up now, I have the cartesian and angular approaches in two solutions, each with an embedded video. Your idea would mean four different knowls. Speaking of solution knowls, I think it would be a good idea to add I would be more on board with the separate solutions for video embeds if it was possible to selectively enable the knowling of the solutions. It might be nice to have the textual solution always expanded, but the video one hidden behind a knowl. Not sure how easy that would be to do with PreTeXt. |
Hmm. I like having solutions in knowls, both for readability and the possibility that a student might actually try the problem before opening the solution. I've tried to get students interested in using Hypothes.is (since it's there) but there hasn't been much uptake, unless there are lots of students doing private annotations that I'm unaware of. So I would rather turn off hypothes.is than solution knowls. |
Yes, it's certainly a tradeoff. It would be nice if students would give the example a try before reading the solution, but in the real world I also know that nobody is going to actually do that. I think I come down on the side of the example solutions being a very important part of an introductory text, so I like having them not hidden. The fact that it improves Hypothesis compatibility is a nice extra. I had some success with using Hypothes.is when I tried it last semester, so I think I'll try it again. But this particular thing isn't really a big deal. The nice thing about APEX is that I can roll my own version exactly how I want it. |
Continuing the discussion from #180. @davidfarmer had suggested that having a short sentence prior to each video may not fit the design philosophy of PreTeXt. Assuming we make this change: I think it's clear what to do with videos currently in figures. Recognizing that what is "best" will be very subjective here, what is the best thing to do with them? It is also not clear to me what will happen when we have examples structured by Does it make more sense to move the video out of the example entirely, and place it just after? |
I was going to get started on changing from |
The HTML work for this is already done, maybe. For example, here: I said "maybe" because if accessibility for this matters, then CSS can't communicate that. Instead, we'd need actual icon elements in the HTML. Thinking with my PTX hat on, I think it's a good idea to have two
No. It needs 1 or more "things". Among the options for a "thing" is
Ideally there'd be multiple, shorter videos :) But no one has time to make that a priority. Suppose a video covers three tasks.
You can use the same video in all three solutions:
Requires someone spending time to find those markers... Extra credit for a calc student? If the video solution doesn't break down cleanly, you could for now just include the whole thing three times.
No.
Not in my opinion. They are logically tied to the example, so they should be tied in the XML sense with a ancestor/descendant relationship. |
Another option for an example written to use tasks instead of lists would be to put the video into the introduction: for most examples in APEX, the solution is the example -- the statement is usually fairly brief. Options available:
|
An introduction is not supposed to have numbered things in it. So a video
there couldn't be in a figure, and you'd have the no caption issue.
…On Fri, Jul 22, 2022, 6:39 AM Sean Fitzpatrick ***@***.***> wrote:
Another option for an example written to use tasks instead of lists would
be to put the video into the introduction: for most examples in APEX, the
solution *is* the example -- the statement is usually fairly brief.
Options available:
- video outside the example (I agree this is not ideal)
- video in a separate solution knowl
- @grady <https://github.com/grady> doesn't like this, but I think
@Alex-Jordan <https://github.com/Alex-Jordan> and I do.
@APEXCalculus <https://github.com/APEXCalculus> is probably
ambivalent since he will go without videos altogether
- for examples with tasks, it could be pretty labour-intensive to
split a video covering several parts across tasks (this would depend on how
many examples with an ol have video solutions. I'm guessing at
least 100)
- video in the introduction
—
Reply to this email directly, view it on GitHub
<#188 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEDOAFS66SR4RLJHAA7XYTVVKQADANCNFSM54D24BPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The only thing I'm not sure about is where I'd put the video to avoid interrupting the flow for those who are actually reading the example. |
I'm not categorically opposed to putting the videos in their own knowls, I can see some benefits. But it's worth thinking about how it would work out if there are actually two independent written solutions offered. I don't think APEX has any of these in the official version, but I've added a few here and there to my fork. |
Thinking the "PreTeXt" way about source, we shouldn't consider whether or not the output puts "X" into a knowl. The philosophy is more like, what is the best logical structure this element can have in the XML tree. Thinking that way, it may even be correct to have the video in the same "solution" as the text solution (although that's not currently my opinion). Whether or not "X" comes out in a knowl is a specific matter for the HTML translation instead of the author's source. It could be the case that logically they should be in separate "solution" elements in source, and if it is still desired to have them not be knowled or have them appear "more together" in some way, we could think about the HTML translation more. Like one idea would be to have the "solution" template do something different when the only content is a "video" element. Or when there is a following-sibling "solution" for which the only content is a "video". Although that particular approach is unlikely to be supported by PreTeXt itself, it's not a crazy thing to write custom APEX XSL for. |
Some reasons I prefer putting the video in its own knowl:
|
Changes are made in #197 but I'm not sure what this will look like in PDF. I think I would need to figure out how to modify the XSL to put the first (video) solution into the margin, or there will be a duplicate Solution heading. |
I think this should be doable but I am done for today. |
It was doable. New XSL pushed, and I've also fixed the issue with YouTube captions not fitting properly in the margin. |
@APEXCalculus @Alex-Jordan @grady I have just posted some output using the code I've committed in the pull request for videos in separate solution knowls: The PDF is compiled directly from PreTeXt output, so I have done nothing to adjust vertical positioning of margin items, insert The only thing I don't 100% like are the solution titles. These are supplied by PreTeXt, but I'm wondering if it's worth figuring out how to override them. Like most things, they're written by an XSL template. But I am already modifying the solution template for LaTeX, so... Do we keep titles like "Solution 1 (Video Solution)" and "Solution 2"? Or should I figure out how to make this become "Video Solution" and "Text Solution"? |
Whoops. The no-video version has videos. Somewhere along the way some publication files went missing, or didn't get committed. I'll fix this ASAP |
Correction: everything is fine, except for my brain. I needed to put Changes to follow. |
The link for the .pdf didn't work for me. Mind checking again?
…On Wed, Aug 17, 2022 at 12:25 PM Sean Fitzpatrick ***@***.***> wrote:
Correction: everything is fine, except for my brain.
The problem is that the no-video version left out the videos, but not the
solutions containing them.
I needed to put component="video" on the solution, not the video. (Or,
both, I guess, wouldn't hurt.)
Changes to follow.
—
Reply to this email directly, view it on GitHub
<#188 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABT5OF2YWXSMHBSLJZEY6VTVZUHA7ANCNFSM54D24BPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sorry: typo in the link. I've edited it and it works now. |
Closing this as completed. I have not implemented tasks in examples (it sounds like lists might stop being allowed in exercises at some point; unclear if this will also apply to examples) because this will take a lot more work and I don't have time. If we want to further tweak how the video solutions appear, we can reopen this issue. |
I know that at one point, @Alex-Jordan and possibly @davidfarmer were thinking about adding some technology to PreTeXt that would indicate when a resource like a video is hidden behind a solution knowl.
In the meantime, I am wondering if we should at least move the videos to separate solutions.
Current markup looks like:
It would not be hard (and can probably be done automatically) to strip out the video, and put it in a second solution;
this could carry a title to indicate the contents:
(possibly this needs an empty paragraph to be schema compliant)
If I were to update markup for exercises with parts to use
task
(see #178 ), where would we put the video?Each task carries its own solution. Does the schema allow for an additional solution outside of the tasks?
Or would it be better to move the video solutions outside of the examples entirely?
The text was updated successfully, but these errors were encountered: