Remarks: Processing Mazes

Revision as of 14:32, 21 May 2011 (view source)

MarkSample (Talk | contribs)

← Older edit

Revision as of 18:18, 27 May 2011 (view source)

CaseyReas (Talk | contribs)

(Moved comments, extended by a few sentences)

Newer edit →

Line 1:

−

[This section is about porting the 10 Print program to a current programming software/hardware environment. What does it mean to take the algorithm out of the C64 and to generalize it for a modern processor and display? This section will be heavily illustrated. Feedback is of course very welcome. -- Casey]

+

[Comments/context moved to the Discussion]

−

The algorithm that defines the 10 PRINT maze exists independently from the Commodore 64 (C64) platform. In fact, the algorithm can be simply executed with a sheet of graph paper, a pen, and a coin to toss. The act of running the algorithm on a number of different platforms reveals what is essential to the algorithm from the specific constraints and affordances of the C64.

+

The algorithm that defines the 10 PRINT maze exists independently from the Commodore 64 (C64) platform. In fact, the algorithm can be simply executed with a sheet of graph paper, a pen, and a coin to toss. The act of running the algorithm on a number of different platforms reveals what is essential to the algorithm from the specific constraints and affordances of the C64. The concision of 10 PRINT originates from its clever exploitation of the C64, as explained in section ??. For example, the code need not tell the lines to wrap to the next line when they the edge of the screen because that is built into the system; lines don't need explicit x- and y-coordinates because characters 205 and 206 define them. When 10 PRINT is ported to other platform, as demonstrated in section ??, these features of the C64 need to be defined within the new platform.

−

[I like this idea of separating the algorithm from the platform. Very similar to your Processing version of 10 PRINT, I think this thought/practical experiment can help us figure out what's unique about the C64 version, versus, say, a manual coin-toss version or a processing version. I think I ran through some of these differences in an email last summer: the speed and color of the maze stood out as two defining aesthetic features of the C64 version. I just put some of those notes on the [http://weizenbaum.mit.edu/mediawiki/index.php/Talk:Remarks:_Processing_Mazes Discussion Page] -- Mark S.]

+

When the C64 was released, it was a powerful system for creating computers graphics. In the thirty years since the introduction of the C64, computers have changed substantially and contemporary hardware is an exciting place to re-imagine the 10 PRINT algorithm. For this exploration, we're using Processing, a programming system first designed in 2001. It's built on top of Java, a dominant language

−

In the thirty years since the introduction of the C64, computers have changed substantially and contemporary hardware is an exciting place to re-imagine the 10 PRINT algorithm.

Remarks: Processing Mazes

From Maze

Revision as of 18:18, 27 May 2011

Views

Personal tools

Navigation

Search

Toolbox

@@ Line 1: / Line 1: @@
-[This section is about porting the 10 Print program to a current programming software/hardware environment. What does it mean to take the algorithm out of the C64 and to generalize it for a modern processor and display? This section will be heavily illustrated. Feedback is of course very welcome. -- Casey]
+[Comments/context moved to the Discussion]
-The algorithm that defines the 10 PRINT maze exists independently from the Commodore 64 (C64) platform. In fact, the algorithm can be simply executed with a sheet of graph paper, a pen, and a coin to toss. The act of running the algorithm on a number of different platforms reveals what is essential to the algorithm from the specific constraints and affordances of the C64.
+The algorithm that defines the 10 PRINT maze exists independently from the Commodore 64 (C64) platform. In fact, the algorithm can be simply executed with a sheet of graph paper, a pen, and a coin to toss. The act of running the algorithm on a number of different platforms reveals what is essential to the algorithm from the specific constraints and affordances of the C64. The concision of 10 PRINT originates from its clever exploitation of the C64, as explained in section ??. For example, the code need not tell the lines to wrap to the next line when they the edge of the screen because that is built into the system; lines don't need explicit x- and y-coordinates because characters 205 and 206 define them. When 10 PRINT is ported to other platform, as demonstrated in section ??, these features of the C64 need to be defined within the new platform.
-[I like this idea of separating the algorithm from the platform. Very similar to your Processing version of 10 PRINT, I think this thought/practical experiment can help us figure out what's unique about the C64 version, versus, say, a manual coin-toss version or a processing version. I think I ran through some of these differences in an email last summer: the speed and color of the maze stood out as two defining aesthetic features of the C64 version. I just put some of those notes on the [http://weizenbaum.mit.edu/mediawiki/index.php/Talk:Remarks:_Processing_Mazes Discussion Page] -- Mark S.]
+When the C64 was released, it was a powerful system for creating computers graphics. In the thirty years since the introduction of the C64, computers have changed substantially and contemporary hardware is an exciting place to re-imagine the 10 PRINT algorithm. For this exploration, we're using Processing, a programming system first designed in 2001. It's built on top of Java, a dominant language
-In the thirty years since the introduction of the C64, computers have changed substantially and contemporary hardware is an exciting place to re-imagine the 10 PRINT algorithm.