Simian GUI Documentation v2.2.1

The ResultFile component

The ResultFile component is the counterpart of the File component, that allows the user to download result files created by the back-end. In comparison to the guiDownload functionality, there are several differences.

• The ResultFile component is able to show multiple download links in a list, instead of being just a download button.
• The ResultFile component does not block the user interface during the download. It also does not trigger an event in the back-end.
• For deployed applications, the file is downloaded via the portal webserver instead of being part of the submission data. This makes the ResultFile component suitable for downloading larger files.

There are two modes of operation:

• base64: In base64 mode, the selected files are base64 encoded and put in the submission data. This is the default mode for local applications.
• portal: In portal mode, the selected files are uploaded to the portal webserver. Download URLs are provided in the submission data. This is the default mode for deployed applications.

In addition to the properties and methods listed below, this component inherits properties and methods from the superclass Component. For example, any ResultFile component has a label and tooltip property even though these are not explicitly listed here.

Properties

Methods

Upload method

The input of the static upload method are:

• filePaths: Array/list of paths to files to upload
• mimeTypes: Array/list of MIME-types corresponding to the files to upload
• metaData: Metadata struct/dict
• payload: The payload struct/dict
• key: Key of the ResultFile component
• Parent/NestedForm: Optional inputs for further specifying what ResultFile component is used to upload the files
• FileNames: Optional input for specifying an array/list of file names to display in the component³
• Append: Optional input to control whether previously uploaded files remain listed. Per default the list is cleared before the new file is uploaded.

Example

In the guiEvent code snippets below a simple struct/dict is written to a .json file in the session folder of the back-end and made available in the front-end.

% Write a struct to a .json file in the back-end's session folder.
sessionFolder   = utils.getSessionFolder(metaData, "Create", true);
niceName        = "example_table.json";

fileName = fullfile( ...
    sessionFolder, ...
    sprintf("example_table-%s.json", matlab.lang.internal.uuid()));

fid = fopen(fileName, 'w');
fprintf(fid, '%s', jsonencode(struct("hello", "world")));
fclose(fid);

% Upload the created .json file to make it available in the front-end.
payload = component.ResultFile.upload( ...
    fileName, ...
    "application/json", ...
    metaData, ...
    payload, ...
    "result_file_key", ...
    'FileNames', niceName);

# Write a dict to a .json file in the back-end's session folder.
session_folder = utils.getSessionFolder(meta_data, create=True)
nice_name = "example_table.json"
file_name = os.path.join(session_folder, f"example_table-{uuid.uuid4()}.json")

with open(file_name, 'wt') as f:
    json.dump({"hello": "world"}, f)

# Upload the created .json file to make it available in the front-end.
component.ResultFile.upload(
    file_paths=[file_name],
    mime_types=["application/json"],
    meta_data=meta_data,
    payload=payload,
    key="result_file_key"
    fileNames=[nice_name]
)

See also

• File for uploading files.