Virtual Reality (VR), Augmented Reality (AR), 3D Application Development Tools and Platforms

Hi folks,

Most of the developers think Unity is only the development platform to develop Virtual Reality (VR), Augmented Reality (AR), 3D Applications.

Here is the list which might be useful you to explore based on your skillset.

1. Unity - C#
2. Unreal - C++
3. Apple SceneKit - Swift / Objective-C
4. Google Sceneform - Android
5. Amazon Sumerian - JavaScript
6. Babylon - JavaScript - Try online Playground
7. A-Frame - HTML JavaScript
8. Three - JavaScript - Examples

Hope this information is useful for you to create your own applications based on your knowledge.

Make your dreams to real using the VR, AR, 3D technologies.

Please send your feedback and comments to psrdotcom@gmail.com

Convert Physical/Virtual Machine to vSphere ESX using VMware vCenter Converter Standalone

Hi all,

Objective

Moving/converting locally installed VMware Virtual Machine to vSphere ESX

Procedure

Download VMware vCenter Converter Standalone

Install it on your own windows machine (or) client/server mode

Once the installation completed, run the coverter

Click on "Convert machine"

Select the VM type and select .vmx file

Enter your destination vSphere server/ip address, username and password

Click on "Next"

You can change the VM configuration before coverting

Click on Next

Now it will start converting your VM and copy the VM to your vSphere

On vSphere, like normal vSphere client, you can start your VM and enjoy the configured/already using VM on vSphere.

Please send your comments and feedback to psrdotcom@gmail.com

Android Virtual Device (AVD) Emulator Creation and Installing APK on Emulator Using Command Line

Dear friends,

Every time whenever we are using most of the Android developers are using Eclipse or some other IDE to create and start the AVD.

I was just thought of using it via command line in my Ubuntu because I was very lazy to start and wait for Eclipse to get ready. I just want to try some apk on Emulator.

Ubuntu Procedure

Open terminal
I was hoping that you had already included the Android tools, platform-tools in PATH. If not just do that else navigate to Android SDK directory

Create AVD:

Syntax: 
$ android create avd -n -t --abi

target-ids are based on the installed Android platforms. Its not the Android API Level.

abi(Application Binary Interface): The ABI is used to control which machine code will run on a given hardware device. For example, for an Android application to run on an x86 device, it is necessary to include x86 ABI support when compiling the application.

Example:
$ android avd -n MyJB -t 12 --abi armeabi-v7a

To view the target-ids list and supported ABI for target-id, execute the following command

$ android list targets

You might be getting some output similar to this

Available Android targets:
----------
id: 1 or "android-3"
     Name: Android 1.5
     Type: Platform
     API level: 3
     Revision: 4
     Skins: HVGA-P, QVGA-L, HVGA-L, HVGA (default), QVGA-P
     ABIs : armeabi
----------
id: 2 or "android-4"
     Name: Android 1.6
     Type: Platform
     API level: 4
     Revision: 3
     Skins: HVGA, QVGA, WVGA800 (default), WVGA854
     ABIs : armeabi
----------
id: 3 or "android-7"
     Name: Android 2.1
     Type: Platform
     API level: 7
     Revision: 3
     Skins: HVGA, QVGA, WQVGA432, WVGA800 (default), WQVGA400, WVGA854
     ABIs : armeabi
----------
id: 4 or "android-8"
     Name: Android 2.2
     Type: Platform
     API level: 8
     Revision: 3
     Skins: HVGA, QVGA, WQVGA432, WVGA800 (default), WQVGA400, WVGA854
     ABIs : armeabi
----------
id: 5 or "android-10"
     Name: Android 2.3.3
     Type: Platform
     API level: 10
     Revision: 2
     Skins: HVGA, QVGA, WQVGA432, WVGA800 (default), WQVGA400, WVGA854
     ABIs : armeabi, x86
----------
id: 6 or "android-11"
     Name: Android 3.0
     Type: Platform
     API level: 11
     Revision: 2
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 7 or "android-12"
     Name: Android 3.1
     Type: Platform
     API level: 12
     Revision: 3
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 8 or "android-13"
     Name: Android 3.2
     Type: Platform
     API level: 13
     Revision: 1
     Skins: WXGA (default)
     ABIs : armeabi
----------
id: 9 or "android-14"
     Name: Android 4.0
     Type: Platform
     API level: 14
     Revision: 3
     Skins: WXGA800, HVGA, QVGA, WQVGA432, WVGA800 (default), WSVGA, WXGA720, WQVGA400, WVGA854
     ABIs : armeabi-v7a
----------
id: 10 or "android-15"
     Name: Android 4.0.3
     Type: Platform
     API level: 15
     Revision: 3
     Skins: WXGA800, HVGA, QVGA, WQVGA432, WVGA800 (default), WSVGA, WXGA720, WQVGA400, WVGA854
     ABIs : armeabi-v7a, mips, x86
----------
id: 11 or "android-16"
     Name: Android 4.1.2
     Type: Platform
     API level: 16
     Revision: 4
     Skins: WXGA800, HVGA, QVGA, WQVGA432, WVGA800 (default), WSVGA, WXGA720, WXGA800-7in, WQVGA400, WVGA854
     ABIs : armeabi-v7a, mips, x86
----------
id: 12 or "android-17"
     Name: Android 4.2.2
     Type: Platform
     API level: 17
     Revision: 2
     Skins: WXGA800, HVGA, QVGA, WQVGA432, WVGA800 (default), WSVGA, WXGA720, WXGA800-7in, WQVGA400, WVGA854
     ABIs : armeabi-v7a, mips, x86

Start AVD

Syntax:
$ emulator -avd

Example:
$ emulator -avd MyJB

It will ask for you to customize, if you are interested and you have knowledge in the options then you can go ahead with custom emulator. Press "enter" to accept default options and your emulator will start within seconds.

Install APK on emulator

Syntax:

$ adb install

Example:

$ adb install MyApp.apk

It will install the apk on your emulator.

Go to apps and click on the installed app to view the installed application.

References:

http://developer.android.com/tools/help/android.html
http://developer.android.com/tools/help/adb.html
http://docs.xamarin.com/guides/android/advanced_thttp://en.wikipedia.org/wiki/Application_binary_interfaceopics/cpu_architecture

Java Virtual Machine (JVM) vs Kilobyte Virtual Machine (KVM) vs Dalvik Virtual Machine (DVM)

Hi friends,

Do you that the java program, when running on different architectures, it runs on different virtual machine (VM)?

Why it need different VM when running the similar syntactical code?

Let me take the opportunity to share and explain what I have gone through

I have been read about 3 main VMs.

Java Virtual Machine
Kilobyte Virtual Machine
Dalvik Virtual Machine

Java Virtual Machine:
JVM executes Java .class bytecode to run the Java applications. JVM with set of libraries form a JRE, which is installed on computer to execute any Java program.


Kilobyte Virtual Machine:
Java API contains large set of standard libraries. To use the same no.of libraries in Mobile is not possible due to memory constraint in the mobile. So, they have come up with an idea to take a subset of libraries and form a profile in Java 2 Platform Micro Edition (J2ME). So JVM is replaced with less memory running KVM. KVM is designed to run in kilobytes memory for small devices.

Dalvik Virtual Machine:
When it comes to Android Operating System, they don't want to either JVM or KVM. Because they want to run a virtual machine for every application. This concept can't be implemented with existing virtual machines. Due to this reason, this virtual machine is integral part of the Android Operating System. In Android, the java .class bytecode converted to dalvik compatible .dex which will be executed with Dalvik Virtual Machine (DVM). The set of .dex files forms an Android Package (.apk) file, which gets installed on the devices to install and run the applications.

Similarities:
All the virtual machines primary source is developed in java.

Dissimilarities:
Set of libraries have changed.
Memory allocation is different.


References:
http://docs.oracle.com/javase/specs/jvms/se7/html/index.html
http://java.sun.com/products/cldc/wp/
http://catazinelive.catreloaded.net/2012/02/08/dvm-dalvik-virtual-machine/