aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
* Fix iOS 7 display to clear scroll barStruan Donald2013-09-26-2/+43
| | | | | If iOS7 set a class on the body and then use this to override various styles as well as the position of the map
* bump build numbersStruan Donald2013-09-25-1/+1
|
* update android white listStruan Donald2013-09-25-1/+1
|
* Restrict to latest version of androidStruan Donald2013-09-25-2/+2
| | | | For soft launch strategy
* Make latest Android version the target versionStruan Donald2013-09-25-1/+1
|
* Give main class a better name for neatnessStruan Donald2013-09-25-2/+2
|
* Fully qualify android activity nameStruan Donald2013-09-25-1/+1
|
* Target an up to date version of androidStruan Donald2013-09-24-1/+1
|
* put uses-feature camera in correct placeStruan Donald2013-09-24-1/+1
|
* Reduce the size of the photos we useStruan Donald2013-09-24-2/+4
| | | | | This helps to stop crashes on Android when taking photos due to out of memory issues
* split out photo option setting to a methodStruan Donald2013-09-24-2/+26
| | | | To remove duplication of option setting
* Update android manifest in line with phonegap recommendationsStruan Donald2013-09-24-1/+2
| | | | Mostly to prevent restarts on returning from the camera
* Save the current user as we goStruan Donald2013-09-19-0/+6
| | | | | | | This means that if something happens to interrupt the reporting process then any user details entered are not frustrating lost. Fixes #140
* Change initial map page if locating draft with no locationStruan Donald2013-09-18-19/+45
| | | | | | | | Only display the cancel button in the toolbar, use a different button with different text to indicate you are adding a location to an existing report Fixes #138
* Do not show relocate if search errors visibleStruan Donald2013-09-18-1/+3
| | | | Fixes #136
* clear search errors when starting new reportStruan Donald2013-09-18-0/+1
| | | | Fixes #136
* bump build numbersStruan Donald2013-09-18-2/+2
|
* Limit to Android 3.0 and aboveStruan Donald2013-09-18-1/+1
| | | | | At the moment there's a lot of glitches on Android 2 so initially restrict to Android 3+ as that seems reasonably stable
* remove example android config for tidynessStruan Donald2013-09-18-7/+0
|
* Add an android error pageStruan Donald2013-09-18-0/+18
| | | | | Slightly less jarring than a dialog if something goes wrong during app startup
* Remove android splash screenStruan Donald2013-09-18-3/+0
| | | | | It doesn't add anything other than a moment of possibly distorted logo so we might as well get rid of it
* Send 0 or 1 to server for may_show nameStruan Donald2013-09-18-1/+1
| | | | | Otherwise may_show_name is always set to true on server Fixes #135
* Save last show name publicly statusStruan Donald2013-09-17-17/+20
| | | | | | | Stops people who never want to show their name having to click the option every time. Fixes #134
* Location instead of positionStruan Donald2013-09-16-10/+10
| | | | For consistency
* remove debug codeStruan Donald2013-09-16-1/+0
|
* Remove hardcoded position result strings from offline pageStruan Donald2013-09-16-26/+46
|
* remove translate3d CSS calls for android phonesStruan Donald2013-09-16-2/+19
| | | | | | This is hopefully to fix the rendering issues on the Galaxy S4. See #116 for details
* Add explanation text to offline locating screenStruan Donald2013-09-16-28/+36
| | | | Fixes #132
* Indicate locating is optional on offline screenStruan Donald2013-09-16-6/+6
| | | | | | Just add extra text to the button. Fixes #131
* Change photo page title if report has a photoStruan Donald2013-09-16-24/+68
| | | | | | | | Also update it when adding a photo to give an indication that adding the photo was succesful. This is to remove any confusion about whether the photo on the page has been added. Fixes #130
* Resolve details screen scrolling issues on Android 2Struan Donald2013-09-13-0/+15
| | | | | | | | | Set Android 2 to use adjustPan when the soft keyboard is visible as this stops the details screen scrolling in such a way that the cursor is off the top of the screen. Leave the default for other versions as then the screen is scrollable. Fixes #128
* Make sure help 'dialog' is modalStruan Donald2013-09-12-0/+2
| | | | | | | | Both by setting the height of the container to 100% so it always covers the screen and also by adding a transparent background to emphasise that it's covering the screen. Fixes #127
* Add forgotten my password question to helpStruan Donald2013-09-12-0/+5
|
* Add note about confirmation to login errorsStruan Donald2013-09-12-10/+12
| | | | | | | Just to make it obvious you need to click the confirmation link to set activate the password Fixes #124
* Add hint text to set password pageStruan Donald2013-09-12-12/+28
| | | | | | | Mostly to make the user realise that they need to click the link in the confirmation email to activate the password. Fixes #125
* prevent map zoom snapback effectStruan Donald2013-09-11-0/+25
| | | | | | | | | | Overload PinchZoom control to check if we are at the limits of zoom and if so ignore any pinch zoom that tries to go past those limits. This stops the visual glitch of the zoom sort of working and then snaping back and also gives a visual indication of when the zoom limits have been reached. Fixes #118
* Allow details screen to scroll on AndroidStruan Donald2013-09-11-9/+96
| | | | | | | | | | | | | | | | | | | | | This fixes #113 in that it means the user can move the screen to see what fields are available. Previously this was prevented by setting the adjustPan mode for the soft input mode which had fixed a bug with the keyboard not dismissing on transition. This has been resolved by adding a plugin for Android to control display of the soft keyboard and hiding the keyboard before navigation in the navigate method of FMSView. Sadly this then meant that the screen size was being measured *before* the keyboard was dismissed with the result that the screen transitioned too was incorrectly displayed. This was resolved by taking the screen height on start up, storing that as a property of the FMS global object and then using this property instead of measuring the screen size at the time of transition. The map has also been expanded to fill the whole screen rather than stopping at the bottom of the navigation bar as on Android when you scroll the screen the map does not scroll and the gap at the top was visible.
* move action buttons on submit password screen below fieldStruan Donald2013-09-10-4/+4
| | | | | | | | Again, this is to make sure the button is visible when the keyboard is on the screen. This is at the cost of button placement consistency but it's probably more obvious of the user. Related to #120
* Place account login button directly under fieldsStruan Donald2013-09-10-2/+2
| | | | | | | This avoid the big gap in the screen and also means that the button is visible when the keyboard is on the screen. Fixes #120
* bump build numbersStruan Donald2013-09-10-2/+2
|
* Scale photos to roughly 3 MPStruan Donald2013-09-09-2/+2
| | | | | | | | | This should both stop issues with memory on phones and also reduce upload size. Will cause upscaling on phones with < 3MP cameras. 3MP picked as a compromise between quality and file size. Should fix #121
* delay display of photo delete buttonStruan Donald2013-08-23-2/+2
| | | | Stops it appearing on the screen before the photo and looking odd
* Make dubug output conditional on a debug flagStruan Donald2013-08-23-24/+30
| | | | | Replace console.log call to a wrapper function that only outputs if we've set a flag in config.
* remove unwanted debug statementsStruan Donald2013-08-23-6/+0
|
* Correctly handle back button on start screensStruan Donald2013-08-23-2/+26
| | | | | | | | On the inital screens the android back button should quit the app, or if on the map screen and you've started a report it should cancel it. Add in a default back method to FMSView and an override method for the map, exising report and offline screens Fixes #117
* Fix race condition when setting currentViewStruan Donald2013-08-23-2/+4
| | | | | | | | | As the front page only serves to work out what to do on load we should never set the currentView to front-page. However, due to execution order what actually happens is that the navigation to the front page completes after the navigation to the actual page displayed. This means that the incorrect currentView is set and the easiest way to fix is to prevent the currentView being set to the front page
* use 9 patch png for android splash screenStruan Donald2013-08-22-0/+0
| | | | | Results in much neater scaling For #115
* Reverse direction of locator progress indicatorStruan Donald2013-08-22-3/+3
| | | | Fixes #90
* use default iOS provisioning profilesStruan Donald2013-08-21-8/+8
|
* Change position of remove photo buttonStruan Donald2013-08-21-6/+34
| | | | | | | To stop it accidentally being mistaken for the next action button move the photo button to be a red X button in the lower right corner of the photo. Fixes #112