4.7 KiB
Singleton Command Object
{{#include ../links.md}}
Usage Scenario
-
A system provides core functionalities, but no driving logic.
-
The driving logic must be dynamic and hot-loadable.
-
A script is used to drive the system and provide control intelligence.
-
The API is multiplexed, meaning that it can act on multiple system-provided entities, or
-
The API lends itself readily to an object-oriented (OO) representation.
Key Concepts
-
Expose a Command type with an API. The [
no_object
] feature must not be on. -
Leverage [function overloading] to simplify the API design.
-
Since Rhai is [sand-boxed], it cannot mutate the environment. To perform external actions via an API, the command object type must be wrapped in a
RefCell
(orRwLock
/Mutex
for [sync
]) and shared to the [Engine
]. -
Load each command object into a custom [
Scope
] as constant variables. -
Control each command object in script via the constants.
Implementation
There are two broad ways for Rhai to control an external system, both of which involve wrapping the system in a shared, interior-mutated object.
This is the other way which involves directly exposing the data structures of the external system as a name singleton object in the scripting space.
Use this when the API is complex but has a clear object structure.
For a relatively simple API that is action-based and not object-based, use the Control Layer pattern instead.
Functional API
Assume the following command object type:
struct EnergizerBunny { ... }
impl EnergizerBunny {
pub fn new () -> Self { ... }
pub fn go (&mut self) { ... }
pub fn stop (&mut self) { ... }
pub fn is_going (&self) -> bol { ... }
pub fn get_speed (&self) -> i64 { ... }
pub fn set_speed (&mut self, speed: i64) { ... }
pub fn turn (&mut self, left_turn: bool) { ... }
}
Wrap Command Object Type as Shared
pub type SharedBunny = Rc<RefCell<EnergizerBunny>>;
Note: Use Arc<Mutex<T>>
or Arc<RwLock<T>>
when using the [sync
] feature because the function
must then be Send + Sync
.
Register the Custom Type
engine.register_type_with_name::<SharedBunny>("EnergizerBunny");
Develop a Plugin with Methods and Getters/Setters
The easiest way to develop a complete set of API for a [custom type] is via a [plugin module].
use rhai::plugin::*;
#[export_module]
pub mod bunny_api {
pub const MAX_SPEED: i64 = 100;
#[rhai_fn(get = "power")]
pub fn get_power(bunny: &mut SharedBunny) -> bool {
bunny.borrow().is_going()
}
#[rhai_fn(set = "power")]
pub fn set_power(bunny: &mut SharedBunny, on: bool) {
if on {
if bunny.borrow().is_going() {
println!("Still going...");
} else {
bunny.borrow_mut().go();
}
} else {
if bunny.borrow().is_going() {
bunny.borrow_mut().stop();
} else {
println!("Already out of battery!");
}
}
}
#[rhai_fn(get = "speed")]
pub fn get_speed(bunny: &mut SharedBunny) -> i64 {
if bunny.borrow().is_going() {
bunny.borrow().get_speed()
} else {
0
}
}
#[rhai_fn(set = "speed", return_raw)]
pub fn set_speed(bunny: &mut SharedBunny, speed: i64)
-> Result<Dynamic, Box<EvalAltResult>>
{
if speed <= 0 {
Err("Speed must be positive!".into())
} else if speed > MAX_SPEED {
Err("Bunny will be going too fast!".into())
} else if !bunny.borrow().is_going() {
Err("Bunny is not yet going!".into())
} else {
b.borrow_mut().set_speed(speed);
Ok(Dynamic::UNIT)
}
}
pub fn turn_left(bunny: &mut SharedBunny) {
if bunny.borrow().is_going() {
bunny.borrow_mut().turn(true);
}
}
pub fn turn_right(bunny: &mut SharedBunny) {
if bunny.borrow().is_going() {
bunny.borrow_mut().turn(false);
}
}
}
engine.load_package(exported_module!(bunny_api));
Push Constant Command Object into Custom Scope
let bunny: SharedBunny = Rc::new(RefCell::(EnergizerBunny::new()));
let mut scope = Scope::new();
// Add the command object into a custom Scope.
scope.push_constant("Bunny", bunny.clone());
engine.consume_with_scope(&mut scope, script)?;
Use the Command API in Script
// Access the command object via constant variable 'Bunny'.
if !Bunny.power { Bunny.power = true; }
if Bunny.speed > 50 { Bunny.speed = 50; }
Bunny.turn_left();