This is a more meaningful path.
[Added]
- User-supplied JavaScript files can be put into
[Added]
- User-supplied JavaScript files can be put into
- ~/.config/lariza/scripts. "hints.js" is one such script, it's
+ ~/.config/lariza/user-scripts. "hints.js" is one such script, it's
bundled with the main application, but must be activated manually.
v19.05 2019-05-05
bundled with the main application, but must be activated manually.
v19.05 2019-05-05
const gchar *entry = NULL;
GDir *scriptdir = NULL;
const gchar *entry = NULL;
GDir *scriptdir = NULL;
- base = g_build_filename(g_get_user_config_dir(), __NAME__, "scripts", NULL);
+ base = g_build_filename(g_get_user_config_dir(), __NAME__, "user-scripts", NULL);
scriptdir = g_dir_open(base, 0, NULL);
if (scriptdir != NULL)
{
scriptdir = g_dir_open(base, 0, NULL);
if (scriptdir != NULL)
{
.\" --------------------------------------------------------------------
.SH "USER-SUPPLIED JAVASCRIPT FILES"
After a page has been successfully loaded, the directory
.\" --------------------------------------------------------------------
.SH "USER-SUPPLIED JAVASCRIPT FILES"
After a page has been successfully loaded, the directory
-\fI~/.config\:/lariza\:/scripts\fP will be scanned and each file in it
-ending with \fB.js\fP will be run as a JavaScript file in the context of
-said page.
+\fI~/.config\:/lariza\:/user-scripts\fP will be scanned and each file in
+it ending with \fB.js\fP will be run as a JavaScript file in the context
+of said page.
.P
During development, you will most likely want to run \fBlariza\fP with
$\fBLARIZA_ENABLE_CONSOLE_TO_STDOUT\fP enabled.
.P
During development, you will most likely want to run \fBlariza\fP with
$\fBLARIZA_ENABLE_CONSOLE_TO_STDOUT\fP enabled.