||2 months ago|
|assets||2 months ago|
|doc||2 months ago|
|examples||2 months ago|
|scripts||2 months ago|
|src||2 months ago|
|.gitignore||2 months ago|
|.rustc_info.json||2 months ago|
|.rustdoc_fingerprint.json||2 months ago|
|CHANGELOG.md||2 months ago|
|CONTRIBUTING.md||2 months ago|
|Cargo.lock||2 months ago|
|Cargo.toml||2 months ago|
|LICENSE||2 months ago|
|README.md||2 months ago|
SchemeScript is now called BluePrint, no need to worry though - it only changed its name.
The official BluePrint Git Repository is hosted on codeberg.org, but it is also mirrored to GitLab and GitHub.
Github Pages is used to host the official Webpage.
Note that most BluePrint features have not been implemented at this point, thus making production use impossible.
- Write your own: Unsatisfied by the default BluePrint commandset? - just use the library in your own project and add your own commands, keywords and macros!
- Rustc, Cargo
NOTE: At this point there are no prebuild binaries available.
To install the BluePrint Compiler (bps) you have to download or clone the git repository,
on Linux this can be achived by running the following command:
git clone https://codeberg.org/comcloudway/blueprint
(NOTE: Some distros don't ship with git installed by default, so you have to install it yourself)
After successfully cloning the sources, it is time to build the bps binary.
This is as simple as running
cargo build --release.
Your basically good to go now and your binary can be found in the newly created ./target/ folder, but the bps command is not available system-wide yet.
To achive this you have to put the file in your $PATH.
Assuming that you have added ~/.local/bin/ to your path,
the command could look something like this:
ln $PWD/target/release/blueprint ~/.local/bin/bps
Now you should be able to run bps an get an errror message, explaining you that you are missing some arguments.
The next chapter is going to focus on the basic usage of the command line utility
Using the BluePrint Compiler
BluePrint Language Documentation
The following article will focus on non-standard implementations.
The rust code is documented using rustdoc and a partially up-to-date version of the generated documentation can be found in the doc/ folder.
The hosted Version can be found hosted on Github Pages