My differentiation topic involves deepening an understanding of Progressive Web Apps. I'm drawn to PWAs for a variety of reasons, chief among them being that they represent a sort of natural extension for projects that I've already established. The responsiveness is already in place, and many of the projects in question rely on initial caching of data from a 'foundational' fetch call on the loading of the homepage. Given that PWAs offer some offline functionality, I'm curious to see how well my applications will work in the situation where the initial data is retrieved but the online connection is then subsequently severed. As I see it, my Rancid Tomatilloes project (among others) is already structured as a proto-PWA. Other convenient factors involve the one-size-fits-all utility of progressive web applications as well as the experience of 'crossing-the-aisle' from prior work with React Native. Getting my hands dirty with both progressive web & native applications will contribute to a more nuanced juxtapos
- Colin Koga, Zac Isaacson, John Travers, Scott Ertmer, Austen Dunn
Goals and Expectations for the Project (You don't know the details of the project yet. But as you go into any project, how do YOU define success?)
- Colin Koga: learning new lang (native) and solid testing, and D3.
- Zac Isaacson: Learning django/ flask is a priority. New lang's and frameworks.
- John Travers: Getting more comforatble with python, new frameworks and langs
- Scott Ertmer: React native, working with D3 for some visual magick
- Austen Dunn: React native & D3
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
- The paired project is due next Thursday. We want to have the majority of it completed by next Monday so that we can have ample time to work with mentors well before the deadline.
- We expect to meet at least twice a week to work together and to set schedules for individual work during these times.
On a website, what is the purpose of HTML code?
- Hypertext markup language is used to establish the scaffolding of the webpage, the skeletal elements that structure and format the foundations of our content so that it may be read as intended by the creator. HTML code allows us to fundamentally portray our page contents in formatted fashion rather than as a messy block - which was historically an obstacle in the sharing of documents via the internet. To summarize, HTML allows us to instruct browsers on how to appropriately display our page contents.
What is the difference between an element and a tag?
- They are interchangeable terms for the most part. To be more specific, tags represent the specific text or prompts contained within the <> that we use while using HTML. Elements include the tag (typically both an opening and closing tag) and all content encapsulated within it. So an element is basically the entire apparatus involved within specific tag "containers".
This file contains hidden or 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
Object: Ford Raptor | |
Attributes: | |
power_type "gas" | |
color "blue" | |
number_of_seats 5 | |
gear_shift "stick" | |
dirty (true) | |
Methods: |
This file contains hidden or 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
Class: Vehicle | |
Attributes: | |
power_type "string" | |
color "string" | |
number_of_seats integer | |
gear_shift "string" | |
dirty (boolean) | |
Methods: |
This file contains hidden or 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
1 Make a fire | |
1.1 Prepare Materials | |
1.1.1 Collect wood | |
1.1.2 Shred wood into tinder and kindling | |
1.1.3 Test lighter | |
1.2 Prepare fire location | |
1.2.1 Pick a flat area and avoid surrounding plants | |
1.2.2 Build a firepit by placing rocks of a certain size in a ring formation | |
1.3 Build the fire | |
1.3.1 Stack in a lincoln log cabin format with an easily accessible heart of kindling |
The assignments listed here should take you between 1.5 and 2 total hours.
To start this assignment:
- Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
- Click the Edit button when you're ready to start adding your answers.
- To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.