Queenie  Davis

Queenie Davis

1664905860

Pronto Graphics: Quick and Simple Graphics for Rust

Pronto Graphics

A library for anyone who just wants to get some graphics on the screen, without having to faff about with the technical details of proper graphics libraries. Just create a window, and start drawing to it. Minimal setup, minimal bother, minimal interference with your own code's structure.

Loosely inspired by Processing.

Examples

You want some circles on the screen?

let mut pg = Window::new(800, 600, "Circles!");
loop {
    pg.circle((100., 100.), 15.);

    pg.fill_color(Color::BLUE);
    pg.circle((300., 450.), 24.);
    
    pg.update();
}

Or a texture?

let mut pg = Window::new_fullscreen();
let my_texture = pg.load_texture("my_texture.png").unwrap();
loop {
    pg.texture((100., 250.), my_texture, 100., 150.);
    
    pg.update();
}

How about some text?

let mut pg = Window::new(720, 480, "Text!");
loop {
    pg.font_color((0xEE, 0x44, 0x88));
    pg.font_size(30);
    pg.text((100., 100.), "Greetings!");
    
    pg.update();
}

Want to press some keys and click some stuff?

let mut pg = Window::new_fullscreen();
loop {
    if pg.key_just_pressed(Key::SPACE) {
        println!("Action!");
    }

    if pg.mouse_pressed(Button::LEFT) {
        pg.circle(pg.mouse_position(), 16.);
    }

    pg.update();
}

Install

Since Pronto Graphics uses SFML for rendering, specifically the SFML bindings for Rust, it's prerequisites are identical to the SFML Rust bindings, namely for the SFML library to be installed. This might possibly change in future versions.

# Cargo.toml

[dependencies]
pronto-graphics = "0.4.0"

Features

  •  Circle, Rectangles, Squares
  •  Lines
  •  Textures
  •  Text
  •  Keyboard
  •  Mouse
  •  Doc comments
  •  Custom fonts

Planned

  •  Transforms (Rotation, Origin, text alignment)
  •  Triangles
  •  Arbitrary shapes
  •  Audio
  •  Caching/Batching of draw calls
  •  Draw customization (outline thickness/etc.)

Contributions

I'm no experiences open saucer either, so don't hesitate with pull requests :)

Just make sure to explain what you're adding or changing and to adequately add doc comments to anything that will be exposed to the end-user.

Notes

  • Investigate whether it might be better for performance to create a new SFML object for each draw call, instead of reusing them.
  • Add separate examples for different features, the hello-world.rs is getting quite big.

|| Docs.rs || Lib.rs || Crates.io ||


Download Details:

Author: Garbaz
Source Code: https://github.com/Garbaz/pronto-graphics

#rust 

What is GEEK

Buddha Community

Pronto Graphics: Quick and Simple Graphics for Rust

Serde Rust: Serialization Framework for Rust

Serde

*Serde is a framework for serializing and deserializing Rust data structures efficiently and generically.*

You may be looking for:

Serde in action

Click to show Cargo.toml. Run this code in the playground.

[dependencies]

# The core APIs, including the Serialize and Deserialize traits. Always
# required when using Serde. The "derive" feature is only required when
# using #[derive(Serialize, Deserialize)] to make Serde work with structs
# and enums defined in your crate.
serde = { version = "1.0", features = ["derive"] }

# Each data format lives in its own crate; the sample code below uses JSON
# but you may be using a different one.
serde_json = "1.0"

 

use serde::{Serialize, Deserialize};

#[derive(Serialize, Deserialize, Debug)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let point = Point { x: 1, y: 2 };

    // Convert the Point to a JSON string.
    let serialized = serde_json::to_string(&point).unwrap();

    // Prints serialized = {"x":1,"y":2}
    println!("serialized = {}", serialized);

    // Convert the JSON string back to a Point.
    let deserialized: Point = serde_json::from_str(&serialized).unwrap();

    // Prints deserialized = Point { x: 1, y: 2 }
    println!("deserialized = {:?}", deserialized);
}

Getting help

Serde is one of the most widely used Rust libraries so any place that Rustaceans congregate will be able to help you out. For chat, consider trying the #rust-questions or #rust-beginners channels of the unofficial community Discord (invite: https://discord.gg/rust-lang-community), the #rust-usage or #beginners channels of the official Rust Project Discord (invite: https://discord.gg/rust-lang), or the #general stream in Zulip. For asynchronous, consider the [rust] tag on StackOverflow, the /r/rust subreddit which has a pinned weekly easy questions post, or the Rust Discourse forum. It's acceptable to file a support issue in this repo but they tend not to get as many eyes as any of the above and may get closed without a response after some time.

Download Details:
Author: serde-rs
Source Code: https://github.com/serde-rs/serde
License: View license

#rust  #rustlang 

Jenny Jabde

1621251999

Quick Flow Male Enhancement Reviews, Benefits Price & Buy Quick Flow?

364bb242-ab45-4601-b9cc-e444f2270076

On the off chance that you fall in the subsequent class, Quick Flow Male Enhancement is the thing that your body is needing right now. The recently discovered male arrangement is the difficult solver for numerous types and types of erectile pressure causing brokenness and causes those issues to be rectified and henceforth blessings you with the more youthful sexual variant.

What is Quick Flow Male Enhancement?
With the new pill, you can supplant all extraordinary and numerous allopathic drugs you had been taking for each issue in an unexpected way. Quick Flow Male Enhancement is the one in all treating instrument pill and causes those explicitly hurtful issues to get right. Regardless of everything, those obstacles are restored and unquestionably, you can feel that the sexual peaks are better. This item builds body imperativeness and the measure of discharge that is required is likewise directed by it.

**How can it really function? **

Different results of this class have numerous regular Ingredients in them, yet the ones here in Quick Flow Male Enhancement are truly uncommon and furthermore natural in their reap and produce. This allows you to get the experience of the truth of more profound sex intercourse which you generally thought was a fantasy for you. Positively, this is a demonstrated natural thing, and relying upon it is no place off-base according to specialists. It is time that your body is given valuable minerals as requested by age.

download-1
**How to Buy? **

It is fundamental that you visit the site and see by your own eyes you willing we are to help you in each progression. Start from the terms and furthermore know inconspicuously the states of procurement. Any question must be addressed as of now or, more than likely later things probably won’t go as you might suspect. Purchase Quick Flow Male Enhancement utilizing any method of online installment and you may likewise go for the simple EMI choice out there.

https://www.benzinga.com/press-releases/21/03/wr20313473/quick-flow-male-enhancement-reviews-fast-flow-male-enhancement-most-effective-and-natural-formul

https://www.facebook.com/Quick-Flow-Male-Enhancement-111452187779423

#quick flow male enhancement #quick flow male enhancement reviews #quick flow male enhancement male health #quick flow male enhancement review #quick flow male enhancement offer #quick flow male enhancement trial

Queenie  Davis

Queenie Davis

1664905860

Pronto Graphics: Quick and Simple Graphics for Rust

Pronto Graphics

A library for anyone who just wants to get some graphics on the screen, without having to faff about with the technical details of proper graphics libraries. Just create a window, and start drawing to it. Minimal setup, minimal bother, minimal interference with your own code's structure.

Loosely inspired by Processing.

Examples

You want some circles on the screen?

let mut pg = Window::new(800, 600, "Circles!");
loop {
    pg.circle((100., 100.), 15.);

    pg.fill_color(Color::BLUE);
    pg.circle((300., 450.), 24.);
    
    pg.update();
}

Or a texture?

let mut pg = Window::new_fullscreen();
let my_texture = pg.load_texture("my_texture.png").unwrap();
loop {
    pg.texture((100., 250.), my_texture, 100., 150.);
    
    pg.update();
}

How about some text?

let mut pg = Window::new(720, 480, "Text!");
loop {
    pg.font_color((0xEE, 0x44, 0x88));
    pg.font_size(30);
    pg.text((100., 100.), "Greetings!");
    
    pg.update();
}

Want to press some keys and click some stuff?

let mut pg = Window::new_fullscreen();
loop {
    if pg.key_just_pressed(Key::SPACE) {
        println!("Action!");
    }

    if pg.mouse_pressed(Button::LEFT) {
        pg.circle(pg.mouse_position(), 16.);
    }

    pg.update();
}

Install

Since Pronto Graphics uses SFML for rendering, specifically the SFML bindings for Rust, it's prerequisites are identical to the SFML Rust bindings, namely for the SFML library to be installed. This might possibly change in future versions.

# Cargo.toml

[dependencies]
pronto-graphics = "0.4.0"

Features

  •  Circle, Rectangles, Squares
  •  Lines
  •  Textures
  •  Text
  •  Keyboard
  •  Mouse
  •  Doc comments
  •  Custom fonts

Planned

  •  Transforms (Rotation, Origin, text alignment)
  •  Triangles
  •  Arbitrary shapes
  •  Audio
  •  Caching/Batching of draw calls
  •  Draw customization (outline thickness/etc.)

Contributions

I'm no experiences open saucer either, so don't hesitate with pull requests :)

Just make sure to explain what you're adding or changing and to adequately add doc comments to anything that will be exposed to the end-user.

Notes

  • Investigate whether it might be better for performance to create a new SFML object for each draw call, instead of reusing them.
  • Add separate examples for different features, the hello-world.rs is getting quite big.

|| Docs.rs || Lib.rs || Crates.io ||


Download Details:

Author: Garbaz
Source Code: https://github.com/Garbaz/pronto-graphics

#rust 

Pronto Graphics: Quick and Simple Graphics for Rust

Pronto Graphics

|| Docs.rs || Lib.rs || Crates.io ||

A library for anyone who just wants to get some graphics on the screen, without having to faff about with the technical details of proper graphics libraries. Just create a window, and start drawing to it. Minimal setup, minimal bother, minimal interference with your own code's structure.

Loosely inspired by Processing.

Examples

You want some circles on the screen?

let mut pg = Window::new(800, 600, "Circles!");
loop {
    pg.circle((100., 100.), 15.);

    pg.fill_color(Color::BLUE);
    pg.circle((300., 450.), 24.);
    
    pg.update();
}

Or a texture?

let mut pg = Window::new_fullscreen();
let my_texture = pg.load_texture("my_texture.png").unwrap();
loop {
    pg.texture((100., 250.), my_texture, 100., 150.);
    
    pg.update();
}

How about some text?

let mut pg = Window::new(720, 480, "Text!");
loop {
    pg.font_color((0xEE, 0x44, 0x88));
    pg.font_size(30);
    pg.text((100., 100.), "Greetings!");
    
    pg.update();
}

Want to press some keys and click some stuff?

let mut pg = Window::new_fullscreen();
loop {
    if pg.key_just_pressed(Key::SPACE) {
        println!("Action!");
    }

    if pg.mouse_pressed(Button::LEFT) {
        pg.circle(pg.mouse_position(), 16.);
    }

    pg.update();
}

Install

Since Pronto Graphics uses SFML for rendering, specifically the SFML bindings for Rust, it's prerequisites are identical to the SFML Rust bindings, namely for the SFML library to be installed. This might possibly change in future versions.

# Cargo.toml

[dependencies]
pronto-graphics = "0.4.0"

Features

  •  Circle, Rectangles, Squares
  •  Lines
  •  Textures
  •  Text
  •  Keyboard
  •  Mouse
  •  Doc comments
  •  Custom fonts

Planned

  •  Transforms (Rotation, Origin, text alignment)
  •  Triangles
  •  Arbitrary shapes
  •  Audio
  •  Caching/Batching of draw calls
  •  Draw customization (outline thickness/etc.)

Contributions

I'm no experiences open saucer either, so don't hesitate with pull requests :)

Just make sure to explain what you're adding or changing and to adequately add doc comments to anything that will be exposed to the end-user.

Notes

  • Investigate whether it might be better for performance to create a new SFML object for each draw call, instead of reusing them.
  • Add separate examples for different features, the hello-world.rs is getting quite big.

Author: Garbaz
Source code: https://github.com/Garbaz/pronto-graphics
License:

#rust 

Awesome  Rust

Awesome Rust

1654894080

Serde JSON: JSON Support for Serde Framework

Serde JSON

Serde is a framework for serializing and deserializing Rust data structures efficiently and generically.

[dependencies]
serde_json = "1.0"

You may be looking for:

JSON is a ubiquitous open-standard format that uses human-readable text to transmit data objects consisting of key-value pairs.

{
    "name": "John Doe",
    "age": 43,
    "address": {
        "street": "10 Downing Street",
        "city": "London"
    },
    "phones": [
        "+44 1234567",
        "+44 2345678"
    ]
}

There are three common ways that you might find yourself needing to work with JSON data in Rust.

  • As text data. An unprocessed string of JSON data that you receive on an HTTP endpoint, read from a file, or prepare to send to a remote server.
  • As an untyped or loosely typed representation. Maybe you want to check that some JSON data is valid before passing it on, but without knowing the structure of what it contains. Or you want to do very basic manipulations like insert a key in a particular spot.
  • As a strongly typed Rust data structure. When you expect all or most of your data to conform to a particular structure and want to get real work done without JSON's loosey-goosey nature tripping you up.

Serde JSON provides efficient, flexible, safe ways of converting data between each of these representations.

Operating on untyped JSON values

Any valid JSON data can be manipulated in the following recursive enum representation. This data structure is serde_json::Value.

enum Value {
    Null,
    Bool(bool),
    Number(Number),
    String(String),
    Array(Vec<Value>),
    Object(Map<String, Value>),
}

A string of JSON data can be parsed into a serde_json::Value by the serde_json::from_str function. There is also from_slice for parsing from a byte slice &[u8] and from_reader for parsing from any io::Read like a File or a TCP stream.

use serde_json::{Result, Value};

fn untyped_example() -> Result<()> {
    // Some JSON input data as a &str. Maybe this comes from the user.
    let data = r#"
        {
            "name": "John Doe",
            "age": 43,
            "phones": [
                "+44 1234567",
                "+44 2345678"
            ]
        }"#;

    // Parse the string of data into serde_json::Value.
    let v: Value = serde_json::from_str(data)?;

    // Access parts of the data by indexing with square brackets.
    println!("Please call {} at the number {}", v["name"], v["phones"][0]);

    Ok(())
}

The result of square bracket indexing like v["name"] is a borrow of the data at that index, so the type is &Value. A JSON map can be indexed with string keys, while a JSON array can be indexed with integer keys. If the type of the data is not right for the type with which it is being indexed, or if a map does not contain the key being indexed, or if the index into a vector is out of bounds, the returned element is Value::Null.

When a Value is printed, it is printed as a JSON string. So in the code above, the output looks like Please call "John Doe" at the number "+44 1234567". The quotation marks appear because v["name"] is a &Value containing a JSON string and its JSON representation is "John Doe". Printing as a plain string without quotation marks involves converting from a JSON string to a Rust string with as_str() or avoiding the use of Value as described in the following section.

The Value representation is sufficient for very basic tasks but can be tedious to work with for anything more significant. Error handling is verbose to implement correctly, for example imagine trying to detect the presence of unrecognized fields in the input data. The compiler is powerless to help you when you make a mistake, for example imagine typoing v["name"] as v["nmae"] in one of the dozens of places it is used in your code.

Parsing JSON as strongly typed data structures

Serde provides a powerful way of mapping JSON data into Rust data structures largely automatically.

use serde::{Deserialize, Serialize};
use serde_json::Result;

#[derive(Serialize, Deserialize)]
struct Person {
    name: String,
    age: u8,
    phones: Vec<String>,
}

fn typed_example() -> Result<()> {
    // Some JSON input data as a &str. Maybe this comes from the user.
    let data = r#"
        {
            "name": "John Doe",
            "age": 43,
            "phones": [
                "+44 1234567",
                "+44 2345678"
            ]
        }"#;

    // Parse the string of data into a Person object. This is exactly the
    // same function as the one that produced serde_json::Value above, but
    // now we are asking it for a Person as output.
    let p: Person = serde_json::from_str(data)?;

    // Do things just like with any other Rust data structure.
    println!("Please call {} at the number {}", p.name, p.phones[0]);

    Ok(())
}

This is the same serde_json::from_str function as before, but this time we assign the return value to a variable of type Person so Serde will automatically interpret the input data as a Person and produce informative error messages if the layout does not conform to what a Person is expected to look like.

Any type that implements Serde's Deserialize trait can be deserialized this way. This includes built-in Rust standard library types like Vec<T> and HashMap<K, V>, as well as any structs or enums annotated with #[derive(Deserialize)].

Once we have p of type Person, our IDE and the Rust compiler can help us use it correctly like they do for any other Rust code. The IDE can autocomplete field names to prevent typos, which was impossible in the serde_json::Value representation. And the Rust compiler can check that when we write p.phones[0], then p.phones is guaranteed to be a Vec<String> so indexing into it makes sense and produces a String.

The necessary setup for using Serde's derive macros is explained on the Using derive page of the Serde site.

Constructing JSON values

Serde JSON provides a json! macro to build serde_json::Value objects with very natural JSON syntax.

use serde_json::json;

fn main() {
    // The type of `john` is `serde_json::Value`
    let john = json!({
        "name": "John Doe",
        "age": 43,
        "phones": [
            "+44 1234567",
            "+44 2345678"
        ]
    });

    println!("first phone number: {}", john["phones"][0]);

    // Convert to a string of JSON and print it out
    println!("{}", john.to_string());
}

The Value::to_string() function converts a serde_json::Value into a String of JSON text.

One neat thing about the json! macro is that variables and expressions can be interpolated directly into the JSON value as you are building it. Serde will check at compile time that the value you are interpolating is able to be represented as JSON.

let full_name = "John Doe";
let age_last_year = 42;

// The type of `john` is `serde_json::Value`
let john = json!({
    "name": full_name,
    "age": age_last_year + 1,
    "phones": [
        format!("+44 {}", random_phone())
    ]
});

This is amazingly convenient, but we have the problem we had before with Value: the IDE and Rust compiler cannot help us if we get it wrong. Serde JSON provides a better way of serializing strongly-typed data structures into JSON text.

Creating JSON by serializing data structures

A data structure can be converted to a JSON string by serde_json::to_string. There is also serde_json::to_vec which serializes to a Vec<u8> and serde_json::to_writer which serializes to any io::Write such as a File or a TCP stream.

use serde::{Deserialize, Serialize};
use serde_json::Result;

#[derive(Serialize, Deserialize)]
struct Address {
    street: String,
    city: String,
}

fn print_an_address() -> Result<()> {
    // Some data structure.
    let address = Address {
        street: "10 Downing Street".to_owned(),
        city: "London".to_owned(),
    };

    // Serialize it to a JSON string.
    let j = serde_json::to_string(&address)?;

    // Print, write to a file, or send to an HTTP server.
    println!("{}", j);

    Ok(())
}

Any type that implements Serde's Serialize trait can be serialized this way. This includes built-in Rust standard library types like Vec<T> and HashMap<K, V>, as well as any structs or enums annotated with #[derive(Serialize)].

Performance

It is fast. You should expect in the ballpark of 500 to 1000 megabytes per second deserialization and 600 to 900 megabytes per second serialization, depending on the characteristics of your data. This is competitive with the fastest C and C++ JSON libraries or even 30% faster for many use cases. Benchmarks live in the serde-rs/json-benchmark repo.

Getting help

Serde is one of the most widely used Rust libraries, so any place that Rustaceans congregate will be able to help you out. For chat, consider trying the #rust-questions or #rust-beginners channels of the unofficial community Discord (invite: https://discord.gg/rust-lang-community), the #rust-usage or #beginners channels of the official Rust Project Discord (invite: https://discord.gg/rust-lang), or the #general stream in Zulip. For asynchronous, consider the [rust] tag on StackOverflow, the /r/rust subreddit which has a pinned weekly easy questions post, or the Rust Discourse forum. It's acceptable to file a support issue in this repo, but they tend not to get as many eyes as any of the above and may get closed without a response after some time.

No-std support

As long as there is a memory allocator, it is possible to use serde_json without the rest of the Rust standard library. This is supported on Rust 1.36+. Disable the default "std" feature and enable the "alloc" feature:

[dependencies]
serde_json = { version = "1.0", default-features = false, features = ["alloc"] }

For JSON support in Serde without a memory allocator, please see the serde-json-core crate.

Link: https://crates.io/crates/serde_json

#rust  #rustlang  #encode   #json