-
Notifications
You must be signed in to change notification settings - Fork 343
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
TA: move Questionlist into Slate #6148
Conversation
11ce9ef
to
1469d22
Compare
@kergomard is working on the settings (https://github.com/kergomard/ILIAS/commits/9/test/feature_use_ks_forms_for_general_settings); |
@nhaagen I plan to give @kergomard feedback on his PR before his vacation. Also, I am sorry, but maybe we need to change "Test Pass Overview" after the feedback from @matthiaskunkel on this Mantis issue. |
d5c5445
to
00f91ea
Compare
c75a276
to
9d9a1d6
Compare
9d9a1d6
to
c77837d
Compare
Hi @dsstrassner , |
Hi @nhaagen, first remark. I got an error by trying to import the attached tst export. (I use doil with this branch: https://github.com/kergomard/ILIAS/tree/_9/TA/QuestionList because of other test and trunk problems.): Stacktrace:
I had no problems to import this test to the doil instance where I tested the Result-Presentation ;-) |
@matthiaskunkel has decided, how the translation and labels should be and changed that for trunk and ILIAS 8: https://mantis.ilias.de/view.php?id=26823#c95923 Please note this during implementation. Thanks in advance @nhaagen |
75bb12c
to
bef0dce
Compare
Hi @nhaagen could you please rebase and resolve the conflicts. After Max huge PR, I got now some errors, so I could not retest your changes. Thanks in advance. |
2569d3f
to
0fe4a9e
Compare
Opening the setting tab of a test: Stacktrace: And Create a question: ArgumentCountError thrown with message "Too few arguments to function ilTestQuestionSetConfigFactory::__construct(), 6 passed in /var/www/html/Modules/TestQuestionPool/classes/class.assQuestionGUI.php on line 848 and exactly 7 expected" Stacktrace: I think here are also some commits missing. |
44052f1
to
7935437
Compare
With the latest commit, there is a super-small change to the UI-Interface: buttons->withUnavailableAction accepts a "false"-paramter as well. |
e79fcf3
to
6f3450b
Compare
I spoke briefly with @dsstrassner about the action menu of the question. I think it's right to change the dropdown into our UI dropdown component as you plan to do and live with both options being offered for now, even if only one can be executed. I think it can be implemented temporarily in this way, because after executing the action, there is direct feedback (i.e. as a user, I see whether my answer or input has been deleted or not - if necessary, I repeat the step with the other action). If this problem can be eliminated as soon as possible afterwards, all the better (perhaps instead of greying out, the two actions should perhaps even replace each other). Please consider the following suggestions:
Best regards |
Hi @nhaagen, thank you for your patience. But now we have the situation, that "Delete Answers" does not work.
I could not delete a saved answer: Entering an answer, going to the next or previous question (to save the answer), going back and selecting "Delete Answer" has no effect. The answer(s) are not deleted. The other things from this Feature Request work like a charm. |
2a0a617
to
ba168f5
Compare
I rebased again and, for the sake of this PR, "fixed" the discardAnswer-action. |
hi @kergomard, from my point of view, you are ready to go ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for this improvement @nhaagen !
Please answer the following questions:
- Do we really need
withHighPriority()
on all the modifications? For me this smells quite a bit. - This looks overly complicated. I think this should be enough, right:
fn($id) => "document.getElementById('$id').addEventListener(
'click',
(event)=>{
event.target.name = 'cmd[discardSolution]';
event.target.form.requestSubmit(event.target);
}
)"
I've a few small change request:
- Could you please rename the table row containing the settings for the Question List to something similar as we then use in the code? It took me a while to understand that the table column for 'usr_pass_overview_mode' is 'show summary'. I would suggest to really use the full name 'usr_pass_overview_mode'.
- Could you please use strict typing here
- Could you please move the namespaces here to a use statement.
This is just a note for the release notes (if not already on our radar): Question-List-Settings from previous ILIAS-Versions will not be imported correctly.
Thanks again and best!
@kergomard
- remove toggle button - show always as mainbar-tools - translate 'Dashboard', remove SideListGUI - move title, username and test-id into header
f6aad58
to
94a8dae
Compare
Hi @kergomard , |
Hi @nhaagen A very real use case this caused me a lot of grieve is the SEB-Plugin. Thanks and best, |
Hi @nhaagen I just checked the rest (my afternoon started early ;-) ). Apart from the question of the Priorities, it is ready to be merged. All checks fail, but this is unrelated. Thanks again and best, |
Unfortunately, we cannot drop Prios alltogether and lowPriority will already conflict; I used a const to go slightly above "low" and leave enough room for further modifications. This is certainly not ideal, but the best I can come up with. |
Thank you very much @nhaagen ! I will merge this now as it is. Best, |
I'd like to add something to my comment above from Sep 27 that I've stumbled across and learned more about in the meantime. This has no effect on the merge and is just for the purpose of recording this in case it is useful later.
As a correction to my suggestion above: "Do not show" an option is not recommended for contextual menus, but "Disable" is. See https://www.nngroup.com/articles/contextual-menus/ : "Disable items that are irrelevant to the user's context. Instead of hiding irrelevant actions, disable them so that users don't have to try to figure out where menu items disappeared, or figure out how to get the system back into the right context to display a particular command." |
https://docu.ilias.de/goto.php?target=wiki_1357_Revamping_Exam_View_with_List_of_Questions
Move „List of Questions“ to Slate:
There is no need for this button anymore as the “List of Questions” can be displayed via the main bar item.
“WorkflowListing” can identify the currently processed question and differentiate between questions which were processed and those which weren’t.
The only things “WorkflowListing” cannot do is to show the “flag” of questions that were “marked” by participants.As this would contribute to unclutter the view, we suppose it being a gain for the Exam View.
In doing so, we suggest to show the installation logo as well.
Settings
The “Dashboard” term is used in three different ways in ILIAS (main bar item, Test object tab, “Dashboard” as referred to here). Thus, it would contribute to disambiguation to rename the “Dashboard” option for the test GUI. Proposal: “Test Pass Overview” (German: “Übersicht Testdurchlauf”)
Activation of „List of Questions” (Checkbox)
Activation of “Test Pass Overview” (Checkbox) with sub-options (“Show prior to the first question” s.o.)