Module attachments 

Mail attachments on a phone (docs/client.md, “Antivirus”). A phone has no antivirus Sioul can call, so none is asked and none is claimed: the words say the file was not checked. The attachment opens in the app you choose, which Android lets read that one file and nothing else of Sioul’s, and “Save…” asks Android where (android/package/src/com/aurelienpierre/sioul/ Attachments.java, AttachmentSave.java). Sioul’s own refusals stand as on a computer: mail set aside keeps its attachments closed, and programs, scripts and installers, Android’s among them, are never opened.

A computer is unchanged (backend::checked_attachment): its antivirus is asked, or you are, when it has none.

Enums

Check 🔒

What stands between an attachment and where it goes.

Statics

SAVING 🔒

The window waiting for Android’s question where to save to be answered.

Functions

check 🔒

The check an attachment gets, from where Sioul runs.

folder 🔒

The folder attachments are written in to be opened: <cache>/sioul/attachments, which Android’s provider may lend from (android/package/res/xml/qtprovider_paths.xml).

kept_closed 🔒

Whether an attachment is kept from opening (it may still be saved): a program, a script, an installer, a shortcut, a disk image (links::is_program, as on a computer); on a phone, Android’s installers too (links::is_phone_program).

open 🔒

The attachment written at file handed to the app you choose (Android asks which, when none is set for its type); the line to show. A copy no app took leaves the cache at once.

opened_line 🔒

What Java’s answer to “open” says, as the status line.

phone 🔒

Whether attachments go the phone’s way: on Android; and in a demo’s pictures of a phone’s screen (SIOUL_GRAB_PHONE with SIOUL_DEMO), so that they show its words. There nothing reaches another app: Android is not there to answer.

save 🔒

Android asked where to save the attachment written at file; the line to show meanwhile. AttachmentSave copies it there, takes it out of the cache and says what became of it (sioul_attachment_saved).

saved 🔒

AttachmentSave’s word (android/main.cpp), once the copy is made or not: {path, name, saved, shown} or {path, name, saved: false, problem}; the status line says it. The copy in the cache goes, saved or not: Java took it out, and here it is taken out again if it stayed. On a thread of Java’s.

saved_line 🔒

What AttachmentSave said once Android’s question was answered, as the status line.

type_of 🔒

The type an app is asked to open, from the name’s extension, as Sioul names the attachments it sends (compose::mime_of): never the type the message claims. Java asks Android’s own table for those this one does not know, and never hands an installer.