Comments on The Entropy of Perplexity!: Android App : MoneyTracker

Hi, I just posted a comment at the db4o site that ...

2009-06-29T17:43:37.715+01:00

Hi, I just posted a comment at the db4o site that might help you to get the footprint of your application down :

http://developer.db4o.com/forums/55881/ShowThread.aspx#55881

Let me know if this might work for you.

Cheers,

Pavel

I'm not sure there are (m)any options at the momen...

2009-05-29T15:56:47.154+01:00

I'm not sure there are (m)any options at the moment.

As it happens I feel the footprint of db4o is too big to be useful in an actual Android application. However, I didn't want to use SQLite so I created a an abstraction layer to handle simple Object Serialisation, easily replacable with db4o later. (The version of MoneyTracker on the Android Market is using the object serialization method.)

The db4o team are going through a process of modularising db4o so I'm hoping to see a vastly reduced db4o footprint in the future.

Much! simpler and nicer than the SQLite version. S...

2009-05-29T15:36:18.703+01:00

Much! simpler and nicer than the SQLite version. SQLite was certainly a good choice for an embedded RDBMS, but it would be nice to have optimized db4o available as well. If you look at the architecture at http://developer.android.com/guide/basics/what-is-android.html you'll see how how deep in it SQLite is. I'm sure that lots of the core libs and app f/w has been written with the SQLite in mind. It's probably up to Google to really embed some sort of object DB into Android. I don't know if its possible to extend the app f/w without forking the whole OS?
Since ContentProviders provide data in the tabular format, they are out of the question.. What other options there are, to exchange data with an db4o service?