Skip to content

Latest commit

 

History

History
131 lines (102 loc) · 5.06 KB

CHANGELOG.md

File metadata and controls

131 lines (102 loc) · 5.06 KB

Release notes for RoboSpice

Version 1.1.2

TO BE RELEASED Bug fix and test addition release :

  • TODO test ormlite module, xml module, gson module

Version 1.1.1

Bug fix :

  • enhanced SpiceManager cpu usage. There used to be a bug in case a service had no request to process that boosted cpu usage. Thx to Riccardo Ciovati.
  • enhanced ORM Lite support : tables are created fully dynamically for all POJOs saved via the ORMLiteObjectPersisterFactory. No need to provide a specific factory for every class of IDs used by persisted POJOs.
  • better RoboSpice Motivations icon
  • Added RoboSpice Motivations to Google Play

Version 1.1.0 (released for DroidCon London, October 24th 2012)

  • Added RoboSpice Motivations to repo as a RoboSpice demo app and in-depth argumentation for RoboSpice existence.
  • Added RoboSpice Motivations to the Google Play store.
  • Added Json Serialization support using Gson (Jackson is also supported since V1.0)
  • Added Xml Serialization support using SimpleXMLSerializer
  • Added Orm Serialization support using OrmLite
  • Permission check : applications must declare both INTERNET and NETWORK_STATE permission.
  • Added getFromCache method in SpiceManager to query cache content.
  • Added progress monitoring for requests (both status and progress percent).
  • Added common foreground service for all SpiceManagers using the same service class.
    • Requests are now completely decoupled from Activity life cycle.
    • Service stops when no more requests are active and no SpiceManager is bound.
  • Added methods to get data in cache if present
  • Added methods to add listeners to a pending request if present.
  • Added support for creating notifications for a request through a new service helper.
  • Allow to cancel pending requests from new Activity.
  • All logs in RoboSpice now use a downgraded version of RoboGuice's logging facility : http://code.google.com/p/roboguice/wiki/Logging
  • Added the ability to provide a custom executor service to the SpiceService's RequestProcessor. Thx to Riccardo Ciovati.
  • Added RoboSpice presentation in the download area of Git Hub
  • Added all RoboSpice related gfx to GitHub repo.
  • Added google discussion group
  • Added Starter Guide on Git hub Wiki

Version 1.0.0

  • Name changed from Content Manager to RoboSpice
  • published on Github
  • published on Maven Central

Version 0.0.13

  • minor enhancement of simple requests, exception stack traces were lost.

Version 0.0.12

  • back to previous dependency injection model inside services.
  • content manager is now more robust and more stable
  • dropped the idea of integrating AsyncTasks into the framework.
  • minor enhancements.

Version 0.0.11

  • configuration is now entirely mavenized. No libs folder anymore, every dependency is controlled by maven. Most dependencies are standard although some of the android dependencies are still missing in maven, in that case, developpers will have to create them through mvn import-file goal. content-manager-it, the test app can't be used under eclipse yet (as the android configurator is not ready yet) : devs should disable maven nature and add the sample as a project in the test app java build path.
  • various attempts have been made to enable canceling a spring android request but that failed. It's not possible and won't be possible in a near future to cancel a request that has started its network connection. That's a real concern but spring android doesn't support this feature yet.
  • mostly released for Samy to give content manager a circuit run.

Version 0.0.10

  • revisited maven configuration for deployment

Version 0.0.9

  • life cycle of the ContentManager has improved
  • InputStream based requests had a logical problem : they were processing InputStream on the UI Thread, and that is prohibited as of HoneyComb (and a bad practice), they now process the network stream in the background and offer either a memory stream or file stream to be processed by listeners (who can still delegate the processing to an asynctask for buttering).
  • Injection Dependency changed to some more standard option : developpers will have to create an Application Class that will provide ContentService instances all their required dependencies.

Version 0.0.8

  • AndroidManifest check. ContentManager will get sure a ContentService has been declared in manifest

Version 0.0.6

  • changed deploy url

Version 0.0.5

  • async operations for ObjectPersisters are available (and optional)
  • persistence layer cleaning, refactoring and renaming
  • added BigInputStream and SmallInputStream requests
  • added README
  • testing
  • more cache cleaning methods
  • removed roboguice dependency :(
  • split of spring android and json modules

Version 0.0.4

  • first maven and jenkins integrations
  • renaming of maven artefacts
  • nexus deployment
  • local service binding
  • removed all bundlization stuff

Version 0.0.1 (June 23rd 2012)

  • extracted project from ctl*m app
  • gitified project