Philip Sheard has been working in IT for over 40 years, and on this project for the last 20. His current skills include Java, Android, Objective-C, iOS, PHP, MySQL, ASP.Net, SQL Server, HTML, CSS, Apache and WordPress.
A Lenovo Chromebook Duet, with 128 GB of storage and a USI pen for £248. This replaces my old Chromebook, which had stopped working. I have not decided how I am going to use it, but it was an incredible bargain.
A Kindle Fire 8 for £40. This upgrades my Fire 7, which was too slow for debugging. Another bargain, normal price £90.
As of Android 12, Device Ids are now the only way that Google allows developers to identify individual devices. EMI/IIE numbers MAC addresses are no longer available. This means that some self hosting licences may have to be reissued.
This release is the first attempt to replace the use of Dropbox with a proprietary solution using standard Android methods. The motivation for this the frequency with which Dropbox publishes new APIs, and their extremely poor documentation.
The layout of the old Dropbox screen has been modified as follows:
The title has changed to Files.
The Authorise option has been removed.
The database Upload and Download options have also been removed. This makes the Save and Restore options pretty useless as things stand, but hopefully all is not lost.
The images Download option now downloads the product images from a location specified by the system administrator (see below).
A number of changes have been made to the Profile page of the Hosting Service (see above):
The title has been changed from Edit Profile to Profile.
There is a new Help option on the toolbar. Clicking it will display a help page. This is how all help text will be delivered in future.
A field called Files has been added. This should be the web address of a directory that your site has access to, and where you place tour company images.zip file.
The site has been given a slightly more modern look.
The proposed solution does not allow the user to save and restore his database. Android still allows apps to access external storage, by means of a file picker type interface. This is usually NOT the SD card, but a picker may allow the user to access that as well. Even if the device does not have an SD card, it may still be possible to export the database, and then upload it to Dropbox or Google Drive. Clearly more work needs to be done on this.
The solution assumes that all users have the same product images. Workarounds are possible, but tedious.
The solution has been implemented as a service, which makes it easy to support self hosted servers. All that the administrator has to do is modify the new dump script. I will add a sample of this to the scripts available for download.