-
Notifications
You must be signed in to change notification settings - Fork 1k
Getting started
Let’s get started with ActiveAndroid. The first thing you need to do, if you haven’t already done so, is download the ActiveAndroid library. or the latest stable ActiveAndroid jar file. If you downloaded the library and not the jar, you'll have to build the jar file by running ant
in the root folder. Your ActiveAndroid.jar, which is what we need, will be in the dist
folder.
Now that you have the ActiveAndroid library you can add it to your project’s build path. If you’re using Eclipse:
- If you haven’t done so already, create an Android project.
- Copy ActiveAndroid.jar to the libs-folder of your new project.
- Right click on your project and select Build Path > Configure Build Path…
- Click the Add External Jars… button and choose the ActiveAndroid jar file.
If you're using Android Studio:
- If you haven’t done so already, create an Android project.
- Drag the jar to the libs folder of project.
- Right click on the jar, and select "Add as a Library…"
First, clone the source from Git and install the package to your local repository:
Note: Maven 3.1.1 or later is required
git clone https://github.com/pardom/ActiveAndroid.git
cd ActiveAndroid
mvn clean install
After the project builds successfully, add the following dependency to your pom.xml
<dependency>
<groupId>com.activeandroid</groupId>
<artifactId>activeandroid</artifactId>
<version>(insert latest version)</version>
</dependency>
Modify your build.gradle to include:
repositories {
mavenCentral()
maven { url "https://oss.sonatype.org/content/repositories/snapshots/" }
}
compile 'com.michaelpardo:activeandroid:3.1.0-SNAPSHOT'
Now that you have ActiveAndroid added to you project, you can begin your two-step configuration process! The first thing we’ll need to do is add some global settings. ActiveAndroid will look for these in the AndroidManifest.xml file. Open the AndroidManifest.xml file located at the root directory of your project. Let’s add some configuration options.
- AA_DB_NAME (optional)
- AA_DB_VERSION (optional – defaults to 1)
The configuration strings for my project look like this
<manifest ...>
<application android:name="com.activeandroid.app.Application" ...>
...
<meta-data android:name="AA_DB_NAME" android:value="Pickrand" />
<meta-data android:name="AA_DB_VERSION" android:value="5" />
</application>
</manifest>
Notice also that the application name points to the ActiveAndroid application class. This step is required for ActiveAndroid to work.
If you are using a custom Application class, just extend com.activeandroid.app.Application instead of android.app.Application
public class MyApplication extends com.activeandroid.app.Application { ...
But what if you're already doing this to utilize another library? Simply initialize ActiveAndroid in the Application class. You may call ActiveAndroid.dispose();
if you want to reset the framework for debugging purposes. (Don’t forget to call initialize again.)
public class MyApplication extends SomeLibraryApplication {
@Override
public void onCreate() {
super.onCreate();
ActiveAndroid.initialize(this);
}
}
If you want to build a database dynamically.You can use the configuration class.
public class MyApplication extends SomeLibraryApplication {
@Override
public void onCreate() {
super.onCreate();
Configuration dbConfiguration = new Configuration.Builder(this).setDatabaseName("xxx.db").create();
ActiveAndroid.initialize(dbConfiguration);
}
}
In our example we have two tables: Category and Item.
In step two you will create classes for those tables.
Don’t worry though, this part is easy too.
We'll go into more detail about setting up the database model later, but here are our classes.
@Table(name = "Categories")
public class Category extends Model {
@Column(name = "Name")
public String name;
}
@Table(name = "Items")
public class Item extends Model {
@Column(name = "Name")
public String name;
@Column(name = "Category")
public Category category;
}
That’s it for configuration. Next, let's learn about creating your database model.