Skip to main content

Module file

Module file 

Source
Expand description

What a dialog picks and where a save goes — the shell-typed payloads tool::Action carries. What a path means is one crate down, in blockworx_store::file; opening the dialog is one crate up, in the shell. What the File flow asks for, and what comes back.

Pure data: opening the dialog is the shell’s, since a picker is a platform affordance, and what a path means is blockworx_store::file’s. What is here is the vocabulary crate::tool::Action carries between the two.

What a pick is depends on the picker, so a crate::file::FilePick is a path: a shell whose documents are not files never opens one of these dialogs, and says so by never raising crate::file::FileRequest.

Enums§

FilePick
What a dialog picked, named for what the app does with it — so the dispatcher cannot mistake a container to open for a place to make one.
FileRequest
What the File menu asked a dialog for.
SaveScope
What a Save-as writes: the document whole, or the history through the rev on the canvas.

Type Aliases§

PickReceiver
The channel a pending dialog delivers on: the pick, or None if the user cancelled.