User:Orsagi/Android app for MediaWiki translation/Project Updates

From mediawiki.org

Android app for MediaWiki translation - Project updates[edit]

This page provides ongoing weekly updates for the Android app for MediaWiki translation GSoC project.

Another great way to follow current assignments and work is on the project's Trello board.

HELP WITH BETA-TESTINGS: Download '.apk' file from here and report issues easily here.

See the outcome at:

Until Mon, September 23rd - Firm 'pencils down' date[edit]

Until Mon, September 16th - Suggested 'pencils down' date[edit]

  • split out code Yes Done
  • improve UI - sizes fit to content length Yes Done
  • Use a ContentProvider for dealing with a database. won't be done because ContentProvider is not the proper use in this case.
  • fix logout. Yes Done
  • create issues list to follow-up Note Note: issue report form
    • fix all those small bugs
  • beta-test on various devices
  • publish a stable package Note Note: public beta apk's

Until Wed, September 4th[edit]

  • continue working on the last week's assignments.

Until Wed, August 28th[edit]

  • Lowering expectations due to Or's exam (on 28th).
  • Complete last week's halfdones.
  • Implement a search (?) - planned but not implemented in the iOS since we doubt it's importance.
  • Any other basic settings?
    • logout.
    • restore defaults.
  • Make prettier, tidy and commented code, get prepared for testing sprint next week!

Until Wed, August 21st[edit]

  • Languages and projects picking support Incomplete Partially done UPDATE: Yes Done [11/9]
    • Custom preference view for showing long lists
      • Quickly searchable.
      • Refreshable for projects.
  • Saving preferences persistantly. Yes Done

Until Wed, August 14th[edit]

  • finishing translation module:  Yes Done 
    • quick submission by clicking on suggestion or self input.
    • minimize on sent. reopen on click.
    • save self input for each message
  • add features: Yes Done
    • translated message should disappear sometime (when?) Note Note: will be decided later
    • add ‘ttmserver’ suggestions.
    • filter to the best suggestion (and no duplicates)
    • handle “no translator right” case
  • add README.md file to commit Yes Done.

Until Wed, August 7th[edit]

migrating and adapting prototype's code to our project. Yes Done

  • write readme file with short description
  • finish implementing proofread activity. Yes Done
    • handle "accept"
    • Save rejected messages in a SQLight DB - do not show them again unless their revision number has been changed (later, we'll implement a reset for this).
    • show "accept/reject" for selected message.
  • optionally: implement preferences menu. N Not done - will be done for next week or two. ( 22/8 - Yes Done )
  • implement receiving messages for translation, their suggestions an documentations and show them nicely. Yes Done

Until Wed, July 31th[edit]

  • commit login demo  Yes Done (see video)
    • well commented
    • well tested + input validation
    • based on API wrapper library - implement login + logout methods
  • Add auto login support - secure save of the credentials so the user won't need to re-type them. (using Custom Account)
  • try out working with IntelliJ environment. Yes Done
  • optionally: implement api wrappers for proofread.

Until Wed, July 10th[edit]

Until Wed, July 3rd[edit]

  • follow-up new git repository - approved Yes Done
  • team meeting with Quim Yes Done
    • notes:
      • take a lesson from OPfW
      • feel free to add some links in monthly report, enable people to get as much info as possible.
      • invest, and plan, some time to handle documentation etc, do not wait for the last moment.
      • do some kind of summery at the end of the program.

Until Mon, June 24th[edit]

  • request for new git repository at location: app/android/translate. Yes Done

Until Mon, June 17th [edit]

  • verify the checklist at: Summer_of_Code_2013#Checklist. Yes Done
  • setup and beginning to familiarize with "Android Studio". Yes Done
  • create a developer account on Gerrit, setup git-review and start familiarize with Gerrit. Yes Done