As an editor developer, I have often desired a standardized "open" activity. That way, it would be easier to integrate with 3rd-party file browsers.
IMO the "open" activity should possess at least these parameters: - type: the file's mimetype - blob: the file's contents - filename: optional string; the file's full name (e.g. "test.docx") - readonly: optional boolean; whether the editor can make changes If we want to make the activity really powerful, it could pass a File or FileHandle object. This would allow the editor to access file attributes and read it properly (https://developer.mozilla.org/docs/Web/API/FileReader). In this case, we could omit all other parameters (except possibly readonly). -- Joshua Smith Plinth Laboratories On Fri, Nov 13, 2015 at 8:35 AM, Tfe Server <[email protected]> wrote: > Hello all, > > (Sorry if i didn't post the message in the right place) > > I am reading the MozActivity API, and i didn't find the way to open an > external editor, and fetch the result when done. > > The goal is to open a MozActivity with a blob, and get the result to save > it to a cloud storage. > > Maybe someone here has an idea for this problem? > > Thanks for your help, > > -- > tfe > > > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
