Research of what it would take to store the playback data

[abelalmeida]

References user story #7

Tasks:

• [x] review Javascipt, CSS, HTML
• [x] Find out what is needed for the project to be able to record and store playback data

[abelalmeida]

1. I went over pretty decent portion of JavaScript from code academy for a good refresher: Codeworks - Intro to JavaScript

• JavaScript and data types
• Variables and operators
• Functions
• Scope
• Arrays
• Loops
• Objects
• Classes

2. I reviewed HTML and CSS-

• HTML text fundamentals

• CSS Styling the web

{t:360}

[abelalmeida]

2. The solution I found was using Screen capture API https://developer.mozilla.org/en-US/docs/Web/API/Screen_Capture_API, After looking at the documentation for an hour an half it was not too helpful. While looking for example I found a working one that I am now reviewing and going over a stand alone working solution. I would like to implement a similar feature in our project. {t:240}

[abelalmeida]

Looking for at what we can use when we create the path using path2D for using SVG playback. {t:180}

[abelalmeida]

I did some more digging into what we would need to use the existing paths created by path2D for SVG playback, I need to chat and discuss with my team about this. {t:240}

[abelalmeida]

Worked on implementing a map, for storing the cube id's with the points so we could later use them to redraw the paths. {t:150}

[RayEscBSU]

Worked with able and stockton {t:60)

[abelalmeida]

I am working on creating a prototype map structure that we are using for the implementation we are considering. {240}

[abelalmeida]

I spent some time looking at the logic that keeps updating the both cubes point arrays. I feel we need to remove what we have added and start in small steps and test along the way to get what we need in the map for each cube. I also trying to get my debugger to open in Firefox which I'll need Stockton's help on it this coming week {t: 240}