meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
android2010:grp15:start [2010/03/19 09:31]
were 		android2010:grp15:start [2010/03/19 13:34] (current)
were
Line 1: Line 1:
 ====== ArmyWorms ====== ====== ArmyWorms ======
-group 15 -- +{{:android2010:grp15:fighters.png?100}}  
-Bishal Raj Karki +{{ :android:android_logo_trans_small.png?100}} 
-Jifeng Xing +  
-Were Oyomno+==group 15== 
 +**Bishal Raj Karki - b0331930** 
 +\\ 
 +**Jifeng Xing - 0316191** 
 +\\ 
 +**Were Oyomno - 0315972** 
  
 ===== Idea ===== ===== Idea =====
Line 42: Line 48:
 ===== Screenshots ===== ===== Screenshots =====
  
-{{:android2010:grp15:snap.jpg?300x300|ArmyWorms mock design }}  +{{:android2010:grp15:snap.jpg?300x300 }}  
- +{{:android2010:grp15:01.png?300x300 }}  
 +{{:android2010:grp15:02.png?300x300 }}  
 +{{:android2010:grp15:03.png?300x300 }}  
 +{{:android2010:grp15:04.png?300x300}} 
  
 ===== Implementation Comments ===== ===== Implementation Comments =====
 We intend to focus on the following aspects: We intend to focus on the following aspects:
-  * Single player in one device - This was completed relatively fast and efficiently. The overall feel for Android as a programming language is that it takes time to get comfortable with and soon grows on you.  The traditional concept of //public static void main()// absence took a while to get used to. Also their frequent use of thread was seen as relative untidy but after understanding it a little it was seen a  cleave way to do things. +  * **Single player in one device** - This was completed relatively fast and efficiently. The overall feel for Android as a programming language is that it takes time to get comfortable with and soon grows on you.  The traditional concept of **//public static void main()//** absence took a while to get used to. Also their frequent use of thread was seen as relative untidy but after understanding it a little it was seen a  cleave way to do things. 
-  * Score keeping / winner deciding - This section is complete and was not too tough to sort out the biggest headache in this region was simulating the fluid firing motion. +\\ 
-  * Multi-player in multiple devices - This definitely sucks i.e the Emulator seems to have some major issues regarding this and was more of a headache. +  * **Score keeping / winner deciding** - This section is complete and was not too tough to sort out the biggest headache in this region was simulating the fluid firing motion. 
-  * Wireless connection - i.e. WLAN / Bluetooth - Seeming it seems like the Wireless connectivity is difficult to implement and test with the emulator.+\\ 
 +  * **Multi-player functionality in multiple devices** - This definitely sucks i.e the Emulator seems to have some major issues regarding this and was more of a headache. 
 +\\ 
 +  * **Wireless connection** - i.e. WLAN / Bluetooth - Seeming it seems like the Wireless connectivity is difficult to implement and test with the emulator. 
 +\\
   * **2D Rendering** - (if more time 3D) - The current implementation is based on 2D game. The time constrained to implement the 3D version was simply unforgiving.   * **2D Rendering** - (if more time 3D) - The current implementation is based on 2D game. The time constrained to implement the 3D version was simply unforgiving.
  
 ===== Presentation ===== ===== Presentation =====
 {{:android2010:grp15:ArmyWormsv1.pdf| ArmyWorms - Presentation 01      }}  {{:android2010:grp15:ArmyWormsv1.pdf| ArmyWorms - Presentation 01      }} 
 +\\
 +{{:android2010:grp15:ArmyWorms.pdf| ArmyWorms - Presentation 02      }} 
  
 ===== Package ===== ===== Package =====
-(.zip file)+{{:android2010:grp15:HelloAndroid.zip| ArmyWorms Zip file}}  
  
 ==== How to run ==== ==== How to run ====