Wendy.Foster - Revision history

Wendy.Foster at 09:55, 18 November 2008

2008-11-18T09:55:05Z

Wendy.Foster at 09:48, 18 November 2008

2008-11-18T09:48:18Z

Wendy.Foster at 09:44, 18 November 2008

2008-11-18T09:44:33Z

Wendy.Foster at 09:42, 18 November 2008

2008-11-18T09:42:17Z

Wendy.Foster at 09:40, 18 November 2008

2008-11-18T09:40:52Z

Wendy.Foster at 09:30, 18 November 2008

2008-11-18T09:30:08Z

Wendy.Foster at 09:27, 18 November 2008

2008-11-18T09:27:03Z

Wendy.Foster at 09:26, 18 November 2008

2008-11-18T09:26:41Z

Wendy.Foster at 03:38, 6 October 2008

2008-10-06T03:38:33Z

Wendy.Foster at 03:27, 6 October 2008

2008-10-06T03:27:55Z

← Older revision		Revision as of 09:55, 18 November 2008
Line 1:		Line 1:
−	==Final Project :: Part 1==	+	==Final Project (Project 3) :: Part 1==

	===Description===		===Description===

@@ Line 28: / Line 28: @@
 #*optimize code for baseline functionality
 #*implement gui widgets for user-defined elements: includes determination of which game aspects will be controlled through widgets and how to place widgets in relation to primary game space
 #'''Incorporate gameplay enhancements into core build'''
 #*implement scoring system into gameplay
 #*determine differential effects for base elements to be linked to advances in gameplay
 #*create and implement bonus items into gameplay
 #'''Incorporate advanced functionality into application'''
 #*attempt wiimote controller implementation
 #*allow for user customization of the environment through gui controls (ability to modify, perhaps, background scenes, paddle appearance, etc.)
 #'''Ports'''
 #*play with opportunities for mobile implementations through Mobile Processing and Java Sun Wireless Toolkit (formerly J2ME)

@@ Line 20: / Line 20: @@
 ====Libraries:====
-<pre>controlP5 gui elements (to provide user configuration options); oscP5 open sound control network protocol (to base facilitate wiimote connection); darwinosc extension for osc (darwinremote application for osx to support wiimote); and ezGestures gesture recognition library (to analyze Wiimote movements)</pre>
+controlP5 gui elements (to provide user configuration options); oscP5 open sound control network protocol (to base facilitate wiimote connection); darwinosc extension for osc (darwinremote application for osx to support wiimote); and ezGestures gesture recognition library (to analyze Wiimote movements)
 ===Plan Framework:===
 #'''Build core functionality'''
-**implement minimum functionality (baseline gameplay elements)
+#*implement minimum functionality (baseline gameplay elements)
-**optimize code for baseline functionality
+#*optimize code for baseline functionality
-**implement gui widgets for user-defined elements: includes determination of which game aspects will be controlled through widgets and how to place widgets in relation to primary game space
+#*implement gui widgets for user-defined elements: includes determination of which game aspects will be controlled through widgets and how to place widgets in relation to primary game space
 #'''Incorporate gameplay enhancements into core build'''
-**implement scoring system into gameplay
+#*implement scoring system into gameplay
-**determine differential effects for base elements to be linked to advances in gameplay
+#*determine differential effects for base elements to be linked to advances in gameplay
-**create and implement bonus items into gameplay
+#*create and implement bonus items into gameplay
 #'''Incorporate advanced functionality into application'''
-**attempt wiimote controller implementation
+#*attempt wiimote controller implementation
-**allow for user customization of the environment through gui controls (ability to modify, perhaps, background scenes, paddle appearance, etc.)
+#*allow for user customization of the environment through gui controls (ability to modify, perhaps, background scenes, paddle appearance, etc.)
-−
+#
 #'''Ports'''
-**play with opportunities for mobile implementations through Mobile Processing and Java Sun Wireless Toolkit (formerly J2ME)
+#*play with opportunities for mobile implementations through Mobile Processing and Java Sun Wireless Toolkit (formerly J2ME)
-**investigate alcheMo for iPhone which automates J2ME to iPhone porting
+#*investigate alcheMo for iPhone which automates J2ME to iPhone porting
-**start playing with the iPhone SDK to determine level of difficulty in becoming fluent enough with Objective-C that a port is possible in the future by re-writing the application instead of translating the code through alcheMo
+#*start playing with the iPhone SDK to determine level of difficulty in becoming fluent enough with Objective-C that a port is possible in the future by re-writing the application instead of translating the code through alcheMo
 <hr />

@@ Line 20: / Line 20: @@
 ====Libraries:====
- controlP5 gui elements (to provide user configuration options); oscP5 open sound control network protocol (to base facilitate wiimote connection); darwinosc extension for osc (darwinremote application for osx to support wiimote); and ezGestures gesture recognition library (to analyze Wiimote movements)
+<pre>controlP5 gui elements (to provide user configuration options); oscP5 open sound control network protocol (to base facilitate wiimote connection); darwinosc extension for osc (darwinremote application for osx to support wiimote); and ezGestures gesture recognition library (to analyze Wiimote movements)</pre>
 ===Plan Framework:===

← Older revision		Revision as of 09:40, 18 November 2008
Line 1:		Line 1:
−	~~[toc]~~	+	==Final Project :: Part 1==
		+
		+	===Description===
		+
		+	====Title: Breakout 2.0====
		+
		+	====Overview:====
		+
		+
		+	This Processing project will operate as a functional prototype for further development and extension to mobile platforms. The Processing Breakout game produced for this project will be the basis for ports into Mobile Processing and Objective C, using the iPhone SDK, for iPhone implementation. I am particularly interested in exploring the multi-touch and accelerometer affordances for gameplay that can be accessed through the iPhone for a Breakout clone.
		+
		+	I am comforted by the knowledge that Jobs and Wozniak created the original Breakout coding in 4 days (although legend has it that Jobs downloaded all the work onto Wozniak who went without sleep for those four days in order to complete the project). Sadly, the Jobs and Wozniak version never made it to implementation on the Atari system. Wozniak claims that evil Atari engineers broke his code; however, their industriousness will operate as my motivation to create a version, that, at the very least, will have a ball, a paddle, and some bricks that will, in some fashion, respond to each other.
		+
		+	====Key Functionality:====
		+
		+
		+
		+
		+
		+
		+	====Libraries:====
		+	controlP5 gui elements (to provide user configuration options); oscP5 open sound control network protocol (to base facilitate wiimote connection); darwinosc extension for osc (darwinremote application for osx to support wiimote); and ezGestures gesture recognition library (to analyze Wiimote movements)
		+
		+	===Plan Framework:===
		+
		+	#'''Build core functionality'''
		+	**implement minimum functionality (baseline gameplay elements)
		+	**optimize code for baseline functionality
		+	**implement gui widgets for user-defined elements: includes determination of which game aspects will be controlled through widgets and how to place widgets in relation to primary game space
		+
		+	#'''Incorporate gameplay enhancements into core build'''
		+	**implement scoring system into gameplay
		+	**determine differential effects for base elements to be linked to advances in gameplay
		+	**create and implement bonus items into gameplay
		+
		+	#'''Incorporate advanced functionality into application'''
		+	**attempt wiimote controller implementation
		+	**allow for user customization of the environment through gui controls (ability to modify, perhaps, background scenes, paddle appearance, etc.)
		+
		+
		+	#'''Ports'''
		+	**play with opportunities for mobile implementations through Mobile Processing and Java Sun Wireless Toolkit (formerly J2ME)
		+	**investigate alcheMo for iPhone which automates J2ME to iPhone porting
		+	**start playing with the iPhone SDK to determine level of difficulty in becoming fluent enough with Objective-C that a port is possible in the future by re-writing the application instead of translating the code through alcheMo
		+
		+	<hr />

	==Project 2: Part I :: Editor Proposal==		==Project 2: Part I :: Editor Proposal==

@@ Line 1: / Line 1: @@
 [toc]
-'''Project 2: Part I :: Editor Proposal'''
+==Project 2: Part I :: Editor Proposal==
-'''Tmesis via Editrix v.0'''
+===Tmesis via Editrix v.0'===
 '''Drawing Tool Proposal : IAT 800'''
 '''Wendy Foster'''

← Older revision		Revision as of 09:27, 18 November 2008
Line 1:		Line 1:
−	[[toc]]	+	[toc]

	'''Project 2: Part I :: Editor Proposal'''		'''Project 2: Part I :: Editor Proposal'''

← Older revision		Revision as of 09:26, 18 November 2008
Line 1:		Line 1:
		+	[[toc]]
		+
	'''Project 2: Part I :: Editor Proposal'''		'''Project 2: Part I :: Editor Proposal'''

@@ Line 7: / Line 7: @@
 ----
-[T]mesis is a seam or flaw resulting from a simple principle of functionality; it does not occur at the level of the structure of languages but only at the moment of their consumption; the author cannot predict tmesis:  he cannot choose to write what will be read.
+[T]mesis is a seam or flaw resulting from a simple principle of functionality; it does not occur at the level of the structure of languages but only at the moment of their consumption; the author cannot predict tmesis:  he cannot choose to write ''what will be read''.
 (Roland Barthes ''from'' The Pleasure of the Text (1973). A Critical and Cultural Theory Reader.  Ed. Antony Easthope, et al.  Toronto: U of Toronto P., 1992. 108-109.