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

Rename several pages #2265

Merged
merged 3 commits into from
Dec 4, 2023
Merged

Conversation

Alex-Jordan
Copy link
Contributor

This makes more name changes discussed at #1992.

'Homework Sets'      => 'Assignments',
'User Settings'      => 'Account Settings',
'User Manager'       => 'Accounts Manager'
'Set Assigner'       => 'Assigner Tool',
'Set Manager'        => 'Sets Manager',
'Achievement Editor' => 'Achievements Manager'

It also changes the order of nav items a little, moving "Assigner Tool" (formerly "Set Assigner") higher up.

Lastly, while reviewing all the places to make name changes, I found a few vestiges of previous names that had never been changed.

Copy link
Member

@drgrice1 drgrice1 left a comment

Choose a reason for hiding this comment

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

I think this looks good.

However, I don't like having the "Assigner Tool" first after "Instructor Tools". In my opinion the two most important and most accessed instructor tools are the "Accounts Manager" and the "Sets Manager", and I think those should be listed first. The "Assigner Tool" connects accounts with sets, and so it makes more sense that it be listed third.

I don't understand how moving the "Assigner Tool" first after "Instructor Tools" helps in any real way with getting used to the new menu (as @somiaj put it).

@somiaj
Copy link
Contributor

somiaj commented Nov 27, 2023

I don't like the "Assigner Tool" is currently between "Accounts Manager" and "Sets Manager". I'm okay with it being after those two as well, but it is currently between them which is taking me a while to get use to.

If that isn't a good place for others, maybe leave position alone in this PR and only focus on renaming.

@Alex-Jordan
Copy link
Contributor Author

Alex-Jordan commented Nov 27, 2023 via email

@Alex-Jordan
Copy link
Contributor Author

Alex-Jordan commented Nov 27, 2023 via email

Copy link
Member

@drdrew42 drdrew42 left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Member

@drgrice1 drgrice1 left a comment

Choose a reason for hiding this comment

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

This generally looks good.

There are several instances of "Set Manager" that need to be changed to "Sets Manager" in templates/HelpFiles/InstructorUserList.html.ep on lines 153-168.

There are comments on lines 238 and 516 of conf/localOverrides.conf.dist that refer to the "homework sets editor".

There are references to "homework sets" in templates/ContentGenerator/Hardcopy/form.html.ep lines 11 and 68, templates/ContentGenerator/Instructor/Assigner.html.ep line 9, templates/ContentGenerator/Instructor/ProblemGrader.html.ep line 37, templates/ContentGenerator/Instructor/ProblemSetList.html.ep line 35, templates/ContentGenerator/Instructor/UsersAssignedToSet.html.ep lines 9, 25, and 92, templates/HelpFiles/InstructorScoring.html.ep line 24, templates/HelpFiles/InstructorUserList.html.ep at numerous places, and templates/HelpFiles/instructor_links.html.ep on lines 40 and 46-48. Should all of those be changed? Should we go all of the way and eliminate the word "homework" displayed in the UI? That might be a lot of work.

@@ -6,12 +6,12 @@
% }
<ul class="nav flex-column">
% if (defined $courseID && $authen->was_verified) {
% # Homework Sets or Course Administration
% # Assignments or Course Administration
Copy link
Member

Choose a reason for hiding this comment

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

This comment should be updated. This file no longer has anything to do with "Course Administration", and there isn't even such a link in the Admin course anymore.

@Alex-Jordan
Copy link
Contributor Author

There are comments on lines 238 and 516 of conf/localOverrides.conf.dist that refer to the "homework sets editor".

Do I understand right that both of these should be referring to the Library Browser?

@drgrice1
Copy link
Member

There are comments on lines 238 and 516 of conf/localOverrides.conf.dist that refer to the "homework sets editor".

Do I understand right that both of these should be referring to the Library Browser?

Both of those lines actually apply to both the Library Browser and the Set Detail page. Although the $pg{displayModes} really applies to a lot more than just those pages and is a course configuration option.

@Alex-Jordan
Copy link
Contributor Author

I am replacing lots of these words/phrases with the approach that it is an "assignment" if it's in the context of something that has been assigned to a user. Otherwise, it is a "set". Does that sound OK?

@Alex-Jordan
Copy link
Contributor Author

Both of those lines actually apply to both the Library Browser and the Set Detail page.

I see how line 238 applies to both. But line 516 is about set definition search depth. How does that apply to Set Detail?

@drgrice1
Copy link
Member

I am replacing lots of these words/phrases with the approach that it is an "assignment" if it's in the context of something that has been assigned to a user. Otherwise, it is a "set". Does that sound OK?

Sounds good to me.

@drgrice1
Copy link
Member

I see how line 238 applies to both. But line 516 is about set definition search depth. How does that apply to Set Detail?

The search depth is also used for the import sets drop-down on the sets manager page. Your right, not the set detail page. However, that was the homework sets editor.

@pstaabp pstaabp merged commit d93dd6f into openwebwork:develop Dec 4, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants