Version 2.0

A Brief Guide for Version 2.0

Version 2.0 is packed with architectural improvements with an eye on collecting additional data to drive new reports, but also has many new features and bug fixes. This document covers both features (for users) and enhancements (for developers) but is likely too technical to be used directly by users. ##Upgrading The settings database adds an installed-version field that will allow to us preform database migrations. (App.js:54) Provided the installed version is one of null, v1.0, or v1.1, collect details on how long a pump site should last, CGM site should last, whether or not to zoom when tapping on a blank portion of the body, an insulin-to-carb ratio, the user's correct factor, target blood sugar, whether or not to use the new reminder system, and sets the database version to 2.0. Every existing site will be awarded one or two event log entries depending whether it's been removed. All existing sites have their locations re-determined, as, on the front of the body, prior versions confused left and right. Once the user reviews and sets new parameters, the application starts. ##Site Editor While the body-UI looks similar, it's been heavily refactored.

1. The Body is now wedged into the bottom of a scrollable VBox. By dragging down, a slider is revealed that will set the time window for sites to be displayed. By default, once a site is healed (as determined by the configured time it takes the site to heal) it will cease being displayed, but by adjusting the time period on the slider, unhealed sites can be suppressed, or long-since healed sites can be displayed.
2. The tap-tap add mechanism has been removed. Long taps are now the only way to add sites.
3. the old add-pump button has been changed to a generic add-site. This will temporarily hide all sites to make it easier to place a site. Shortcut: If you long-tap the add-site button, you'll get the add-event action sheet. The add-site button is implemented with a "combobutton" rather than an ordinary "button," and recognizes both taps and long-taps. You can swipe on the body to reveal a shaded image showing sites commonly used. It's hidden behind a legal disclaimer. Accepting the disclaimer writes the date/time of acceptance to settings as a form of auditing. ###Reminders When you add a site, if reminders are enabled, Site Selector will schedule a notification for Now + Type.lasts to change that site. This is implemented with [http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Introduction/Introduction.html](iOS Local Notifications) which have the advantage of not requiring any special privileges. Obviously this only works when compiled with Phonegap, and requires Greg Allen's Local Notification plugin. Running outside of Phonegap, Reminders are effectively ignored.
   ##Log In Site Selector 1, the log was an implicit report on saved Sites. Now there is an explicit Event Log, with title/description/time, and a Class/FK relationship to the underlying data (termed Owner Record). When you tap an item out of the log, the edit interface for that class is loaded with the owner record. Add Event ###Add Event In 2.0, the only event you can add is recording a blood sugar. Sites also log to the event log, but you cannot do that via a menu. Menu is there for additional types in the future, namely, Food, Insulin, Exercise. ##Reports Two reports exist in v2.0: Site Log and Site Effectiveness. Site Log is roughly similar to the old log, though, it adds a thumbnail indicating placement in addition to the textual description. Site Effectiveness agregates blood sugar stats against the different sites so as to identify which sites offer tighter control or faster/slower insulin absorption. ##Settings There are new settings to set baselines for the reports and to set defaults for data entry. The settings UI has been redone with fieldsets to make it more attractive. (All forms across the app have this style.)