Differences between revisions 8 and 9
Revision 8 as of 2016-02-01 10:05:50
Size: 5485
Editor: PeterPeters
Comment:
Revision 9 as of 2016-02-01 10:06:57
Size: 7049
Editor: PeterPeters
Comment:
Deletions are marked like this. Additions are marked like this.
Line 120: Line 120:

---- /!\ '''Edit conflict - other version:''' ----
Line 134: Line 136:

---- /!\ '''Edit conflict - your version:''' ----
=== ANDROID_AVD_HOME ===
 * When starting the android emulator, if it complaints that it can not find the <name of the AVD>.ini in "ANDROID_AVD_HOME" or "HOME" locations:
  1. find out where your ANDROID_AVD_HOME actually is. In AVD manager, select the AVD, then press the button "Details". In the picture below, the path in the red ellipse is actually where ANDROID_AVD_HOME should be.
   * {{attachment:avddetails.jpg}}
  1. Go to Control Panel\System and Security\System, then Advanced system settings, Advanced, Environment Variables, in the lower part of the dialog box about "System variables", press "New..." or if the ANDROID_AVD_HOME exists, press "Edit", make sure it looks like the following. Note: you have to fill out what is actually your ANDROID_AVD_HOME from Step 1.
   * {{attachment:avdhome.jpg}}

=== An alternative emulator ===
 * If you are fed up by the slow emulator, you may want to try this one:
  * https://www.genymotion.com

=== How to speed up the emulator ===
Thanks to Sven Ebens.

 * need an intel chipset, that supports VT-X
 * need to enable virtualization technology (or simular) in BIOS
 * snapshot is not necessarily faster, because it still takes basicly the same time to boot, but you get to continue where you left off
 * Disable Driver Signature Verification:[[attachment:disabledirver.pdf]]
 * Faster emulator: [[attachment:fasteremulator.png]]
  

---- /!\ '''End of edit conflict''' ----

Creative Apps 201602 (NOT OPERATIONAL YET !!!)

1. Planning

  • schedule.png

  • Week 1: Installation Processing with Android Mode, initial programming for Android
  • Week 2: Sensors, user interfaces
  • Week 3: Database access / networking??
  • Week 4: Installation XDK, initial programming with XDK
  • Week 5: User interfaces
  • Week 6: Android Native Apps II

2. Week 1


/!\ Edit conflict - other version:


  • If you have no experience with Processing, you are advised to follow GetStartedWithProcessing.pdf to learn the basics (password protected PDF. if you need the password, send p.j.f.peters(at)tue.nl an email);


/!\ Edit conflict - your version:


  • If you have no experience with Processing, you are advised to follow GetStartedWithProcessing.pdf to learn the basics (password protected PDF. if you need the password, send p.j.f.peters(at)tue.nl an email);


/!\ End of edit conflict


  • Try out some examples from the Processing programming environment, to see how these examples would behave on the emulator or on your Android phone.
  • Create full screen visual art on Android, using Processing. See below some examples. (To get inspired, you may want to have a look at http://openprocessing.org)

  • Create an Android app, display "Hello Eindhoven" in the center of the screen.
  • What to be delivered (as one single ZIP file)
    • working source code
    • screen copy of the output

3. Week 2

  • Presentations
  • Code
  • Homework and deliverables
    • Try out some examples using the Ketai library on the emulator or on your Android phone.
    • Android phone owners: Create an interactive app using one (or more) sensors.
    • Emulator only: Create an interactive app using touch (=mouse) input
    • What to be delivered (as one single ZIP file)
      • source code
      • screen copy of the output

4. Week 3

  • Presentations
  • Code: https://github.com/iddi/creativeapps

  • Homework and deliverables
    • Try out some HTML5 examples on the emulator or on your Android phone.
    • Create an interactive app using one (or more) sensors.
    • What to be delivered (as one single ZIP file)
      • source code
      • screen copy of the output

5. Week 4

6. Week 5

7. Week 6

8. Deliverables

  • Every week you will get homework and you are supposed to compete the work before the next lecture.
  • Deliver your work to creativeapps.submission@gmail.com, with your full name in the subject (so that we can find all your work later easily).

  • Deliver your work always in one ZIP file attached to your email.
  • You don't have to deliver every week. It can be delayed, until one week after the last lecture.
  • Please send your feedback request to one (not all) of the lectures according to this spreadsheet. Registrations.xls

9. Installation


/!\ Edit conflict - other version:


9.1. Processing installation

9.2. Intel XDK Installation

  • TBD


/!\ Edit conflict - your version:


9.3. Processing installation

9.4. Intel XDK Installation

  • TBD


/!\ End of edit conflict



/!\ Edit conflict - other version:


9.5. An alternative emulator

  • If you are fed up by the slow emulator, you may want to try this one:


/!\ Edit conflict - other version:



/!\ Edit conflict - your version:



/!\ End of edit conflict



/!\ Edit conflict - your version:


9.6. ANDROID_AVD_HOME

  • When starting the android emulator, if it complaints that it can not find the <name of the AVD>.ini in "ANDROID_AVD_HOME" or "HOME" locations:

    1. find out where your ANDROID_AVD_HOME actually is. In AVD manager, select the AVD, then press the button "Details". In the picture below, the path in the red ellipse is actually where ANDROID_AVD_HOME should be.
    2. Go to Control Panel\System and Security\System, then Advanced system settings, Advanced, Environment Variables, in the lower part of the dialog box about "System variables", press "New..." or if the ANDROID_AVD_HOME exists, press "Edit", make sure it looks like the following. Note: you have to fill out what is actually your ANDROID_AVD_HOME from Step 1.

9.7. An alternative emulator

9.8. How to speed up the emulator

Thanks to Sven Ebens.

  • need an intel chipset, that supports VT-X
  • need to enable virtualization technology (or simular) in BIOS
  • snapshot is not necessarily faster, because it still takes basicly the same time to boot, but you get to continue where you left off
  • Disable Driver Signature Verification:disabledirver.pdf

  • Faster emulator: fasteremulator.png


/!\ End of edit conflict


CreApps: FrontPage/CreativeApps201602 (last edited 2016-04-18 14:57:55 by PeterPeters)