generated from CogitoNTNU/README-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'dev' into 3-make-tetris-board
- Loading branch information
Showing
4 changed files
with
39 additions
and
41 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Development Environment | ||
|
||
We will be utilizing a virtual environment to develop the project. This will allow us to have a consistent development environment across all developers.In this case we will be using `venv` to create the virtual environment. | ||
|
||
## Getting Started | ||
|
||
* Have [Python](https://www.python.org/downloads/) installed | ||
* Verify that python is installed by running `python --version` | ||
* Pip install the virtual environment package | ||
* Verify that pip is installed by running `pip --version` | ||
* Install the virtual environment package by running `pip install virtualenv` | ||
* In the root of the project, create a virtual environment by running `python -m venv .venv` | ||
* Activate the virtual environment | ||
* On Windows, run `.venv\Scripts\activate` | ||
* On Mac/Linux, run `source .venv/bin/activate` | ||
* Done! You should now have a fully functional development environment | ||
* To deactivate the virtual environment, run `deactivate` | ||
|
||
## Dependencies | ||
Once you have entered venv you need to make sure the dependencies are installed by running `pip install -r requirements.txt`. | ||
If you use a new pip dependency, make sure to add it to the `requirements.txt` file. This can be done by running: | ||
```bash | ||
pip freeze > requirements.txt | ||
``` | ||
after you pip installed it locally, and then committing the changes. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# Cogito work night nr. 3 | ||
|
||
## Agenda | ||
|
||
- Venv | ||
- [Mer klarere plan for Tetris](#tetris) | ||
- Progge | ||
- Hva skjer neste uke? | ||
|
||
|
||
## Tetris | ||
- **Headless:** ingen grafikk ting skjer sekvensielt. En viss boardstate og en ny block -> velger presist hvor den skal plasseres (blant mulige plasser) uten tidsbegrensning. | ||
For development purpuses har vi en to print outs av brettet. Første viser brettet med den uplasserte blokken (øverst i midten), andre viser brettet etter at blokken er plassert. Bruker de objektene som vi har blitt enige om. Tanken er at vi kan bruke dette til å teste ut forskjellige algoritmer for å plassere blokken (ai/algorytme velger posisjonen). | ||
- **Grafisk:** pygame. Adapsjon av samme objekter som headless bare at vi nå styrer hvor blokken skal plasseres dynamisk. Blokken faller nedover med en viss hastighet og vi kan flytte den rundt med en viss hastighet (feks. et tastetrykk = forflytter blokken en rute). For å la agenten spille må vi lage et oversettelses lag mellom headless og grafisk, hvor vi kan sende input til grafisk for å manuvrere blokken til samme posisjon som headless ville plassert den. |