Shepherd now does automatic polling much slower, but has a manual poll button. Shepherd highlights sites that use a different deployment server than Shepherd's target deployment server in italic. Shepherd lists all Usher-advertised services on site detail screens. Changed upload script to avoid passive FTP.
Merge branch 'develop' of github.com:acres4/acres4 into develop
Supervisor - Bluetooth - any device previously used by this user will be moved to the top of the available devices list.  This will have no effect until a server-based bluetooth tracking functionality is added.
Bluetooth - fixed bug where user/device associations would incorrectly persist after manual removal
Supervisor - Bluetooth - the most recent user name for each BT device is now shown below the device in the pairing menu
Added MEAL Talk classes to NetJSON
Supervisor - Bluetooth - added unpaid button that does not work very well if at all at the moment
Supervisor - Bluetooth - improved UI when connecting a device.  Failure is still not indicated well.
Selecting a canned report will update the filter details, added a ReportParams object to the dashboard cells, fixed the check marks on the canned report. Only one canned report can be selected at a time.
Created offline MEAL recording class
Supervisor/Frontline - both update the offline MEAL reporting tool's cached Mercury configuration
Added server test ability for Mercury and Build servers to Shepherd.
@autobuild{shpeherd} Shepherd does server status tests now for Mercury and Build. Need a little bit more info to do Oracle.
@autobuild{shepherd} Typo in last autobuild for Shepherd.
Shepherd no longer logs all test messages to console.
Supervisor - reorganized service call tab source files in the project
Removed MealRecorder from NetJSON-OSX
Changed the dashboard to be in a scroll view so the report viewer can be part of the dashboard.  This will allow reports to persist.
Fix for issue with incoming messages being processed out of order.  See sifter issue 1101 (Change Auto-Defer Call Setting from 60 Secs to 30 Secs).  WorkInfo objects were being received in rapid succession and the CommDispatcher was not sending the State notifications in the right order.  Incoming comet messages could be handled at the same time on different threads causing messages to be delivered out of the intended order.  The dispatchResponse method is now being called in the sync block preventing the second message from being processed ahead of the first message.
Merge branch 'develop' of https://github.com/acres4/acres4 into develop