Documentation
RPGM executes RPGM applications developed with RCode. To get started, be sure that R is installed, as it is not provided with RPGM.
Download and install RPGM. R should be detected, if not, update the R path through File -> Settings.
RPGM works as a standalone software. The developpers make the RPGM applications in RCode in an RPGM project.
An RPGM application is composed of several files:
- A settings file (.ppro): in which global properties are defined.
- Sequence files (.pseq): the workflow (the steps) of the application are drawn with a chartflow.
- Graphical User Interfaces file (.pgui): the end-user interacts with the application through an interface, which the link between the end-user and R, and is composed of widgets.
- R files: the R code to be executed, see RCode R Editor.
To start with the developement of RPGM applications, several turotials are available:
- Getting started: the main mechanic of an RPGM application is fully explained, the one to start with.
- Dynamism & Layout: to create better RPGM applications, we look how we can make them dynamic (a modification of a widget or a click on a button can update the current interface). Moreover, the layout widgets are introduced.
- Plotly: a tutorial dedicated to the graph widget.
- CSS: a simplifed langage for styling every widget or graphical user interface with (almost) no limit. Can be used in several ways in RPGM, explained through the tutorial.
An RPGM application can be built with no code for the graphical user interfaces. However, a full API is provided in order to make them dynamic, to create Excel outputs or to access to the CSS properties the the application.
- R GUI functions: to dynamically manage the GUI.
- R RPGM functions: to manage the RPGM application.
- R Script functions: to manage the script, essentialy to provide information to the user about the script execution.
- R XLSX functions: to create an Excel output.
- CSS Reference: the list of the classes used in RPGM, to customize them.
- Widget Properties: the list of the of the properties of the widgets which can be changed, dynamically.
- Widget Types: the names of the types and subtypes of all widgets.