You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tried bundling Warp by placing it in the common folder, and that works fine.
One possible plan of action is to include multiple apps into an apps folder on initialization (cloning them from GitHub). These apps could include Warp, mashlib, etc.
We would implement this as follows:
in multi-user mode, place apps on the server's account
in single-user mode, place apps on the user's account
This would require a modification to server-config.js with an extra initializeApps function, that is called from ensureWelcomePage.
I counter-propose using the full local databrowser instead of warp,
as it gives much more functionality for all kinds of data
it avoids the problem of the origin of the web app need ing to be
I suggest an upgrade of the server pull in the latest mashlib.js and databrowser.html, but making sure that if the user has configured their server to use their own specific databrowser file, that config is not overwritten by the server upgrade.
I suggest both the small HTML file and the large JS file are provided on the server. An alternative would be for us to serve the JS file from a solid.github.io etc -- a place we control and upgrade.
Regarding using the full databrowser, my two cents would be to not enable this by default, for the following reasons:
I think it is more complicated to use than Warp, and might not be suitable for everybody.
Since it feels more like a full application than Warp, it might give people the impression that databrowser = Solid.
For the last point, a redirect to a public space (such as indeed solid.github.io) might change that impression for some users. This is also what currently happens with Warp.
Activity
RubenVerborgh commentedon Aug 11, 2017
Alternative suggested by @dmitrizagidulin: bundle Warp with node-solid-server.
RubenVerborgh commentedon Aug 11, 2017
I just tried bundling Warp by placing it in the
commonfolder, and that works fine.One possible plan of action is to include multiple apps into an
appsfolder on initialization (cloning them from GitHub). These apps could include Warp, mashlib, etc.We would implement this as follows:
appson the server's accountappson the user's accountThis would require a modification to
server-config.jswith an extrainitializeAppsfunction, that is called fromensureWelcomePage.timbl commentedon Aug 13, 2017
I counter-propose using the full local databrowser instead of warp,
I suggest an upgrade of the server pull in the latest mashlib.js and databrowser.html, but making sure that if the user has configured their server to use their own specific databrowser file, that config is not overwritten by the server upgrade.
I suggest both the small HTML file and the large JS file are provided on the server. An alternative would be for us to serve the JS file from a solid.github.io etc -- a place we control and upgrade.
RubenVerborgh commentedon Aug 14, 2017
Another suggestion is to fix Warp (linkeddata/warp#23).
RubenVerborgh commentedon Aug 14, 2017
Regarding using the full databrowser, my two cents would be to not enable this by default, for the following reasons:
For the last point, a redirect to a public space (such as indeed solid.github.io) might change that impression for some users. This is also what currently happens with Warp.
RubenVerborgh commentedon Sep 1, 2017
Proposal: use #567 (Data Browser).
Use data browser for containers as well.
RubenVerborgh commentedon Sep 3, 2017
Data Browser proposal implemented in #573.
Use data browser for containers as well. (#573)