Here you can check out AmigaOS 3.x with Google Drive handler support.
The author claims that Dropbox support is next on his list.
https://www.youtube.com/watch?v=8v9guAQdbDA&feature=youtu.be
Arrgh - I was just trying to post the news as "Amiga Software News"-item and was wondering why it didn't appear in the "Amiga Software News"-section after clicking the "Submit"-button, when I noticed this thread already existed.
I'll post my 'news-item' nevertheless here in this thread, as it contains some additional information from the e-mails Norbert Kett and I exchanged since yesterday:
Norbert Kett,
chief programmer at 4Flash, has released an
Google Drive Handler for AmigaOS 3.x.
"Google Drive Handler" for AmigaOS 3.x is a Dos handler, allowing easy access to your Google Drive storage (Gmail account required).
Support for "Drop Box" and "Google Cloud Print" is planned as well:
- "Drop Box Handler" is under development. While a Gmail address is required for Google Drive, this will be a bit different for Drop Box later on. Norbert Kett's intention is to release the "Drop Box Handler" next month.
- "Google Cloud Print" will be an easy printing solution for Amiga. You can print documents with drag&drop, and no printer driver is required. This is sort of network printing - only Google offers this printing support at the moment.
"Google Drive Handler" for AmigaOS 3.x is based on
- libCurl v7.37.1 and
- OpenSSL v0.9.8zh. This version of OpenSSL contains all security patches until December 3rd, 2015, but only supports TLS 1.0.
OpenSSL v1.0.2e (also included in this distribution) is the latest, full featured SSL library, but requires a fast 68k machine (68040+).
Without licence key, the handler acts as a read only volume, and document exporting is disabled. To obtain the licence key, please contact Norbert Kett using this email address:
anchor@rocketmail.com. Once you obtained a licence you will get full access to all his upcoming handlers. The cost of the license is 10 EUR. With one licence, you can use all his upcoming "REST API based products" on all Amiga like platforms without limitation.
"REST API" is an industry standard for app <-> server communication. It is getting more popular. Some services for example:
Google Drive, Google Cloud Printing, DropBox, Microsoft One-Drive, Amazon Cloud, PayPal, Twitter, FaceBook, and many others.
It may also work on AROS Vision, and on MorphOS too. However, it has not been fully tested yet on these platforms (MorphOS will get a native version separately).
Only porting to OS4 is problematic, since Norbert Kett currently has no hardware to run OS4 and test the handler with.
An OS4 emulation is not enough - a real machine is required. Norbert tried to port it to OS4 in UAE, but when he tried the handler on a real Amiga with OS4, some issues arose that weren't perceivable on the emulated machine.
So everybody wanting OS4 ports of this software should seriously consider to support him with OS4 capable hardware - at least as a loan!
Further details:
Short: Google Drive handler for AmigaOS 3.x
Author: Norbert Kett (anchor@rocketmail.com)
Type: comm/tcp
Version: 0.4
Requires: 68020
Architecture: m68k-amigaos >= 3.0.0
DESCRIPTION
This is a Dos handler allowing easy access to Your Google Drive storage.
REQUIREMENTS
AmigaOS 3.x, 68020 28MHz, 8M fast RAM, with Internet connection. The
handler has been tested on OS3.1, and OS3.9. It may also work on AROS
Vision, and on MorphOS too. However, it has not been fully tested yet
on these platforms. (MorphOS will get a native version separately.)
LIMITATIONS
Without licence key, the handler acts as a read only volume, and document
exporting is disabled. To obtain the licence key, please contact me using
my email address. Once licence obtained, full access to all my upcoming
handlers is enabled. (Dropbox and Google Cloud Print are planned as well)
The cost of the license is 10 EUR.
INSTALLATION
Since there is no installer yet, You need to follow these steps:
1. Copy the entire 'Google' folder to your Devs: from the archive.
2. Visit the following site with a modern browser: https://goo.gl/1K3xoq
and copy the given client code into Devs:Google/_client_code
(Please note: Every time when You ask new client code, You must delete
Devs:Google/_access_token and Devs:Google/_refresh_token files if they
are exist!)
3. Add the following lines to Your user-startup:
;BEGIN Google
Assign SSLROOT: Devs:Google/.sslroot
Mount GOOGLE: from Devs:Google/google.mountlist
;END Google
(If somehow You already have SSLROOT: assign, skip that line)
That's all. Let's check your installation. Reboot, and open a new
CLI window. Type: list google:
If everything is fine, after a few seconds You should see the list of
files and folders of your GD root.
If You want to see GD icon on your Workbench, upload one from
Devs:Google/.data folder to Your GD root, and rename it to Disk.info.
Disk1.info is a classic icon format for OS3.1, Disk2.info is for
Peter Keunecke's icon.library, while Disk3.info is a png image for
OS3.9. In order to upload files You'll need to use a full version
of the handler, or a modern browser.
COMPONENTS
GD handler is based on libCurl (v7.37.1), and OpenSSL (0.9.8zh)
This version of openssl contains all security patches until
2015.12.03, but supports only TLS 1.0. Use this handler at Your
own risk. If You have stronger CPU (68040/68060/Apollo FPGA),
You can try the handler built with the latest, full featured,
but slower openssl. (v1.0.2e) Just rename google-drive-handler_102e
to google-drive-handler in Your Devs:Google folder.
You can check the components, and the licence status with this
command: list google:@about
The SSL connection and data transmission is a relatively slow on
68k based machines. GD handler worked on my boosted ACA1221 with
68020 28MHz, but it wasn't too fast. For the fluent operating a
68030 is strongly recommended.
TECHNICAL RESTRICTIONS
- GD does not show the file size of the document type files. The zero
file size may cause problems, thus the handler showing a huge file size
for exportable documents. The real size is determined only at the export
time. File managers without EOF support are unable to handle it. Dopus
can't handle EOF, and its default I/O buffer size is too small for
networking. I recommend FileMaster, or Workbench for GD. FileMaster uses
big enough (and adjustable) I/O buffer size by default, and handles EOF.
- GD does not allow modification of file contents. If You want to modify
a file, make a local copy first, and when You have finished, upload it
to your GD.
- GD expects the exact file size for every upload. If You creating a new
file, it is empty. Due to this, if You uploading something, the content
will be stored into a buffer, and the real upload will occur when the
file has been closed. The maximum size of the uploaded file is limited
by amount of free RAM.
PLANNED FEATURES
- OCR (automatic text document export from image, during upload)
- Shared file support
- icon ghosting
- thumbnails as icons for NG systems
- 64 bit actions for NG systems
- change detection (if You operate with GD on other machine too)
- MOS, AROS x86, OS4 port (I have no OS4 capable machine yet)
VERSION
This handler is still in an early stage of development, far from the
mature state. It may contain bugs. Please consider this release as a
public beta. Any feedback is welcomed.
Thanks to:
- BSzili,
- Viktor Soponyai alias dh1 from Amiga Mania Magazin,
- PMonster,
- Sir_Lucas.
.
.
.
