I developed a bound script with a UI accessible from a menu extension and clickable dropdown items embedded in a google doc file. The purpose of the script is to transition from the starting document template, allow team collaboration and editing, and after team approval, transition the final edit of the google doc into a pdf file for storage in the team archive.
As a bound script, this implementation works partially and clumsily because the script extension does not always persist through derivative documents, and cannot programatically close the parent doc editor and open another editor instance for the child document. I am hoping that changing the script platform from bound to unbound might enable a higher level of process control. What I have in mind is the following:
- a persistent popup dialog which, given a folder name or ID, would invoke a google drive file selector,
- after selection of a google doc file, enable simple document editing operations already implemented in the bound script,
- after custom editing of the new document, upon a button click perform the file copying/moving operations already implemented in the bound script, and
- close the edit window of the parent document and open a new edit window for the child document.
Any unbound script examples or guidance in how to implement the file selector and edit open/close functions would be appreciated.
Thanks.