On the first floor, there is a common space area that can be shared with all art/IMM students. When you first enter the space, you come into the small kitchen area. Accessorized with a fridge, microwave, and a table with no seats that are high enough for it.
But when you walk past this little kitchenette area, you come into one of the sleeping oasis-es in this building. The art lounge has chairs, tables, and even better a couch. All of these pieces of furniture can be used for your napping pleasures. Had an all nighter and have a few minutes to snooze? This is the place to be. Too tired to walk over to your dorm? Take a quick nap, no one will disturb you.
After all, every college student needs a good nap.
Everyone has a nap spot in AIMM. This hallway is a lesser-known spot because it experiences high traffic during the day due to its proximity to some classrooms and The Cage. However, on weekends and nights, this hallway provides a dim, quiet, private place to snooze. Grab your giant hoodie and pick a corner! It’s all yours!
Welcome to the World of Animation! You enter the portal to this land by simply walking into the room! These locations are the key portals for animation where animation students work, thrive, and create… and occasionally cry because animation is hard.
Upon entering the doors of Room 222, Visitors are transported to the land of Butterflies named after Erin’s Kraemer’s lovely animation project. The Land of Butterflies is an animated world where fun critters are born. We see them fly through the sky, around trees, and through animated grass blades made out of fur.
Find the next Portal (The Globe Theater) in Room 202.
Find a time between classes and 206 can be transformed into a wonderful sleep world. Many scholars have rested their heads here, and you can join them. Outfitted with plush bean bags and a comfy red couch, anyone can relax and take a nap here. If you’re not careful, you just may sleep through your next class.
IMM and Computer Science students can develop and create projects in this fun and inviting space.
Wanna take a break? Take a load off on one of the bean bag chairs and grab a controller to any of the consoles the U Lab provides including the current generation xBox One to Wii.
Most web applications are built in a three-tiered architecture:
APIs are basically three-tiered web applications without the presentation layer. You access the data using a URL over HTTP, like a web page, but all you get back is data.
Why is this important? Because you can create different & separate presentation layers for different devices and situations. It also allows you to mashup data from different sources and wrap it in entirely new interfaces.
example:
One of the great things about Timeline.js is that it’s both a content visualization app (application + presentation layer) and a content database (data layer). As such it gives us a complete content management solution that relatively non-technical people can use to update the presentation layer without having to know how to code.
Let’s take a few minutes to catch up on some of your Design Notebooks
According to Wikipedia:
“The Internet of Things (IoT) refers to uniquely identifiable objects and their virtual representations in an internet-like structure.”
The idea is that objects can be directly connected to the internet, transmitting or receiving data, or be tagged in such a way to have digital representations of the objects be accessible over the internet. And, increasingly, much of that IoT traffic is M2M.
http://www.youtube.com/watch?v=LVlT4sX6uVs
History – http://postscapes.com/internet-of-things-history
More info on IoT – http://postscapes.com/internet-of-things-resources/
How do we connect everyday objects to the internet?
examples:
The Internet of Things is about sensors and networks
The Internet is the network of networks
examples:
Let’s take a few minutes to review some of your Design Notebooks from last week.
“Forget about the mobile internet…” ( social grade refs )
Which device to design for? Depends on user context; What are they doing? Why are they accessing (or contributing) content? Where are they?
Designing for read-only content on multiple device forms? Consider HTML5/responsive web design.
Designing for data collection? Consider the type of data:
For more info on cell phone sensors and how they work, check out Sensors and Cellphones
Native or Code Generated?
Native apps are typically coded using Java (Android) or Swift/Objective-C (iOS).
Code-generated apps are built using standard web technologies like HTML, CSS and Javascript, and then run through a processor application to convert the input files into native code.
This week’s homework assignment is due next week before class. When you’ve completed them, post a comment on this page (First Day of Class), including a link to your Design Notebook.
Let’s take a couple of minutes to review some of your Design Notebooks.
Open Content
Open Apps
API stands for “Application Programming Interface”.
The Data Layer
Collection Database Resources – This is your database of collection records, could be in a database management system like MySQL, or even in flat files like CSV or Excel.
The Application Layer
Application Programming Interface – A middleware application in a server-side language like PHP, Ruby, Python or Server Side Javascript (Node.js) that responds to user requests by querying the database and returning the results of the requested action. There are some decent lightweight frameworks available that simplify creating RESTful APIs.
REST (Representational State Transfer) APIs work like web pages, but for machines. You build URL strings to tell the API which resource you want, and make a single request for that resource.
The Presentation Layer
When designing a RESTful API, use nouns to to identify resources. Limit your base URLS to two; one for collections, and one for specific items within a collection.
Examples: /collections - retrieve a listing of all collections /collections/12345 - retrieve info for a specific collection
You can then nest resources to reflect associations between resources.
Examples: /collections/12345/items - retrieve the collection of all items in a specific container /collections/12345/items/54321 - retrieve a specific item in a specific container
To perform actions, use the following HTTP methods when making your REST requests:
Pragmatically speaking, you’ll often find POST being used in lieu of PUT and DELETE to edit and delete resources.
*Want to design a RESTful api for your collection data? Check out the Apigee Web API Design book!
This week’s homework assignment is due next week before class. When you’ve completed them, post a comment on this page (First Day of Class), including a link to your Design Notebook.
