Changelog

kaeppler edited this page Apr 20, 2012 · 3 revisions

Changelog

Come back here for a list of recent changes to the library.

ignition 0.2 (Apr. 20th, 2012)

This release in a nutshell

  • Many improvements to IgnitedAsyncTask to make it even more flexible and powerful
  • Many improvements to IgnitedLocationManager and related classes
  • Reduce number of sample apps to 3, where each one combines all code samples for the respective ignition module

NOTE

IgnitedAsyncTask APIs have changed! You may need to update your code to reflect these changes. Most importantly, the task callbacks are now called:

  • onTaskStarted
  • onTaskProgress
  • onTaskCompleted
  • onTaskSuccess
  • onTaskFailed

This release in detail

See https://github.com/kaeppler/ignition/compare/ignition-0.1...ignition-0.2

ignition-support:

  • fix RemoteImageLoader to correctly work with servers that do not report a Content-Length header (thanks mlc for the fix!)
  • adding expected status codes to an IgnitedHttp request will not add them multiple times anymore
  • IgnitedScreens now supplies a SCREEN_DENSITY_XHIGH constant (can be read even on Android 1.6)
  • IgnitedDialogs: added a helper method to create a default progress dialog
  • RemoteImageLoaderHandler now accepts a custom looper. This is useful if you're instantiating the handler on a worker thread, but want to handle the image on the UI thread (pass Looper.getMainLooper() here).

ignition-core:

  • IgnitedAsyncTask now supports the concept of task handlers. This means the class is freed of the requirement to always handle task events itself. Instead, any arbitrary object may now act as an IgnitedAsyncTaskHandler so that you can share callback functionality across activities. Of course any Context may still act as a handler itself, by implementing IgnitedAsyncTaskContextHandler.
  • IgnitedAsyncTask now supplies callbacks that do not have access to a Context instance. These callbacks will always be called, even if the current context is null.
  • IgnitedAsyncTask callbacks now return boolean. By returning true in a handler, you can prevent the event from bubbling up to the task class itself. Semantics are equivalent to how event handlers work in Android.
  • IgnitedAsyncTask's run() method is now public so that you can invoke a task synchronously. This is useful if you want to re-use task logic in e.g. an IntentService, which itself spawns an AsyncTask.
  • EndlessListAdapter now provides a static helper method that can be invoked from onScroll and which determines whether the bottom of the list view has been reached (see code samples)

ignition-location:

  • the location module does no longer depend on the Google APIs; vanilla android-10 suffices now
  • many fixes and tweaks

samples:

  • there will only ever be one single sample for each module from now, with each app listings all available sample activities (fixes issue #20)
  • added sample for EndlessListAdapter