- User Since
- Mar 22 2015, 9:31 AM (417 w, 5 d)
- LDAP User
- MediaWiki User
Feb 16 2019
Could you tell the expected behaviour of the rendering ? how it is supposed to look.
I'd like to work on this.
Would like to know how to merge statements for reproducing the error.
Jun 11 2018
Jun 9 2018
Dec 5 2017
@Aklapper I can mentor this task for GCI. I'll import it.
Dec 3 2017
I can mentor this, should I import it in GCI site ?
Oct 11 2017
Thanks to the Wikimedia Community and my mentors for helping me out for this Amazing project :)
Sep 20 2017
Sep 19 2017
Aug 31 2017
Importing and solving bugs : Earlier Wikipages were used to report and discuss bugs/features for the extension.All of these were imported to phabricator and each of these were resolved.
Removing legacy code and upgrading to MediaWiki standards: This task was majorly to refactor the code of the extension and use template parser to generate HTML.Static HTML code was removed.Using Template parser upgrades the extension to Mediawiki standards.
Providing Unit tests for the extension: Unit tests using PhpUnit were provided to the extension.Quiz extension has 2 Classes: Question and Quiz.Unit tests were added for both these classes providing functional coverage.
Adding required features : Various custom features were added to extension as discussed with the community.These involved changing feedback behaviour, shuffling scheme etc.
Aug 29 2017
Aug 28 2017
Aug 27 2017
Aug 26 2017
I've added it as a topic at Wikiversity:Colloquium
Aug 25 2017
We can have auto shuffling using Js instead of the shuffle buttons if that is required .
Shuffle auto for questions shuffling using JS ?
But isn't this task for shuffling of proposals/answers ?
Aug 23 2017
Aug 21 2017
Wouldn't it be confusing to have shuffle, shufflequestions and shuffleanswers ?
Currently shuffle button is used to shuffle the questions.
Aug 17 2017
Can anyone confirm the patch on localhost ?
Aug 16 2017
The feedback before the proposals can be global question feedback and we can leave it in that position while shuffling the proposals and other feedback.
This issue arises due to naming of the class in change https://gerrit.wikimedia.org/r/#/c/362793/ for bug T146370.
Aug 14 2017
Aug 12 2017
We can shuffle the proposals and their respective feedback on every reload.
After submission we can keep the order the way it was provided in the quiz syntax.
Aug 10 2017
I get your point now.
Apparently this isn't a Quiz extension thing, but how the images behave in mediawiki.
Yes I can see that I can't see the numbering when it is wrapped around the image.
Aug 9 2017
Aug 8 2017
I did try it on higher resolution.
Aug 7 2017
Updated Documentation, closing task as resolved.
I'm able to see the numbering currently.
Duplicate of invalid bug T159604.
For the Quiz a question is said to be correctly answered if all the correct proposals are selected and no wrong proposal is selected i.e
Aug 6 2017
Currently the way the patch is, the default behaviour for whole wiki would be to only show feedback of attempted questions.
Adding T172593 as parent task as this can't be done with CSS only.
Adding T172593 as parent task as this can't be done with CSS only
Aug 5 2017
If I'm right then we're trying to achieve quiz such that for each question the order of proposal (answer) changes.
As we're passing classnames with styles , can all this be combined into 1 attribute having these values as key-value pair
(this can extend functionality of T172593 ) or do we simply add these as individual parameters ?
I think you mentioned this for passing style
If the feedback is added to the source code then It is shown as per current behaviour.
Either we can simply add the CSS to Common.css right now for the proposal class or we can add new classname ( answers ) to only the following type of question :
Aug 3 2017
Are we trying to achieve something like the screenshot -
Aug 1 2017
I've added shuffleNumbering function inside ext.quiz.js that reassigns the numbering of questions for the quiz.
Jul 30 2017
Jul 28 2017
Css class can be added to feedback which can hide/show all the feedback from Common.css.
This won't be able to hide feedback of only those question that have not been attempted, it will simply hide all the feedback.
I believe you're suggesting to have multiple columns for question number 1, 2 and 7 where each column has 1 input box ?
Each question is separately called using parseQuestion function.
Inside parseQuestion the number is added inside span by keeping track Question Id.
It would not be possible in this setup to use ol tags.