jaspModuleTemplate install
Is the jaspModuleTemplate still current for its installation in JASP 0.95.4? I've attempted to install & run the template module using documented methods, and others. Get a "Waiting for initialization" hang, at best, R engine connection fail, even if UI widgets appear. Maybe if there is any updated info I need to know, I best leave the question at that.
Otherwise I could expand on what I've tried and their specific results (e.g. "Install Developer Module" method, via Preferences -> Advanced; via renv, building via RStudio project or separately within JASP R console; "Install Module" method with manual bundling of the .jaspmodule; manual copy into %APPDATA%\JASP\JASP\modules). I could also document the checks per method (e.g., renv::status() and library(jaspModuleTemplate) ok, jaspBase and jaspGraphs linked; simple "print-to-file" R functions).
Have used AI to scour JASP documents and check each step and suggest others, and review log files. Their diagnosis is "There is a fundamental breakdown in how JASP handles local developer paths", or "The "Developer Mode" appears to be broken for local builds, as the engine cannot maintain a stable link to the package it supposedly just "installed."" Seems implausible but I should ask before I keep going. Thanks in advance.
Comments
Is the jaspModuleTemplate still current for its installation in JASP 0.95.4? I've attempted to install & run the template module using documented methods, and others. Get a "Waiting for initialization" hang, at best, R engine connection fail, even if UI widgets appear. Maybe if there is any updated info I need to know, I best leave the question at that.
Otherwise I could expand on what I've tried and their specific results (e.g. "Install Developer Module" method, via Preferences -> Advanced; via renv, building via RStudio project or separately within JASP R console; "Install Module" method with manual bundling of the .jaspmodule; manual copy into JASP\modules). I could also document the checks per method (e.g., renv::status() and library(jaspModuleTemplate) ok, jaspBase and jaspGraphs linked; simple "print-to-file" R functions). Most methods don't even get the module name showing anywhere in the "+" menu.
Have used AI to scour JASP documents and check each step and suggest others, and review log files. Their diagnosis is "There is a fundamental breakdown in how JASP handles local developer paths", or "The "Developer Mode" appears to be broken for local builds, as the engine cannot maintain a stable link to the package it supposedly just "installed."" Seems implausible but I should ask before I keep going. Thanks in advance.
Confirming that this issue remains in the new version: I'm unable to get the jaspModuleTemplate working in JASP 0.96 (Windows) using Developer Mode.
The problem: The first step according to the JASP documentation is to install the template. But doing so, as it describes, compiling the template with R CMD INSTALL or install.packages(..., type="source") fails because jaspBase and jaspGraphs are not available (they're internal JASP-only packages). This includes using JASP’s R console , which has path issues anyway (cannot setwd(), defaults to phantom C:/Users/CRAN/Documents), so every renv::activate(...) or path-based command fails.
So using the button labelled “Install Developer Module” expects the installed package. It doesn't actually "install" — it assumes the module is already compiled; it can't find the files it needs, otherwise, what comes within the inst/ folder. You can reorganise files so you can give it what looks like an installed package (moving contents out of inst), to get this button doing something, listing the module so that the QML GUI elements can be displayed, but no R code works, so there's no developer mode really available this way.
Is an updated workflow or fix planned?
Details:
JASP 0.96.10.0 (both .exe and via the store)
Windows
JASP internal R: 4.5.2
Tried fresh clones, cache clears, matching R 4.5.2, parent vs direct paths, etc.
Thanks!
Hello rvgardt,
This is really more of an issue for our GitHub page. I have attended Pablo to your question. We also run a "Module developers" Mattermost channel, btw. We have recently updated our workflows re. modules. I will leave it up to Pablo to send you the correct documents!
EJ