Continuing the discussion from Some Observations, Suggestions & Questions:
iRhino 3D users: I have a question about Cloud integration in iRhino 3D (see below).
Before that: some background...
The Dropbox and GoogleDrive integration in iRhino 3D was written during the early early days of iOS...way back when there weren't even Google apps and Dropbox apps and Box apps and iCloud Drive...you get the idea. We implemented these features using the tools available at the time... and they "sort of" work. But the world has moved forward and things have changed (what's new?)
For example: we are using what is called the Dropbox "Classic" API, which uses http/REST to get to files. Dropbox now has what is called the Dropbox "Sync" API, which has far deeper integration, but also presumes a lot more about what you want to do with the files you are "sync"-ing with. iCloud is another good example. iCloud Drive would be very difficult to integrate in iRhino 3D with the current "browse-for-files-add-update-on-demand" paradigm.
Additionally, there are now very good iOS apps for GoogleDrive, Dropbox, Box, and iCloud drive that work well with iRhino 3d as it stands (some refinement might be needed, but these seem to do the trick).
It seems time to move to the newer, more "sync"-ish tools available for Dropbox, Box, GoogleDrive, iCloud Drive, OneDrive, etc. In fact, I think it is overdue (I'm spending too much time chasing down bugs using old, deprecated APIs provided by these services). This would be a major change to how files are managed in iRhino 3D. You would now likely have folders in iRhino 3D for each of the cloud services and these would show all the 3dm files you current are syncing...no more "Download again" from the file-info screen...whenever these files changed "in the cloud" they would update in iRhino 3D, etc.
Ok, now my question: How valuable is keeping the current (old) behavior where you add a model from a list of files and update on-demand?
Keeping the old behavior and adding the new would be very complicated and potentially confusing. Given that iRhino 3D gets less attention than it deserves, I would like to spend more of our time adding features like view-styles, curves, and annotation tools, and less time maintaining cloud-service integration.