I was not aware of this, and this may also be a contributing factor to why removing Dropbox from SmartBASIC may save time and allow Mr. K to add in other things that we would really like to have.
I got the following from a photo app that I use quite regularly today, and was caught off guard by this.
The message:
The old version of the Dropbox platform is being retired on September 28, 2017. The developer of this app has yet to acknowledge the change, so this app may not continue to work in the future.
I know that the Dropbox App has been updated 3 times, and as soon as I get my once a month disability check, I have 190 updates that are waiting that Apple will not allow me to play movies or music I own in the cloud nor will it allow me to update Apps (They will hold all for ransom for .99 cents).
Anyway, I believe we have a good start towards a real solution to removing Drobpx. I just used the D&D Browser to download all the items I needed (source, libs, and images) and the links to files, which I have a prorgram (Resolving URL) that will copy any file from a website to the SmartBASIC IDE).
However, once these were downloaded, it was a manual renaming and copying them to the proper directory(ies) to run them. Once we can come up with a process, which i will write programming specs to take the pieces we have, identify the new coding, and develop a GUI that will allow us to set everything up in one screen and run it, we can work on how to rename or preserve the file name being copied. I noticed that for images, the links do possess the file name. We just need to make changes to parse them out. For source files, we can insist that the first line be something like "REM Program: Compare v1.0.sb", and the program we write when it sees this will create a source file with that name in it.
I know there is a lot of information recently posted by me and others, and I am still reading them, and doing some planning on the items that will work, code we have, code needed to be written, and I am very confident that we can remove Dropbox and use the forum, or maybe even GITHUB or SOURCEFORCE as well as our forum to put all thee assets in one place and run a program that gets them and downloads them.
While SB does not support FTP as a protocol, Rbytes and I have been able to use the HTTPD protocol as a viable replacement. Again, I am very confident we have most if not all the pieces to create a program that will process the files from wherever (right now it all works with the forum) and a solution is close at hand.
So please, read everything, and, I like to write on paper flowcharts of processes and systems, which is what I am doing so I know what features we are misssing. I am very pleased with the participation which has supplied great information, so please continue. No idea is that far fetched, and any idea, even if SB does not support it, may spark other ideas on how to accomplish it. As you can see, everyone has been very constructive and I hope we continue along those lines.
Thank you for taking time out of your busy days, and being disabled/retired, I do have time to try writing proof of concepts to what has been suggested so far. Let's keep the momentum going.
George
PS: If someone else wishes to write the specs on this, it does not have to be me. I'd rather it be a collaberatve effort, and hopefully we can divide the coding up into manageable pieces for anyone who wishes to become part of the team.