1. 28 Jun, 2012 1 commit
    • Alan McNatty's avatar
      A large commit that moves the artefactdatasqlhelper 'stuff' into a content... · 268396d3
      Alan McNatty authored
      A large commit that moves the artefactdatasqlhelper 'stuff' into a content provider so we can set upa content observer and listen for content changes. This is significant in the cleanliness of the artefacts .. an uninstall and reinstall will be required.
      
      Also split the Utils class into Sync and Account Util classes so it's a bit more focused (easier to know where to look etc).
      268396d3
  2. 26 Jun, 2012 1 commit
  3. 13 Jun, 2012 1 commit
  4. 06 Jun, 2012 1 commit
  5. 28 May, 2012 1 commit
    • Alan McNatty's avatar
      This is another major phase of work in getting the upload API working for Journals. · c283d97e
      Alan McNatty authored
      A lot of additonal internal fiddling - we're getting closer to the desired end result but there is still some refactoring to do.
      TODO:
      1) our Artefact object will become an Upload object (name only really).
      2) the files / attachments should be visable on the upload/post settings UI
      3) on the back-end upload API sie - check for a Journal post with the same title and description. If one exists - attach the additional file and move on. Saves creating lots of duplicate (looking) journal posts
      4) add the Journal name to the main UI (consider also adding an icon for file or compose so the type can be easily seen)
      5) review the add / delete philosophy of the sync adapter - may be an easy solution - check for existing, etc and add and remove those not seen.
      6) testing - especially the sync of saved posts but also from startup - if auth success trigger a sync etc.
      7) review useof notifications - seem very noisey if lots of uploads are done.
      c283d97e
  6. 12 May, 2011 1 commit
  7. 10 May, 2011 1 commit
  8. 02 May, 2011 1 commit
  9. 06 Mar, 2011 1 commit