Book Image

Rust Programming By Example

By : Guillaume Gomez, Antoni Boucher
Book Image

Rust Programming By Example

By: Guillaume Gomez, Antoni Boucher

Overview of this book

Rust is an open source, safe, concurrent, practical language created by Mozilla. It runs blazingly fast, prevents segfaults, and guarantees safety. This book gets you started with essential software development by guiding you through the different aspects of Rust programming. With this approach, you can bridge the gap between learning and implementing immediately. Beginning with an introduction to Rust, you’ll learn the basic aspects such as its syntax, data types, functions, generics, control flows, and more. After this, you’ll jump straight into building your first project, a Tetris game. Next you’ll build a graphical music player and work with fast, reliable networking software using Tokio, the scalable and productive asynchronous IO Rust library. Over the course of this book, you’ll explore various features of Rust Programming including its SDL features, event loop, File I/O, and the famous GTK+ widget toolkit. Through these projects, you’ll see how well Rust performs in terms of concurrency—including parallelism, reliability, improved performance, generics, macros, and thread safety. We’ll also cover some asynchronous and reactive programming aspects of Rust. By the end of the book, you’ll be comfortable building various real-world applications in Rust.
Table of Contents (18 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
3
Events and Basic Game Mechanisms
Index

Widget


This crate is centered around the concept of widgets, which are different than the gtk widgets. In relm, a widget is composed of a view, a model, and a method to update the model in reaction to events. The concept of widget is implemented by a trait in relm: the Widget trait.

Model

We'll start with an empty model and we'll populate it later in this chapter:

pub struct Model {
}

As you can see, a model can be a simple structure. It could also be () if your widget don't need a model. Actually, it can be any type you want.

Besides the model, a widget needs to know the initial value of its model. To specify what it is, we need to implement the model() method of the Widget trait:

#[widget]
impl Widget for App {
    fn model() -> Model {
        Model {
        }
    }

    // …
}

Here, we use the #[widget] attribute provided by the relm_attributes crate. Attributes are currently an unstable feature of the language, that's why we use nightly. We'll see in the section about the declarative view...