-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex_old.html
More file actions
157 lines (132 loc) · 8.44 KB
/
Copy pathindex_old.html
File metadata and controls
157 lines (132 loc) · 8.44 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta name="description" content="">
<meta name="author" content="Mark Otto, Jacob Thornton, and Bootstrap contributors">
<meta name="generator" content="Jekyll v3.8.5">
<title>CSVAD MAT 594X | CMPSC 291I </title>
<link rel="shortcut icon" href="images/favicon.ico">
<!-- Bootstrap core CSS -->
<link href="css/bootstrap.min.css" rel="stylesheet">
<style>
.bd-placeholder-img {
font-size: 1.125rem;
text-anchor: middle;
-webkit-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
user-select: none;
}
@media (min-width: 768px) {
.bd-placeholder-img-lg {
font-size: 3.5rem;
}
}
</style>
<!-- Custom styles for this template -->
<link href="css/cover.css" rel="stylesheet">
</head>
<body>
<div class="cover-container d-flex w-100 h-100 p-3 mx-auto flex-column">
<header class="masthead mb-40">
<div class="inner">
<h3 class="masthead-brand">CSVAD</h3>
<nav class="nav nav-masthead justify-content-center">
<a class="nav-link active" href="index.html">Syllabus</a>
<a class="nav-link" href="#">Readings</a>
<a class="nav-link" href="code_of_conduct.html">Code of Conduct</a>
<a class="nav-link" href="#">Class Github</a>
<a class="nav-link" href="#">Resources</a>
</nav>
</div>
</header>
<main role="main" class="inner cover">
<h1 class="cover-heading">Computational Systems for Visual Art and Design</h1>
<p >Computational systems of rules, relationships, and behaviors can extend traditional art and design practices or support new creative workflows and outcomes. In this course, we will explore the creation of computational systems for visual art and design. Following a studio format, we will learn creative coding platforms and algorithms to create visual works that are flexible, dynamic, and generative. In the process, we will touch on the design philosophy and abstractions of existing creative coding platforms and examine methods to create alternatives. Students will learn basic approaches to modify creative programming languages and frameworks or develop new software interfaces for visual expression. Technical production will be complemented by readings on computational art and design theory and review of seminal works in computational art and design.</p>
<h3 class="cover-heading">Instructor Information</h3>
<ul class="list-unstyled">
<li> Jennifer Jacobs | jmjacobs (at) mat (dot) ucsb (dot) edu | Elings 2215 </br>(temporary office HFH 5102) </li>
<li> Office Hours: Wednesdays 13:00-15:00 <b>by appointment only</b></li>
</ul>
<!-- <h3 class="cover-heading">Introduction</h3>
<p><i>Art, in the only sense in which one can separate art from technics, is primarily the domain of the person; and the purpose of art, apart from various incidental technical functions that may be associated with it, is to widen the province of personality, so that feelings, emotions, attitudes, and values, in the special individualized form in which they happen in one particular person, in one particular culture, can be transmitted with all their force and meaning to other persons or to other cultures.</i>
</br> -Lewis Mumford, Art and Technics, 1952 </p>
<p>Whether as a tool or as a material, technology has almost always been present in human art and design. Computation in particular that has had a widespread impact on art and design. From their first application as tools for expression, computers significantly changed how we make art. Unlike previous technological tools, computers enabled the creation of works were not manually executed by human hands, nor explicitly conceived of by human minds. </p>
<p>Computers enable works of art and design to be expressed through code: a series of computational rules or relationships (or procedures) that can be compiled and executed by a computer. Coding allows artists to manage complex structures, automate processes, and generalize and reuse operations. When applied to visual expression, code enables the creation of visual media that is dynamic, responsive, interactive, and generative. Code also supports specific ways of thinking about the art and design process. Rather than produce discrete artifacts, creators can conceive of works as systems that contain numerous, or even infinite variations of an idea.</p>
<p>In addition to new opportunities, creating works of art and design with code poses new challenges. Artists and designers must frequently repurpose programming languages that were developed for other applications. Programming in general requires understanding abstract representations and working in a highly structured manner, which can conflict with the exploratory nature of many forms of art and design. Visual artists and designers are also drawn to visual tools and media but programming requires manipulating a representational description of the work. he culture surrounding computer programming can also impose limits and restrictions on who can participate, and which works are validated and which are not. </p>
<p>In this course, we will explore the opportunities and challenges of using code to create visual art and design. We will produce works of art and design with existing programming languages, and we will engage in the creation of new coding tools, interfaces, and abstractions. In the process, we will examine the history and theory of applying code to the production of aesthetic visual works.</p>-->
<h3> Weekly Structure </h3>
<h4>Tuesdays</h4>
<ul>
<li> Review last week's project</li>
<li> Introduce new topic area</li>
<li> Technical instruction and coding activity</li>
<li> Introduce reading assignment</li>
</ul>
<h4>Thursdays</h4>
<ul>
<li>Discuss reading</li>
<li>Instruction supplemental</li>
<li>Project assignment</li>
<li>In class working time/ peer and instructor support</li>
</ul>
<h3>Week One: Init</h3>
<a href="sep26.html"><h4>September 26</h4></a>
<p>Introduction to the course and syllabus, questions activity, introduction to Processing and Github.</p>
<h3>Week Two: Procedure and Repetition</h3>
<a href="#"><h4>October 1</h4></a>
<p>Discussion: Code as a medium for visual expression</br>
Practice: Writing basic algorithims for visual output.</p>
<p> <a href="#"><h4>October 3</h4></a>
<a> Discussion: Automation in art and design</br>
Practice: Loops to generate repeating form and pattern.</p>
<h3>Week Three: Parameterization</h3>
<a href="#"><h4>October 8</h4></a>
<p>Discussion: Capturing Design Intent</br>
Practice: Creating a design system with degrees of freedom and constraints. Exposing those parameters in a basic interface</p>
<p> <a href="#"><h4>October 10</h4></a>
<a> Discussion: Abstracting Design Patterns</br>
Practice: Creating variation through functions and classes</p>
<h3>Week Four: Generativity</h3>
<a href="#"><h4>October 15</h4></a>
<p>Discussion: Challenges and Opportunities of generative art</br>
Practice: Designing with noise and randomness</p>
<p> <a href="#"><h4>October 17</h4></a>
<a> Discussion: Challenges and Opportunities of generative art pt 2</br>
Practice: Using external data to drive design outcomes</p>
<h3>Week Five: Digital to Physical</h3>
<a href="#"><h4>October 22</h4></a>
<p>Discussion: Challenges and Opportunities of generative art</br>
Practice: Designing with noise and randomness</p>
<p> <a href="#"><h4>October 24</h4></a>
<a> Discussion: Understanding data-driven design</br>
Practice: Using external data to drive design outcomes</p>
<h3>Week Six:Abstraction</h3>
<a href="#"><h4>October 29</h4></a>
<a href="#"><h4>October 31</h4></a>
<h3>Week Seven:Dynamism/Interactivity</h3>
<a href="#"><h4>November 5</h4></a>
<a href="#"><h4>November 7</h4></a>
<h3>Week Eight: Interface</h3>
<a href="#"><h4>November 12</h4></a>
<a href="#"><h4>November 14</h4></a>
<h3>Week Nine</h3>
<a href="#"><h4>November 19</h4></a>
<a href="#"><h4>November 21</h4></a>
<h3>Thanksgiving Holiday<h3>
<h3>Week 10</h3>
<a href="#"><h4>December 2</h4></a>
<a href="#"><h4>December 5</h4></a>
<h3>Finals Week</h3>
Final Project Presentation and Critique
</main>
<footer class="mastfoot mt-auto">
<div class="inner">
<p>Cover template for <a href="https://getbootstrap.com/">Bootstrap</a>, by <a href="https://twitter.com/mdo">@mdo</a>.</p>
</div>
</footer>
</div>
</body>
</html>