Difference between revisions of "Summer of Code/2018/Sugarizer Exerciser Activity"
(5 intermediate revisions by the same user not shown) | |||
Line 36: | Line 36: | ||
* Integrate presence in sprint math | * Integrate presence in sprint math | ||
* Design mockups of exercise activity (GSoC project) | * Design mockups of exercise activity (GSoC project) | ||
+ | |||
+ | === GSoC Period: === | ||
+ | |||
+ | ==== Meeting (14/5/18): ==== | ||
+ | The meeting centered around moving from the sprint math activity to the GSoC project, Exerciser Activity. The progress made during community bonding period was discussed along with approaching our GSoC project. In the meeting the following tasks were asked for the week: | ||
+ | * Update the wiki page for the project | ||
+ | * Fix the restart in presence of sprint math activity | ||
+ | * Build a demo sugarizer activity using reactjs | ||
+ | * Build Mockups for the proposed sugarizer activity | ||
+ | * Make exerciser activity repo | ||
+ | * Update the blog | ||
+ | |||
+ | ==== Meeting (23/5/18): ==== | ||
+ | [[File:Dashboard view.jpg|thumb|200x200px]] | ||
+ | The meeting was centered around the react demo activity that I built last weeks and some mockups were discussed for the Sugarizer activity. The mockup that we agreed on was is on the right. In the meeting the following tasks were asked for the week: | ||
+ | * Update the wiki page for the project | ||
+ | * Initialise reactJS in exerciser activity | ||
+ | * Make a demo dash board | ||
+ | * Update the blog | ||
+ | |||
+ | ==== Meeting (1/6/18): ==== | ||
+ | Due to my exams, the task load of last week was low, and incomplete tasks were tasked for next week. My tasks for next week are given below: | ||
+ | * Update the wiki page for the project | ||
+ | * Initialise reactJS in exerciser activity | ||
+ | * Make a demo dash board | ||
+ | |||
+ | ==== Meeting (8/6/18): ==== | ||
+ | Due to my exams, the task load of last week was low, and incomplete tasks were tasked for next week. My tasks for next week are given below: | ||
+ | * Update the wiki page for the project | ||
+ | * Build exercise builder form | ||
+ | * Update the blog post | ||
+ | |||
+ | ==== Meeting (15/6/18): ==== | ||
+ | Last week task of building the MCQ template exercise was completed. Tasks for next week are given below: | ||
+ | * Sugarize the UI | ||
+ | * Handle Localization | ||
+ | * Fix Scrolling Issue | ||
+ | * Implement running exercise (priority) | ||
+ | * Add update/delete exercise | ||
+ | |||
+ | ==== Meeting (22/6/18): ==== | ||
+ | The Tasks laid out for next week were the following: | ||
+ | * fix bugs (scroll/reorder/submit) | ||
+ | * save user time to complete exercise | ||
+ | * build a result screen using chart.js | ||
+ | * Limit number of button | ||
+ | * Localization | ||
+ | ==== Meeting (29/6/18): ==== | ||
+ | The Tasks laid out for next week were the following: | ||
+ | * Handle Localization | ||
+ | * Start Building Cloze Text | ||
+ | * Sugarize the UI | ||
+ | ==== Meeting (6/7/18): ==== | ||
+ | The Tasks laid out for next week were the following: | ||
+ | * Take lang input from Sugarizer settings | ||
+ | |||
+ | * Finish Building Cloze Text Template | ||
+ | ==== Meeting (12/7/18): ==== | ||
+ | The Tasks laid out for next week were the following: | ||
+ | * Creating a write in option in CLOZE template | ||
+ | |||
+ | * Adding next blank in edit mode of CLOZE template | ||
+ | * Improve text rendering | ||
+ | * Adding buttons to restart from score screen and edit mode | ||
+ | * Start working on Reorder List template | ||
+ | ==== Meeting (20/7/18): ==== | ||
+ | The Tasks laid out for next week were the following: | ||
+ | * White space need at the end of a placeholder | ||
+ | |||
+ | * Try to use regexp instead of string comparaison | ||
+ | * Change emplacement of restart button in score screen: bottom right | ||
+ | * Add a Test button to go to Run mode from Edit mode | ||
+ | * Implement Run mode for reorder template | ||
+ | * Handle datastore for the app |
Latest revision as of 06:39, 21 July 2018
About The Project:
The aim of the project is to create a Sugarizer Activity that can be used by the educators to create exercises for their students based on their curriculum. The educators will be able to enter the questions and answers into the activity and share that activity on the server for students to use. After the activity is shared the students on the server will be able to do the assignment and get a final score at the end.
Student:
Mankirat Singh
Mentors:
Lionel Laske
Michaël Ohayon
Community Bonding Period:
During the bonding period we'll do 2 things:
- Use the Sprint Math activity developed by Mankirat as a sandbox to learn development of a Sugarizer activity
- Detail UI and features of the Exerciser activity
First Meeting (30/4/18):
The meeting was centered around communication, due dates and structure/ time of future meetings.
In the first meeting the following tasks were asked:
- Build a wiki page for the project
- Update the UI of sprint math activity
- Refactor code of sprint math activity so that presence can be added later
- Update the SVG icon of sprint math activity
- Integrate Palette in sprint math activity
- Design mockups of exercise activity (GSoC project)
Second Meeting (9/5/18):
The meeting was centered around tasks given in the last meeting, tasks for the next meeting and other development environment issues i was facing.
In the meeting the following tasks were asked:
- Update the wiki page for the project
- Update the UI of sprint math activity
- Review complexity of the questions in sprint math
- Fix the css issue on chrome
- Integrate presence in sprint math
- Design mockups of exercise activity (GSoC project)
GSoC Period:
Meeting (14/5/18):
The meeting centered around moving from the sprint math activity to the GSoC project, Exerciser Activity. The progress made during community bonding period was discussed along with approaching our GSoC project. In the meeting the following tasks were asked for the week:
- Update the wiki page for the project
- Fix the restart in presence of sprint math activity
- Build a demo sugarizer activity using reactjs
- Build Mockups for the proposed sugarizer activity
- Make exerciser activity repo
- Update the blog
Meeting (23/5/18):
The meeting was centered around the react demo activity that I built last weeks and some mockups were discussed for the Sugarizer activity. The mockup that we agreed on was is on the right. In the meeting the following tasks were asked for the week:
- Update the wiki page for the project
- Initialise reactJS in exerciser activity
- Make a demo dash board
- Update the blog
Meeting (1/6/18):
Due to my exams, the task load of last week was low, and incomplete tasks were tasked for next week. My tasks for next week are given below:
- Update the wiki page for the project
- Initialise reactJS in exerciser activity
- Make a demo dash board
Meeting (8/6/18):
Due to my exams, the task load of last week was low, and incomplete tasks were tasked for next week. My tasks for next week are given below:
- Update the wiki page for the project
- Build exercise builder form
- Update the blog post
Meeting (15/6/18):
Last week task of building the MCQ template exercise was completed. Tasks for next week are given below:
- Sugarize the UI
- Handle Localization
- Fix Scrolling Issue
- Implement running exercise (priority)
- Add update/delete exercise
Meeting (22/6/18):
The Tasks laid out for next week were the following:
- fix bugs (scroll/reorder/submit)
- save user time to complete exercise
- build a result screen using chart.js
- Limit number of button
- Localization
Meeting (29/6/18):
The Tasks laid out for next week were the following:
- Handle Localization
- Start Building Cloze Text
- Sugarize the UI
Meeting (6/7/18):
The Tasks laid out for next week were the following:
- Take lang input from Sugarizer settings
- Finish Building Cloze Text Template
Meeting (12/7/18):
The Tasks laid out for next week were the following:
- Creating a write in option in CLOZE template
- Adding next blank in edit mode of CLOZE template
- Improve text rendering
- Adding buttons to restart from score screen and edit mode
- Start working on Reorder List template
Meeting (20/7/18):
The Tasks laid out for next week were the following:
- White space need at the end of a placeholder
- Try to use regexp instead of string comparaison
- Change emplacement of restart button in score screen: bottom right
- Add a Test button to go to Run mode from Edit mode
- Implement Run mode for reorder template
- Handle datastore for the app