There's plenty of working tools available already. However, we are randomly breaking/finding old broken code and improving things constantly as we push out a model we feel can be competitive. 100% FOSS!
Also, we are going to turn this spec into something that supports a visual editor for games and applications built right into VSCode: Notes
**GraphScript** is a highly customizable, high performance library for creating complex full stack software and library architectures. It's based around graphs hierarchies, event systems, and microservices, with an intuitive composition and node/function indexing tree system for rapid development.
Check out the code in examples for very clear, compelling implementatons that flex our rapidly evolving feature sets. Get in touch at brewster.joshua1@gmail.com if you'd like to contribute and see this evolve.
graphscript is organized by the basic principles of graph theory:
- Graph: These are contained in a shared scope.
- Nodes: There is a hierarchy of objects.
- Connections: Within each shared scope, properties can be linked in order to react to each other.
Beyond these basic concepts, nodes can be direct proxies for generic javascript functions, objects or class instances from any libraries, enabling an intuitive frontend/backend hierarchical organization scheme that can plug right in as an event system for existing object-oriented programs.
See Graphs and GraphNodes for more information.
The basic connectivity framework. You can design entire apps or modules as nested object (or scope) associations with the graph node properties and event system. We've demonstrated dozens of modules in the examples and throughout the source code. Just dump them in a Graph and you can quickly build event systems with a clear readable hierarchy. This isn't a rigid system as you'll see in the examples. Add more GraphScript properties (which we distinguish with a __) using loaders to customize node instantiation behaviors e.g. for spawning a multithreaded app from a fairly simple hierarchical definition for the desired i/o scheme.
See Services for more information.
This forms a microservices layer on top of the graph system. It makes it easier to communicate between separate graphs that track their own properties. We've implemented all kinds of protocols (HTTP, WebRTC, WSS, Event Sources, End-to-End encryption, etc) on top of this to demonstrate the convenience of a graph-based event system for software pipelining.
Included Services contains a reference of the services included in the main graphscript packages.
- Graphs, Services
- Web Workers, including convenient canvas renderer multithreading and MessageChannel pipelining
- WebRTC
- WebSockets
- Event Sources
- Session system for syncing data across connections (e.g. for game servers)
- Router for creating user systems and connection routing by user assocation.
- End 2 End encryption (via
sjcl
)
- Graphs, Services
- Experimental pure nodejs HTTP/HTTPS server for rapid prototyping. Tie requests to graph node properties or use a simple page templating system.
- Websocket server and Websockets (via
ws
) - Server-Sent Events (via
better-sse
) - Child-Processes (still need to add a polyfill for web workers)
- Session system for syncing data across connections (e.g. for game servers)
- Router for creating user systems and connection routing by user assocation.
- End 2 End encryption (via
sjcl
)
- A minimal GraphScript distribution featuring only Graphs, the EventHandler, and the base loaders. Should work in browser and node.js
- User database system made for use with Mongoose/MongoDB. Includes dozens of boilerplate data structures for a simple query system with optional user permissions and access token verification.
- Entity Component System - a semi out-of-date but functional ECS format.
- WebGL plotter, can handle millions of points.
- Node templates (e.g. for use with the remoteGraphRoutes) for receiving data from sensors and stuff.
-
graphscript-services.gpu
: Experimentalgpu.js
plugin. ~500kb, use it with workers for best results. -
graphscript-services.storage
: Some BrowserFS, CSV, and Google Drive utilities. Not very complete.
Want to see this API improve faster? Please contribute or create issues and offer perspective. This repo is mostly a labor of love by Josh, with Garrett swooping in to reality check the actual utility of it from time to time. We want this to API to give you open web super powers, so we can all move on to building much more interesting end products as a community, as well as get more students, engineers, and researchers working in a collaborative development environment. This is the future! Down with knowledge and tool hoarding!
-
device-decoder
- Complex Browser USB and Browser or Native Mobile Bluetooth driver set that is by-default multithreaded using our web worker system. You can use the worker system to create fully-threaded pipelines from the device codec without touching the main thread.