chromex.app.file-browser-handler

Liking cljdoc? Tell your friends :D

Mostly clj/s.
Exceptions indicated.

api-table^clj
gen-call^clj
gen-wrap
on-execute*^cljs
select-file
select-file*^cljs
tap-all-events
tap-on-execute-events

clj

Use the chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable users to upload files to your website.

available since Chrome 36
https://developer.chrome.com/apps/fileBrowserHandler

Use the chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable
users to upload files to your website.

  * available since Chrome 36
  * https://developer.chrome.com/apps/fileBrowserHandler

raw docstring

api-table^clj

source

gen-call^clj

source

gen-wrap^clj/smacro

(gen-wrap kind item-id config & args)

source

on-execute*^cljs

(on-execute* config channel & args)

source

select-file^clj/smacro

(select-file selection-params)

Prompts user to select file path under which file should be saved. When the file is selected, file access permission required to use the file (read, write and create) are granted to the caller. The file will not actually get created during the function call, so function caller must ensure its existence before using it. The function has to be invoked with a user gesture.

|selection-params| - Parameters that will be used while selecting the file.

This function returns a core.async channel of type promise-chan which eventually receives a result value. Signature of the result value put on the channel is [result] where:

|result| - Result of the method.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via chromex.error/get-last-error.

https://developer.chrome.com/apps/fileBrowserHandler#method-selectFile.

Prompts user to select file path under which file should be saved. When the file is selected, file access permission
required to use the file (read, write and create) are granted to the caller. The file will not actually get created during
the function call, so function caller must ensure its existence before using it. The function has to be invoked with a user
gesture.

  |selection-params| - Parameters that will be used while selecting the file.

This function returns a core.async channel of type `promise-chan` which eventually receives a result value.
Signature of the result value put on the channel is [result] where:

  |result| - Result of the method.

In case of an error the channel closes without receiving any value and relevant error object can be obtained via
chromex.error/get-last-error.

https://developer.chrome.com/apps/fileBrowserHandler#method-selectFile.

source raw docstring

select-file*^cljs

(select-file* config selection-params)

source

tap-all-events^clj/smacro

(tap-all-events chan)

Taps all valid non-deprecated events in chromex.app.file-browser-handler namespace.

Taps all valid non-deprecated events in chromex.app.file-browser-handler namespace.

source raw docstring

tap-on-execute-events^clj/smacro

(tap-on-execute-events channel & args)

Fired when file system action is executed from ChromeOS file browser.

Events will be put on the |channel| with signature [::on-execute [id details]] where:

|id| - File browser action id as specified in the listener component's manifest. |details| - File handler execute event details.

Note: |args| will be passed as additional parameters into Chrome event's .addListener call.

https://developer.chrome.com/apps/fileBrowserHandler#event-onExecute.

Fired when file system action is executed from ChromeOS file browser.

Events will be put on the |channel| with signature [::on-execute [id details]] where:

  |id| - File browser action id as specified in the listener component's manifest.
  |details| - File handler execute event details.

Note: |args| will be passed as additional parameters into Chrome event's .addListener call.

https://developer.chrome.com/apps/fileBrowserHandler#event-onExecute.

source raw docstring