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

Subtitle editor: Allow to change end time of segment in timeline by drag and drop #1316

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

snoesberger
Copy link
Contributor

In the subtitle editor timeline, it was only possible to change the start time of a segment by drag and drop. This change makes it possible to change the end time in the same way.

Resolves #1314

…drop.

Fixes "e" handle for subtitle segment in timeline.
Removes code for "n" and "s" handle which is never used.
Copy link

Hi @snoesberger
Thank you for contributing to the Opencast Editor.
We noticed that you have not yet filed an Individual Contributor License Agreement. Doing that (once) helps us to ensure that Opencast stays free for all. If you make your contribution on behalf of an institution, you might also want to file a Corporate Contributor License Agreement (giving you as individual contributor a bit more security as well). It can take a while for this bot to find out about new filings, so if you just filed one or both of the above do not worry about this message!
Please let us know if you have any questions regarding the CLA.

@ziegenberg ziegenberg added the type:enhancement New feature or request label Apr 23, 2024
Copy link

Hi @snoesberger
Thank you for contributing to the Opencast Editor.
We noticed that you have not yet filed an Individual Contributor License Agreement. Doing that (once) helps us to ensure that Opencast stays free for all. If you make your contribution on behalf of an institution, you might also want to file a Corporate Contributor License Agreement (giving you as individual contributor a bit more security as well). It can take a while for this bot to find out about new filings, so if you just filed one or both of the above do not worry about this message!
Please let us know if you have any questions regarding the CLA.

@KatrinIhler
Copy link
Member

It's a bit unfortunate that I can't test this just because the ICLA hasn't been processed yet. 😅

@snoesberger
Copy link
Contributor Author

I filled in the ICLA a week ago, but haven't received a confirmation yet.

@lkiesow
Copy link
Member

lkiesow commented May 6, 2024

Apereo got the ICLA. Please just ignore the test for now. It can take a while before that is officially documented. If anyone asks, please point them to this comment.

@lkiesow
Copy link
Member

lkiesow commented May 6, 2024

It's a bit unfortunate that I can't test this just because the ICLA hasn't been processed yet. 😅

Maybe to avoid future confusion about this, a few words about the test deployment, which absence I think you are complaining about. First, you can always just clone this and run npm start locally.

Second, I think here is a misconception that the failing ICLA test has something to do with the missing test deployment. Since that is deploying code, for security reasons, it's only doing that for known developers. To be more precise, it's limited to people in the team Developers of the Opencast organization here on GitHub:

if: ${{ needs.member.outputs.is_team_member == 'true'
|| github.event.pull_request.head.repo.full_name == 'opencast/opencast-editor' }}

@gregorydlogan or I can easily add more people to that group. If you want access or want someone else to have access, just let us know. @snoesberger, I've invited you to that team.

Copy link
Member

@lkiesow lkiesow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried this and found a bug. It seems like you get two input fields for subtitles whenever you start a new subtitle:

opencast-editor-subtitle-two-input-fields.mp4

@KatrinIhler
Copy link
Member

Second, I think here is a misconception that the failing ICLA test has something to do with the missing test deployment. Since that is deploying code, for security reasons, it's only doing that for known developers. To be more precise, it's limited to people in the team Developers of the Opencast organization here on GitHub:

Ah, thx, I did not know this! Makes sense.

@snoesberger
Copy link
Contributor Author

Tried this and found a bug. It seems like you get two input fields for subtitles whenever you start a new subtitle:
opencast-editor-subtitle-two-input-fields.mp4

Thanks for testing, Lars. This is strange, I can reproduce the behaviour but only when I start the editor in development mode. If I build the editor and start the new build, only one input field is added. And I have the same behaviour when I do the same for the main branch, so it looks like this problem hasn't been added by the changes in this PR.

@snoesberger snoesberger requested a review from lkiesow May 7, 2024 11:34
Copy link
Member

@Arnei Arnei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works and simplifies the code to boot, nice.

Can confirm that the concern Lars brought up is unrelated to this pull request, as it is already happening on main.

@snoesberger
Copy link
Contributor Author

I'd love to see this PR merged. Or is there still something preventing it from being merged?

@Arnei
Copy link
Member

Arnei commented Aug 9, 2024

I don't see any blockers anymore, thanks for the reminder.

@Arnei Arnei merged commit 7e9df77 into opencast:main Aug 9, 2024
6 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Subtitle editor: change length of subtitle segment in the timeline
5 participants