coryxie / mindroid.java Goto Github PK

Mindroid is an application framework that lets you create innovative applications using a set of reusable components - just like Android. The name Mindroid has two different meanings. On one hand Mindroid is a minimal set of core Android classes and on the other hand these classes also form the mind of Android. Mindroid is almost completely Android API-compliant with minor exceptions since Mindroid even runs on Java v1.4 (Java SE and Jave ME CDC) targets. Mindroid also includes an application framework documentation. The application framework is mainly intended for machine-to-machine (M2M) communication projects and the Internet of Things.

• ant sdk (Compile the Mindroid.jar SDK)
• ant apps (Compile the example application and install into the apps directory)
• ant docs (Build the SDK docs)

• ant run
• Linux: java -classpath Mindroid.jar:Main.jar main.Main rootDir=.
• Microsoft Windows: java -classpath Mindroid.jar;Main.jar main.Main rootDir=.

The rootDir must point to the parent directory of the apps directory to enable the package manager to find and load the apps. When starting the Mindroid examples e.g. from out/pc rootDir has to point to ".".

Links:

• Mindroid - Android everywhere
• Android messaging and concurrency for native C++ code development
• Alan Kay on Object-Oriented Programming

Most ideas of Mindroid come from Google's Android messaging and concurrency classes.

Android's messaging and concurrency framework (together with the Binder IPC mechanism) forms the basis of all Android applications and services. The messaging and concurrency framework is mainly based on the Thread, Looper, Message, MessageQueue and Handler classes. For convenience there is also the AsyncTask class and for inter-process communication there are some other classes like Binder, Parcel and Messenger.

A Looper is used to run a message loop for a thread. Threads by default do not have a message loop associated with them; to create one, call Looper.prepare() in the thread that is to run the loop, and then Looper.loop() to have it process messages until the loop is stopped. Most interaction with a message loop is through the Handler class. A Handler allows you to send and process Message and Runnable objects associated with a thread's MessageQueue. Each Handler instance is associated with a single thread and that thread's message queue. When you create a new Handler, it is bound to the thread / message queue of the thread that is creating it - from that point on, it will deliver messages and runnables to that message queue and execute them as they come out of the message queue. Furthermore, one can bind as many Handlers as he or she wants to a single thread / message queue for message handling. There are two main uses for a Handler. First a Handler allows you to enqueue an action to be performed on a different thread than your own and furthermore it also enables you to schedule messages and runnables to be executed at some point in the future. The AsyncTask class enables proper and easy use of concurrency in a multithread environment. For more information about this class see Google's "Painless Threading" article. (Source: Google Android Developer Reference).