hbons/SparkleShare — Issue #523: Settling and documenting and the synchronization behaviour
Author: Motiejus
Created: 2012-01-12 18:28:13+00:00
State: open

Hello,

I am willing to create an android version of SparkleShare that can do full synchronization.

For that to work I have to mimic what SparkleControllerBase does. The code that makes the commits and changeset is in SparkleControllerBase.cs. It is quite understandable, but undocumented.

Is the commit and changeset format is going to change radically? If not, we could start documenting the interface and I could start porting SparkleControllerBase to java (and subsequently merge it with SparkleShare-android UI, since it's pretty).

Are there any more gotchas I should know while implementing a new backend?