![]() |
CiteULike | ![]() |
NewMediaReferences's CiteULike | ![]() |
![]() |
|
![]() |
Register | ![]() |
Log in | ![]() |
Whitney Artport Commissions: CODeDOCby: Commissioned
|
Reviews
[Write a review of this article]
Find related articles from these CiteULike users
Find related articles with these CiteULike tags
Posting History
Abstract"The Codedoc project: CODeDOC takes a reverse look at 'software art' projects by focusing on and comparing the 'back end' of the code that drives the artwork's 'front end'--the result of the code, be it visuals or a more abstract communication process. A dozen artists coded a specific assignment in a language of their choice and were asked to exchange the code with each other for comments. The assignment was to 'connect and move three points in space,' which obviously could be interpreted in a literal or abstract way. The 'core' of the code (commonly referred to as the 'main') was not to exceed 8KB, which equals a fairly short text document. The results of the programming are made visible only after the code--what visitors to this site encounter first is a text document of code from which they can launch the front end of the project. The languages in which the code is written are Java, C, Visual Basic, Lingo and Perl. Obviously, this is only a selection of scripting and programming languages. HTML (Hypertext Markup Language), the scripting language on which the World Wide Web is based, and Flash Script were excluded mostly for pragmatic reasons (the inclusion of these languages probably would have doubled the number of artists, making the project unwieldy). Not all of the artists originally invited were able to participate in CODeDOC due to their busy schedules."
BibTeX record
RIS record