initial commit

Author: aayushi-droid

1. Display Image with pygame.py

@@ -0,0 +1,37 @@
+"""Display Image With Pygame"""
+
+import pygame
+
+pygame.init()
+
+display_width = 800
+display_height = 600
+gameDisply= pygame.display.set_mode((display_width, display_height))
+pygame.display.set_caption("Race Game")
+
+black = (0, 0, 0)
+white = (255, 255, 255)
+
+clock = pygame.time.Clock()
+carImg = pygame.image.load("img/image.jpeg")
+crashed = False
+
+def car(x, y):
+    gameDisply.blit(carImg, (x, y))
+
+x = display_width * 0.45
+y = display_height * 0.8
+
+while not crashed:
+    for event in pygame.event.get():
+        if event.type == pygame.QUIT:
+            crashed = True
+    
+    gameDisply.fill(white)
+    car(x, y)
+
+    pygame.display.update()
+    clock.tick(60)
+
+pygame.quit()
+quit()

2. Moving an image in python.py

@@ -0,0 +1,51 @@
+import pygame
+
+pygame.init()
+
+display_width = 800
+disply_height = 600
+
+gameDisplay = pygame.display.set_mode((display_width, disply_height))
+pygame.display.set_caption("moving an image in python")
+
+black = (0, 0, 0)
+white = (255, 255, 255)
+
+clock = pygame.time.Clock()
+crashed = False
+carImg = pygame.image.load("img/image.jpeg")
+
+# add image in game
+def car(x, y):
+    gameDisplay.blit(carImg, (x, y))
+
+x = display_width * 0.50
+y = disply_height * 0.20
+
+x_change = 0
+car_speed = 0
+
+while not crashed:
+    for event in pygame.event.get():
+        if event.type == pygame.QUIT:
+            crashed = True
+
+        if event.type == pygame.KEYDOWN:
+            if event.key == pygame.K_LEFT:
+                x_change = -5
+            elif event.key == pygame.K_RIGHT:
+                x_change = 5
+        if event.type == pygame.KEYUP:
+            if event.key == pygame.K_LEFT or event.key== pygame.K_RIGHT:
+                x_change = 0
+    ##
+    x += x_change
+
+    gameDisplay.fill(white)
+    car(x,y)
+
+    pygame.display.update()
+    clock.tick(60)
+
+pygame.quit()
+quit()

CONTRIBUTING.MD

@@ -0,0 +1,92 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. 
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a 
+   build.
+2. Update the README.md with details of changes to the interface, this includes new environment 
+   variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this
+   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 
+   do not have permission to do that, you may request the second reviewer to merge it for you.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

Pipfile

@@ -0,0 +1,12 @@
+[[source]]
+name = "pypi"
+url = "https://pypi.org/simple"
+verify_ssl = true
+
+[dev-packages]
+
+[packages]
+pygame = "*"
+
+[requires]
+python_version = "3.7"

Pipfile.lock

@@ -1,2 +1,34 @@
-# PyGame-Tutorial
-PyGame Tutorial in Python3
+# Pygame Tutorial
+
+> Pygame is python framework for deveopment games in python.
+
+<img src="./img/pygame_logo.gif" alt="pygame snake">
+
+## How to Contribute
+
+- Fork the project repository
+
+ > Find the project's repository on GitHub, and then "fork" it by clicking the Fork button in the upper right corner:
+
+- Clone your Fork
+ 
+ > Using Git on your local machine, clone your fork using the URL you just copied: git clone URL_OF_FORK.
+
+- Add the project repository as the "upstream" remote
+  > Add the project repository as the "upstream" remote using: git remote add upstream URL_OF_PROJECT.Before tryingto push first sync it with upstream repository.
+
+  - Upstream Repository - where you forked your project
+  - Origin Repository - Your forked project
+
+**Check Details workflow here before submitting - https://dataschool.io/how-to-contribute-on-github/
+
+## Contributors
+
+<!-- Don't change under this line -->
+<!-- If you contributed to project then add your github link and link to your image-->
+
+<table>
+    <td>
+        <tr><a href="https://github.com/aayushi-droid"><img src="https://avatars1.githubusercontent.com/u/59429424?s=460&u=9fe1f1e20bff25ba6f044990ceab7a5d5bc4d1d4&v=4" alt="aayushi-droid" style="height:80px;width :80px;border-radius:50%"></a></tr>
+    </td>
+</table>