Remove Charcoal references from the code for now

Author: Keavon

Cargo.lock

@@ -2,7 +2,6 @@
 members = [
 	"editor",
 	"graphene",
-	"charcoal",
 	"proc-macros",
 	"frontend/wasm",
 ]

Cargo.toml

@@ -4,13 +4,12 @@ This is a great place to start learning about the Graphite codebase and its arch
 
 ## Core libraries
 
-Graphite's core rust codebase is split into three reusable libraries:
+Graphite's core rust codebase is split into two reusable libraries:
 
 - Editor
 - Graphene
-- Charcoal
 
-Each depends on its successor in the list. These are used internally but also intended for usage by third parties through Rust or linked by a project in C, C++, or another language.
+The Editor depends on Graphene, but Graphene can also be used alone. These are used internally but also intended for usage by third parties through Rust or linked by a project in C, C++, or another language.
 
 ## Code structure
 
@@ -25,6 +24,4 @@ The main modules of the project architecture are outlined below. Some parts desc
 - **Graphite Editor (Backend)**: `/editor/`  
   Used by a frontend editor client to maintain GUI state and dispatch user events. The official Graphite editor is the primary user, but others software like game engines could embed their own customized editor implementations. Depends on Graphene.
 - **Graphene (Document Graph Engine)**: `/graphene/`  
-  A stateless library for updating Graphite design document (GDD) files. The official Graphite CLI and editor client backend are the primary users, but this library is intended to be useful to any application that wants to link the library for the purpose of updating GDD files by sending edit operations. Optionally depends on Charcoal if rendering is required.
-- **Charcoal (Asset Render Engine)**: `/charcoal/`  
-  A stateless library (with the help of in-memory and/or on-disk caches for performance) for rendering Graphite's asset graph (GDA) files. The official Graphite CLI and Graphene are the primary users, but this library is intended to be useful to any application that wants to link the library for the purpose of rendering Graphite's asset graphs. For example, games can link the library and render procedural textures with customizable parametric input values.
+  A stateless library for updating Graphite design document (GDD) files. The official Graphite CLI and editor client backend are the primary users, but this library is intended to be useful to any application that wants to link the library for the purpose of updating GDD files by sending edit operations. This also serves as the 2D render engine and this is intended to be useful to any application that wants to link the Graphene library for the purpose of rendering Graphite graphs. For example, games can link the library and render procedural textures with customizable parametric input values.

charcoal/Cargo.toml

@@ -57,7 +57,7 @@ Contributions welcome! If you think of something Graphite would be great for, su
 - Removing translucent watermarks that were applied in the same location to a batch of photos by finding their shared similarities and differences and using that as a subtraction diff
 
 ## Game development
-- Design a GUI for the game and use Charcoal to render the in-game GUI textures at runtime at the desired resolution without scaling problems, or even render it live as data updates its state
+- Design a GUI for the game and use Graphene to render the in-game GUI textures at runtime at the desired resolution without scaling problems, or even render it live as data updates its state
 - Authoring procedural noise-based textures and PBR materials
 
 ## Data visualization
@@ -98,4 +98,4 @@ Contributions welcome! If you think of something Graphite would be great for, su
 - Generating a PDF invoice based on data in a pipeline in a server
 
 ## Industrial control
-- Factory line is examining its fruit for defects. In order to verify the quality, they need to enhance the contrast, automatically orient the image and correct the lighting. They then pass the results into a machine learning algorithm to classify, and sometimes need to snoop on the stream of data to manually do quality control (ImageMagick or custom Python libraries are often used for this right now)
+- Factory line is examining its fruit for defects. In order to verify the quality, they need to enhance the contrast, automatically orient the image and correct the lighting. They then pass the results into a machine learning algorithm to classify, and sometimes need to snoop on the stream of data to manually do quality control (ImageMagick or custom Python libraries are often used for this right now)

charcoal/src/lib.rs

@@ -64,7 +64,6 @@ TODO: Add more to make a comprehensive list, finish writing definitions, separat
 - ## Graphite Editor (Frontend)
 - ## Graphite Editor (Backend)
 - ## Graphene (Document Graph Engine)
-- ## Charcoal (Asset Render Engine)
 - ## Trace
 - ## Path
 - ## Shape

docs/codebase/README.md

@@ -57,12 +57,7 @@ module.exports = {
 						crateDirectory: path.resolve(__dirname, "wasm"),
 						// Remove when this issue is resolved: https://github.com/wasm-tool/wasm-pack-plugin/issues/93
 						outDir: path.resolve(__dirname, "wasm/pkg"),
-						watchDirectories: [
-							path.resolve(__dirname, "../editor"),
-							path.resolve(__dirname, "../graphene"),
-							path.resolve(__dirname, "../charcoal"),
-							path.resolve(__dirname, "../proc-macros"),
-						],
+						watchDirectories: ["../editor", "../graphene", "../proc-macros"].map((folder) => path.resolve(__dirname, folder)),
 					})
 			)
 			.end();