feat: flashcard student view

[tpreston2u]

The gamesxblock flashcard student view.

Testing Information:

You will need to install the xblock sdk in order to view the xblock. The following steps reference the xblock documentation on readthedocs.io (https://edx.readthedocs.io/projects/xblock-tutorial/en/latest/getting_started/prereqs.html)

1. Create a new directory for the xblock to go into and navigate to it (the documentation recommends naming it 'xblock_development').
2. Clone the gamesxblock repo into the xblock_development directory:

• gh repo clone edx/gamesxblock

4. Create and activate a virtual environment inside the xblock_development directory:

• virtualenv venv
• source venv/bin/activate

5. Clone the xblock sdk into the xblock_development directory:

• git clone https://github.com/openedx/xblock-sdk.git

6. Create an empty directory named 'var' inside the xblock_development directory.
7. Navigate to the xblock-sdk directory.
8. Install xblock sdk requirements:

• make install

9. Return to the xblock_development directory.
10. Install the gamesxblock:

• pip install -e gamesxblock

11. Create the SQLite database before running the xblock sdk

• python xblock-sdk/manage.py migrate

12. Run the xblock sdk server:

• python xblock-sdk/manage.py runserver

13. Navigate to http://localhost:8000 and select 'gamesblock' or 'Multiple GamesXBlock.'

[connorhaugh]

Hey! awesome work on this! I have a few questions/suggestions/hints from a python perspective that may or may not be helpful. I haven't tested your code, but great start!

[connorhaugh]

In my head, I assumed that this was going to be three xblocks:

• A generic GamesXblock
• A FlashCard Xblock (which inherits from GamesXblock)
• A Matching Game (which inherits from GamesXblock)

I would imagine that the two might share a lot of fields, but have key differences. Can you talk a little about why you made the choice to go about it this way? (doing it as one xblock?)

[tpreston2u]

Ray and I based our decision to use one xblock on the way the capa block was implemented. From what we can tell, the capa block doesn't use inheritance for the different problem types. Our biggest motivator to keep them in one xblock is that each xblock will exist within its own folder if we separate them. We are always open to any further input though.

[connorhaugh]

Suggested change

	self.term_is_visible = not(self.term_is_visible)
	if self.term_is_visible:
	self.term_is_visible = not(self.term_is_visible)
	return {'image': self.list[self.list_index]['definition_image'], 'text': self.list[self.list_index]['definition']}
	else:
	self.term_is_visible = not(self.term_is_visible)
	return {'image': self.list[self.list_index]['term_image'], 'text': self.list[self.list_index]['term']}

This will keep the logic a little cleaner and more readable

[connorhaugh]

make sure to not to include pyc files. In future commits you can ignore .pyc files by creating a .gitignore file

[rayzhou-bit]

Just need to make the changes Connor pointed out and it looks good to me!