Rename Palette to FRAME (#4182)

* palette -> frame

* PALETTE, Palette -> FRAME

* Move folder pallete -> frame

* Update docs/Structure.adoc

Co-Authored-By: Benjamin Kampmann <ben.kampmann@googlemail.com>

* Update docs/README.adoc

Co-Authored-By: Benjamin Kampmann <ben.kampmann@googlemail.com>

* Update README.adoc
This commit is contained in:
Shawn Tabrizi
2019-11-22 19:21:25 +01:00
committed by GitHub
parent 68351da29b
commit c9175b59ff
206 changed files with 485 additions and 483 deletions
+10 -10
View File
@@ -11,7 +11,7 @@ Substrate is split into multiple levels with increasing opinion and decreasing f
* primitives
* client
* PALETTE (formerly `srml`)
* FRAME (formerly `srml`)
Putting all these components together we have:
@@ -35,23 +35,23 @@ In the lowest level, Substrate defines primitives, interfaces and traits to impl
* _found in_: `/client`
* _crates prefix_: `substrate-`
* _constraints_:
** crates may not (dev-)depend on any `palette-`-crates
** crates may not (dev-)depend on any `frame-`-crates
In the client you can find a set of crates to construct the outer substrate-node, implementing outer runtime interfaces, thus it depends on `runtime`. It provides the outer building blocks like transaction queue, networking layer, database backend, full* and light-client support.
=== PALETTE (formerly `srml`)
=== FRAME (formerly `srml`)
* _found in_: `/palette`
* _crates prefix_: `palette-` and `pallet-`
* _found in_: `/frame`
* _crates prefix_: `frame-` and `pallet-`
* _constraints_:
** all crates that go on chain must be `[no_std]`
** must not (dev-)depend on anything in `/client`
PALETTE is a set of modules that implement specific transition functions and features one might want to have in their runtime.
FRAME is a set of modules that implement specific transition functions and features one might want to have in their runtime.
_Pallets_ are individual modules within _Palette._ These are containers that host domain-specific logic. They have the `pallet-` prefix. For example, `pallet-staking` contains logic for staking tokens.
_Pallets_ are individual modules within _FRAME._ These are containers that host domain-specific logic. They have the `pallet-` prefix. For example, `pallet-staking` contains logic for staking tokens.
There are a few crates with the `palette-` prefix. These do not contain domain-specific logic. Rather, they are the main Palette support infrastructure. These are:
There are a few crates with the `frame-` prefix. These do not contain domain-specific logic. Rather, they are the main FRAME support infrastructure. These are:
- Executive
- Metadata
@@ -79,7 +79,7 @@ We also provide some binaries pulling from the components creating full applicat
* _found in_: `/bin/node`
The default (testing) application pulling together our recommended setup of substrate-client with a wasm-contracts-supporting palette-runtime. The node pulls it all together, constructs the (upgradable) runtime, and wires up the client around it. You can find an example client, which includes a full wasm-contracts chain in `node`. This is also what is being built and run if you do `cargo run`.
The default (testing) application pulling together our recommended setup of substrate-client with a wasm-contracts-supporting frame-runtime. The node pulls it all together, constructs the (upgradable) runtime, and wires up the client around it. You can find an example client, which includes a full wasm-contracts chain in `node`. This is also what is being built and run if you do `cargo run`.
==== Node Template
@@ -99,7 +99,7 @@ Subkey is a client library to generate keys and sign transactions to send to a s
....
+---------------+ +----------------+
| | | |
| runtime +<------+ palette |
| runtime +<------+ frame |
| | | |
+------+-----+--+ +-------------+--+
^ ^ ^