From d1d1b3156de080f4d2b4aff250dbfc720ddf1938 Mon Sep 17 00:00:00 2001 From: Michele Caini Date: Wed, 28 Mar 2018 22:29:01 +0200 Subject: [PATCH] fixed doc for #27 --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 7ddb66c43..76c4cf32b 100644 --- a/README.md +++ b/README.md @@ -23,6 +23,7 @@ * [Snapshot loader](#snapshot-loader) * [Continuous loader](#continuous-loader) * [Archives](#archives) + * [One example to rule them all](one-example-to-rule-them-all) * [View: to persist or not to persist?](#view-to-persist-or-not-to-persist) * [Standard View](#standard-view) * [Single component standard view](#single-component-standard-view) @@ -893,6 +894,8 @@ In particular: Every time such an operator is invoked, the archive must read the next element from the underlying storage and copy it in the given variable. +#### One example to rule them all + `EnTT` comes with some examples (actually some tests) that show how to integrate a well known library for serialization as an archive. It uses [`Cereal C++`](https://uscilab.github.io/cereal/) under the hood, mainly @@ -901,6 +904,9 @@ because I wanted to learn how it works at the time I was writing the code. The code is not production-ready and it isn't neither the only nor (probably) the best way to do it. However, feel free to use it at your own risk. +The basic idea is to store everything in a group of queues in memory, then bring +everything back to the registry with different loaders. + ## View: to persist or not to persist? First of all, it is worth answering an obvious question: why views?