Questions regarding Inter-Analysis Object Sharing and Custom File I/O Capabilities
Posted: Tue Jan 27, 2026 7:44 pm
Hi everyone,
I am currently developing a module for jamovi and have a couple of specific questions regarding the capabilities of the API and R integration.
1. Persistence and Object Sharing Between Analyses: Is it possible to save an R object from one analysis so that it becomes accessible to a separate analysis (within the same or different module)?
I am aware that standard analyses like ANOVA can save residuals back to the dataset as new columns. However, I am looking to pass arbitrary R objects (rather than just data columns) between analyses. Is there a mechanism to store an object in a shared state that another analysis instance can read, or are all analyses strictly isolated, meaning communication is limited solely to modifying the Data (spreadsheet)?
2. File Saving Capabilities and GUI Access: What are the limitations regarding File I/O within a module? Specifically, I would like to allow the user to save a specific internal object to a custom file format.
I have successfully tested taking a file path as an input string and saving to it. However, I would like to know if it is possible to trigger a native "Save As" window (GUI) from within the module options? I want users to be able to browse their directories and specify a filename and type interactively, rather than typing a path manually. Is this level of OS/GUI access permitted or supported in the current module framework?
Any guidance or examples would be greatly appreciated!
Thanks.
I am currently developing a module for jamovi and have a couple of specific questions regarding the capabilities of the API and R integration.
1. Persistence and Object Sharing Between Analyses: Is it possible to save an R object from one analysis so that it becomes accessible to a separate analysis (within the same or different module)?
I am aware that standard analyses like ANOVA can save residuals back to the dataset as new columns. However, I am looking to pass arbitrary R objects (rather than just data columns) between analyses. Is there a mechanism to store an object in a shared state that another analysis instance can read, or are all analyses strictly isolated, meaning communication is limited solely to modifying the Data (spreadsheet)?
2. File Saving Capabilities and GUI Access: What are the limitations regarding File I/O within a module? Specifically, I would like to allow the user to save a specific internal object to a custom file format.
I have successfully tested taking a file path as an input string and saving to it. However, I would like to know if it is possible to trigger a native "Save As" window (GUI) from within the module options? I want users to be able to browse their directories and specify a filename and type interactively, rather than typing a path manually. Is this level of OS/GUI access permitted or supported in the current module framework?
Any guidance or examples would be greatly appreciated!
Thanks.