Google Drive finale

Google Drive potrebbe presto avere un terminale (video)

Lorenzo Quiroli

Google potrebbe accontentare gli utenti più esperti e introdurre un terminale all’interno di Drive su Android. È davvero possibile? Sì, secondo un nuovo teardown dell’ultima versione di Drive, che ne trova delle tracce evidenti.

activity android:exported=”false” android:label=”@string/title” android:name=”com.google.android.apps.docs.drive.shell.TerminalDisplay” android:theme=”@style/Theme.AppCompat” android:windowSoftInputMode=”adjustPan|stateVisible”/>

<string name=”drive_shell_version”>Drive Shell, version 1.0.</string>
<string name=”title”>Drive Shell</string>

<string name=”error_gokart_cannot_fetch”>shell: unable to fetch data from Drive</string>
<string name=”error_gokart_rename”>shell: unable to rename</string>
<string name=”error_gokart_set_parent”>shell: unable to set parent</string>
<string name=”error_gokart_trash”>shell: unable to trash</string>

<string name=”error_invalid_path”><g example=”rm” id=”command”>%1$s</g>: cannot stat <g example=”foo/bar/baz” id=”path”>%2$s</g>: No such file or directory</string>
<string name=”error_make_dir_invalid_path”><g example=”mkdir” id=”command”>%1$s</g>: cannot make directory <g example=”foo/bar/baz” id=”path”>%2$s</g>: No such directory</string>
<string name=”error_missing_operand”><g example=”mdkir” id=”command”>%1$s</g>: missing operand</string>
<string name=”error_move_home_root”><g example=”mv” id=”command”>%1$s</g>: cannot move home or root</string>
<string name=”error_remove_dir_without_recursive”><g example=”rm” id=”command”>%1$s</g>: cannot remove <g example=”foo/bar/baz” id=”path”>%2$s</g>: Is a directory</string>
<string name=”error_remove_home_root”><g example=”rm” id=”command”>%1$s</g>: unable to remove %2$s</string>
<string name=”error_remove_invalid_path”><g example=”rm” id=”command”>%1$s</g>: cannot remove directory <g example=”foo/bar/baz” id=”path”>%2$s</g>: No such directory</string>
<string name=”error_resource_busy”><g example=”mv” id=”command”>%1$s</g>: cannot move – resource busy</string>
<string name=”error_open_resource”><g example=”open” id=”command”>%1$s</g>: cannot open <g example=”foo/bar/baz” id=”path”>%2$s</g></string>

<string name=”help_change_dir”>Change the shell working directory to DIR. The default is ~</string>
<string name=”help_clear”>Clear the terminal screen</string>
<string name=”help_cowsay”>Moo</string>
<string name=”help_echo”>Write the given arguments to the standard output</string>
<string name=”help_exit”>Exit the Drive Shell</string>
<string name=”help_help”>Display information about the built in commands</string>
<string name=”help_list”>List the contents of a folder in Drive</string>
<string name=”help_make_dir”>Make the specified directory</string>
<string name=”help_move”>Rename or move source to destination file or directory</string>
<string name=”help_open”>Open a resource from your Drive account</string>
<string name=”help_print_working_dir”>Print the name of the current working directory</string>
<string name=”help_remove”>Remove the specified file or directory which sends it to trash</string>
<string name=”help_whoami”>Show details about the current user</string>

Basandosi sulle stringhe presenti e sugli altri dati i comandi dovrebbero essere cd, cat,clear, cowsay, echo, exit, help, ll, ls, mkdir, mv, open, pwd, rm e whoami. Se avete familiarità con Linux li avrete già usati, a parte cowsay (la mucca dice), il cui testo di aiuto dice “Moo”.

terminale drive

Forse si tratta di un’interfaccia che rimarrà riservata per gli ingegneri di Google, forse no: ne sapremo di più presto, mentre a seguire vi lasciamo con il video di un piccolo easter egg presente in questa versione di Drive.

Fonte: AndroidPolice
video