Now, API (Application Programming Interface) is a interface for between programs so that they can share data. This is really cool because the example given was that we could store photos on Flickr and then in our HTML for our web page we could write a line of code that can request the image or image set from Flickr. This I think is really nifty (a very technical term) as I don't need to store all my photos on my own server. API is all about accessing data in a functional way.
Another thing that I am looking forward to incorporating in my Project A is the use of
tag (division tag) to make my scripting a whole lot neater! So I can put this around content that I want to do stuff with later.
tags are styled with #ids or .classes. We then can assign our own tags in HTML rather than h1 or p and then we add style to these new tags using css.
Another enlightening fact we were told today is that we can actually have more than on CSS file. Admittedly this hadn't occurred to me in the slightest. #ids however can only have one meaning assigned. So we need to assign a class which can handle many.
Another cool trick was using the source file to get the extension to see the CSS file for the web page. so if we find anything that we like style wise we can check it out by adding the extension into the URL. Wolfenflickr I think is pretty cool, APIs could be used for all sorts of things. 'New ways of experiencing content" was the main idea that went with using APIs. Every Block is cool too however knowing about how many fire department dispatches their were between 1 and 4 baffles me at the moment. But who knows that might be something really important when collecting data about an American city (Everyblock not available anywhere else yet). But essentially it collects data from APIs about your local area and arranges them in a feed so you can see what is happening in your local area.
No comments:
Post a Comment