|
|
| (509 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| <p style="color:#FFFF00; font-size: 45pt; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1"> | | <p style="color:#FFFF00; font-size: 52pt; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">'''o h j i a n'''</p> |
|
| |
|
| | <div style=" |
| | font-family: courier new; |
| | font-size: 14px; |
| | color:#bbbbbb |
| | text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1 |
| | "> |
|
| |
|
| '''o h j i a n'''
| |
|
| |
|
| =<p style="color:# FFB6C1; text- shadow: 2px 2px 4px #0000FF, 2px 2px 4px #0000FF">INDEX</p>= | | <p style="color:#FFFF00; font-size: 45pt; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1"> |
| | | [[User:Ohjian/Final_presentation|Grad Project]]<br> |
| * oh
| | [[User:Ohjian/Project-Proposal|Project Proposal]]<br> |
| * hi
| | [[User:Ohjian/Thesis-Outline|Thesis Outline]]<br><br> |
| * [[hello]]
| | [[User:Ohjian/XPUB_1|YEAR 1]]<br> |
| | | [[User:Ohjian/XPUB_2|BRIDGE]] |
| =<p style="color:#FFB6C1; text-shadow: 2px 2px 4px #0000FF, 2px 2px 4px #0000FF">Special Issue #16</p>=
| |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Getting Started</p>==
| |
| | |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Readings</p>==
| |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">References</p>==
| |
| | |
| * "A Rose is a Rose is a rose", Gertrude Stein
| |
| * Oulipu
| |
| * George perec
| |
| * "Sprache und sein", Kübra Gümüşay
| |
| * "Dictionary of Winds", Ivetta Gerasimchuk
| |
| | |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Words of interest</p>==
| |
| | |
| * Archive
| |
| * Atlas
| |
| * Book
| |
| * Context
| |
| * Darkness
| |
| * Destination
| |
| * Direction
| |
| * Encyclopedia
| |
| * Index
| |
| * Interrelations
| |
| * Language
| |
| * Lexikon
| |
| * Local
| |
| * Lacolization
| |
| * Map
| |
| * Mobility
| |
| * Movements
| |
| * Multiverse
| |
| * Multilayers
| |
| * Navigation
| |
| * Navigator
| |
| * Orientation
| |
| * Question Mark
| |
| * Rejection
| |
| * Relation
| |
| * Space
| |
| * Territory
| |
| * Toolkit
| |
| * Weaving
| |
| | |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Notes</p>==
| |
| | |
| ===Readings for Prototyping class===
| |
| | |
| [[Prototyping/2021-2022/T1]] | |
| | |
| ====Exploratory Programming for the Arts and Humanities by Nick Montfort====
| |
| | |
| | |
| =====[ 4 ] Calculating and Using Jupiter Notebook=====
| |
| | |
| ''calculator (to calculate) / computer (to compute) / ordinateur (French, to order, to organize)''
| |
| | |
| Python is a programming language
| |
| | |
| Jupiter Notebook is an interpreter of Python
| |
| | |
| Syntax vs. Semantics in programming languages like Python or Processing:
| |
| | |
| * If the Syntax is correct, the code is formally correct, it is valid.
| |
| * If the code does what it is supposed to do, it is intentional.
| |
| * Intentional programs are always valid.
| |
| * Valid programs are not always intentional.
| |
| | |
| Syntax and Semantics in HTML (Hypertext Markup Language):
| |
| | |
| * HTML is not a programming language
| |
| * JavaScript is a program
| |
| * HMTL does not encode instructions
| |
| * Web Browser are forgiving and will also render invalid pages whenever possible. Just because a page is looks intentional in a web browser it doesn't mean it's valid code. So maybe other or future web browsers will struggle to show the intended page. Use Validators like validator.w3c.org to make sure your code is valid.
| |
| | |
| ! Dont ever replace the content of a a cell in Python once it has successfully run, even if the outcome is not intentional. Instead copy to a new cell to change the content !
| |
| | |
| | |
| =====[ 5 ] Double, Double=====
| |
| | |
| Indentation is important! Use 4 spaces instead of a tab!
| |
| | |
| * Function: a bundle of computation 7 it must be provided exactly one argument / a function accepts arguments as well as returns values
| |
| * Interface: Schnittstelle / the specific way in which a function accepts an argument and returns values defines the interface to a function
| |
| * Argument: Ausgangswert? / Information that is passed into a function / The arguments to the function hold the values that the function needs to do its work. It sends back the answer aas return value
| |
| * Value: Ergebnis / Result that is returned by the function
| |
| * Sequence: data that is given as an argument
| |
| * Element: a sequence can have several elements, a list [element, element, element]
| |
| | |
| | |
| =====[ 6 ] Programming Fundamentals=====
| |
| | |
| Types of Abstraction:
| |
| * iteration = generalize a computation over a sequence / looping / allows repeated computation
| |
| * polymorphism = a code that applies to data of different types
| |
| | |
| there are different types of data, for example:
| |
| * integral numbers = int
| |
| * strings of characters = str
| |
| * lists of integers = int
| |
| * Boolean value = True/False
| |
| | |
| some functions or operator only work with certain types of data, other are polymorph and work with different types of data
| |
| | |
| types of data can be converted = casting
| |
| | |
| inner and outer universe / scope: variable have a certain value in a function, but outside of the function the same variable can have a different value
| |
| | |
| | |
| ===Reflection moment===
| |
| | |
| I was re-reading what we have to prepare for Christinas class and realized I misunderstood it the first time. I guess we are not supposed to bring even more new texts/material to elaborate, but rather bring examples of processing methods. So as far as I understand we should focus on different ways to approach a text or material, how to process/play/manipulate/work with it …
| |
| | |
| I think I will try to come up with maybe 3 different processing methods and use any text or material (old or new) to exemplify these methods. A method could be a complex annotation system but also a super simple and playful manipulation (i.e. get rid of all the punctuation in a text and see what happens).
| |
| | |
| What do you think? Should we just play around with this and then present our favorites in class?
| |
| | |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Experiments</p>==
| |
|
| |
|
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Annotation Compass</p>==
| | </p> |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Rejection Map</p>==
| | <br><br> |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">What the book is</p>==
| |
| ==<p style="color:#d3d3d3; text-shadow: 10px 10px 18px #FFB6C1, 10px 10px 18px #FFB6C1">Cocktail Generator</p>==
| |
|
| |
|
| =<p style="color:#FFB6C1; text-shadow: 2px 2px 4px #0000FF, 2px 2px 4px #0000FF">Special Issue #17</p>=
| | </div> |
| =<p style="color:#FFB6C1; text-shadow: 2px 2px 4px #0000FF, 2px 2px 4px #0000FF">Special Issue #18</p>=
| |
