Getting started with charting

I started using the http://www.achartengine.org library in my app today. Have not integrated it properly yet. So far I have just shoved the demo activity into my existing app. This is the jar and what goes where part of the job out of the way, so now I just have to get the hang of the renderers and pick a nice looking chart. More on this as I use it, but so far it looks nice. Tons of places to use charts in just about any app.

Fixed a bunch of problems related to how activities are kicked off when you are expecting a result. Using startActivityForResult and calling finish from the target Activity means that your user does not end up meandering through no longer relevant Activities as they press the back button. The overall flow is now much improved.

Still getting tripped up by the upgrade path for a modified database. I reckon this should be a straightforward, almost mechanical method to write (the override of SQLiteOpenHelper.onUpgrade()), but I keep getting knotted up in it. On my workstation it's fine, but on my device, not so much. This is presumably because I only deploy to the device now and again. This means that several chunks of upgrade SQL need to be run in the correct order, rather than the simple chunks getting run every time I make a minor change on my machine. Will have to thrash this one out soon as it is costing me too much time.

Exceptions - I had been getting several situations where I was not getting exceptions even though the emulator had hung (awaiting launch of Activity). It turned out that the emulator/eclipse tool set (DDMS most likely) had paused things as they started to go pear shaped. Just clicking resume a few times gave me a nice explicit exception trace to work with.

Started watching this too. Excellent idea. I had developed a simple serializer/deserializer a while ago which dumped arbitrary data to appengine. Happier using a 'real' toolset to do this from now on. I downloaded and installed the beta of the eclipse tooling for this, but did not give it a spin yet.

Now getting over the initial wobbles related to getting a hang of how everything hangs together - list views for example and just how I get references to widgets and where I keep them. Will hopefully start to see development accellerating over the next few days.

Comments

Post a Comment

Popular posts from this blog

Building a choropleth map for Irish agricultural data

I wanted to create a choropleth map  using Irish data. The Irish Government has made a large quantity of data available at data.gov.ie. The set I chose was for Bovine TB across Ireland over a number of years. You can get geojson for a variety of countries and Ireland's county boundaries are available. All I had to do was get the data labels to match. In the data some counties are split into 2 parts. I merged and summed these data points to get the choropleth to work with normal county boundaries. You can see the results here . A link to the github is included at the top of the notebook.
Read more

Early Stopping with Keras

Steps to train a model There are a number of things you have to do when working on a Machine Learning problem. Import your data and transform it as appropriate Define  your model using something like Keras - this includes your chosen hyperparameter values Run the training phase Evaluate the model If at the end of this process the evaluation shows that your model is not sufficient for your needs you will need to make some changes and rerun the training.  Ideally you should have a way to spot that training is not going as you want and stop it. This is one of the uses of early stopping. The other is if your model has reached a sufficient quality standard for you to use and further improvements have slowed, stopped altogether or an unnecessary.  Early Stopping Keras provides a way of doing this using the EarlyStopping callback . There are a range of callbacks in Keras and you can define your own. Details are here . The EarlyStopping callback works by choosing a metric
Read more

AutoCompleteTextView backed with data from SQLite in Android

Image
This is a handy piece of code. As your database gets bigger you can allow the user to pick the correct value by typing. If the db gets very big, you can always increase the threshold, so that the query does not run until there will be a suitably sized resultset returned. Running it at a threshold of 1 is fine for very small resultsets.  Here is the code you need to back your AutoCompleteTextView with a cursor adapter. @Override protected void onResume() { super.onResume(); text = (AutoCompleteTextView) findViewById(R.id.autoCompleteTextView1); final AdapterHelper h = new AdapterHelper(this); Cursor c = h.getAllResults(); startManagingCursor(c); String[] from = new String[] { "val" }; int[] to = new int[] { android.R.id.text1 }; CursorAdapter adapter = new MyCursorAdapter(this, android.R.layout.simple_dropdown_item_1line, c, from, to); adapter.setFilterQueryProvider(new FilterQueryProvider() { public Cursor runQuery(Cha
Read more