TECHNOLOGIES
Why No(U)t? functions with:
- Java support; the prototype code was developed with Mobile Processing on a Nokia 6600 (with a resolution of 176×208) mobile phone;
- Bluetooth technology
CODE
The code is based on the sample and with the help of Vinay Ventrakamen and Nicholas Zambetti for IUAV Interaction Design Programme. In particular, samples we followed are: Simple SMS Application and ZóGAME.
Prototype simulate the interface animation and the text insertion option; more screens were created and put in a succession. Processing file code was divided in 6 tabs to make the navigation to the editor easier.
The essential phases in writing code were:
- insertion of images
- disposition and interaction of screens
- phone settings with Mobile Processing Library recall
- variables
- recalling by previous/next screen
- recalling of every screen, according with user’s inputs (mobile bottons)
“Why No(U)t?” parts:
“Welcome”:
Starting the software appears a “Welcome screen”, that contains logo and disappear after few seconds (calculated with a millisecond counter) *
“Index”:
Composed by two levels: background and icon status (recalled from the “Set Status” option)
“Menu”:
Composed by six different screens (everyone with a different icon selected)
“Compass”:
Developed on three levels:
- “Map_ve” is an image, bigger than the mobile screen and it’s moving by the joystick input;
- “Screen_layerINFO” is visible only if user request and it’s linked with “Map_ve”;
- “Map_buttons” is a static level.
“Why Not?”:
Composed by a sequence of images.
“Sos?”:
Composed by 3 groups of variable interfaces (voidDraw…):
- “Sos” with the s.o.s.’s contact list
- “Sos_edited” that appears in an higher level and depends on “Sos_edit” impostation;
- “Sos_edit” sequence of images similar to “contacts”
“Contacts”:
Composed by a sequence of images.
* this part of the code was created from us.
WHY NO(U)T? | Concept | How it function | Graphics | Tecnologies & Code | Downloads | Credits & Contacs