Skip to content

oplS17projects/redesigned-doodle

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

28 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Redesigned-Doodle

Scott Quinn and Harsh Patel

Redesigned-Doodle

Statement

We replicated the examples given inside the turtle-examples library. We prompt the user to choose what they want and with the press of a button creates the example and they can choose if they would like to save it as a file. It is interesting because it would give a deeper understanding of the turtles and GUI library. Personally I find it interesting because I enjoyed playing around with the library. I hope to learn how this library works.

Analysis

Explain what approaches from class you will bring to bear on the project.

Be explicit about the techiques from the class that you will use. For example:

Replicating the Sierpinski triangle function and Koch snowflake function both use recursive calls.

Deliverable and Demonstration

At the end of the project sequence we are able to do all that the examples libary does and more. Our project is just a series of functions that should be able to be run from any instance of racket. It will be interactive by typing having the user press buttons to select what they want to be drawn.

Evaluation of Results

If it actually draws things onto the screen we would consider it to be sucessful.

Architecture Diagram

ADF

The user interacts with the help of the GUI library. The GUI library is the intermediate between the user and the turtles library. The diagram splits the basic functions of the turtle library into 2 general categories: Moving the turtle and manipulating the turtle. Moving does just that. It moves the turtle. There it draws, erases, and turns the turtle. This also includes the offset type for each type of function. The other part is manipulation. This is used to indirectly influence the image being drawn such as creating multiple turtles.

Schedule

We would go step by step through the examples and when they are operating successfully we would continue to the next. Repeat until done. There are three deliverable milestones to explicitly define, below.

The nature of deliverables depend on your project, but may include things like processed data ready for import, core algorithms implemented, interface design prototyped, etc.

You will be expected to turn in code, documentation, and data (as appropriate) at each of these stages.

Write concrete steps for your schedule to move from concept to working system.

First Milestone (Sun Apr 9)

Which portion of the work will be completed (and committed to Github) by this day? -We did the first 6 examples (until gapped-lines) -We should also be done with the user interface.

Second Milestone (Sun Apr 16)

Which portion of the work will be completed (and committed to Github) by this day? We found out how to actually use the turtle-examples library. We did some minor edits to farious functions so that they could run properly.

Public Presentation (Mon Apr 24, Wed Apr 26, or Fri Apr 28 [your date to be determined later])

What additionally will be completed before the public presentation? -We got the library working. Some of the examples did not work. We fixed regular-polys (the second number didn't do anything), and lorenz( the turtle wouldn't animate). We also added a basic function called fract that randomly draws fractured lines.

Group Responsibilities

Here each group member gets a section where they, as an individual, detail what they are responsible for in this project. Each group member writes their own Responsibility section. Include the milestones and final deliverable.

Please use Github properly: each individual must make the edits to this file representing their own section of work.

Harsh Patel @hpatel28

I couldn't get the interface working.

Scott Quinn @Scott-Quinn

Scott is team lead. Additionally, Scott will work on replicating the turtle examples.

About

harsh patel and scott quinn

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages