Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

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.

Sign In or Register to comment.