Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Integration: Difference between revisions

From triplescripts.org wiki
Content added Content deleted
(Created page with "Triple scripts can run in the browser today, by design. (And, of course, from the terminal using NodeJS—provided that's the command-line environment the author targets by i...")
 
(→‎VSCode: clarify comparison to browser)
 
Line 3: Line 3:
== VSCode ==
== VSCode ==


VSCode alone cannot run "raw" triple script bundles, but it's within the realm of possibility that a developer can provide an extension derived from their triple script, similar to the same way that triple scripts target the browser today. It's highly desirable, especially for the [[Build Manifesto]] that in the future this change—so that VSCode gain the ability to run arbitrary raw bundles, e.g. simply by pointing at one. This ''should'' be possible using an extension, but there has been no work on this so far.
VSCode alone cannot run "raw" triple script bundles like the browser *or NodeJS) can, but it's within the realm of possibility that a developer could provide an extension derived from their triple script. It's highly desirable, especially for the [[Build Manifesto]] that in the future this change—so that VSCode gain the ability to run arbitrary raw bundles, e.g. simply by pointing at one. This ''should'' be possible using an extension, but there has been no work on this so far.


Ideal VSCode integration could use [[selective reification]] to provide optional inspectors, etc.
Ideal VSCode integration could use [[selective reification]] to provide optional inspectors, etc.

Latest revision as of 22:12, 18 June 2020

Triple scripts can run in the browser today, by design. (And, of course, from the terminal using NodeJS—provided that's the command-line environment the author targets by including the necessary support modules; all triplescripts.org work so far has focused almost exclusively on NodeJS during the proofing stage, for pragmatic reasons.)

VSCode[edit]

VSCode alone cannot run "raw" triple script bundles like the browser *or NodeJS) can, but it's within the realm of possibility that a developer could provide an extension derived from their triple script. It's highly desirable, especially for the Build Manifesto that in the future this change—so that VSCode gain the ability to run arbitrary raw bundles, e.g. simply by pointing at one. This should be possible using an extension, but there has been no work on this so far.

Ideal VSCode integration could use selective reification to provide optional inspectors, etc.

It's just as likely, whether intentional or not, that the VSCode team (or the wider developer community) ends up embracing and extending triplescripts.org's initiatives and effectively salts the ground for us, however...

Gnome Shell[edit]

Gnome ships with the ability to run JS apps today. In fact, Gnome Shell itself is written in JS.

GJS is also a candidate for a system backend as an alternative to NodeJS, as well as an an alternative to the browser (using embedded WebKit). There has been very little experimentation on a "SystemG" so far; we've opted to focus on NodeJS up until now, for stability. The best course of action for work on SystemG at this point would be to focus on Gnome as shipped with Ubuntu 20.04 LTS.

Further integration[edit]

Cookies help us deliver our services. By using our services, you agree to our use of cookies.