[FAQ] Some questions regarding this project

[Raj2032]

Hey I have some questions regarding this project:

Is it retained or immediate or is it both?

Does it support Android at this stage?

[rzerres]

Hey @Raj2032,

your question is referenced to #475. No it's not retained nor immediate.

Since multiplatform support is one of the major design goals of this project , android is seen a a first class citizen. Right now, nobody is actively looking into the specific needs of the mobile targets (like gesture support or theme adoption). But yes, OrbTk code should make its way to compile native as an android app.

Please let us know about your expectations. Are you able to pick up a specific part, issue, describe ideas, document available corner cases?

[Raj2032]

@rzerres Hi thanks for your response.

Please let us know about your expectations. Are you able to pick up a specific part, issue, describe ideas, document available corner cases?

Actually I have some questions about this, does it lock you into some kind of framework (when coding), the way how Bevy does it with their framework?

For example if I were to use PathBuf library/crate:

use std::path::PathBuf;

let mut path = PathBuf::new();

path.push(r"C:\");
path.push("windows");
path.push("system32");

See how this doesn't lock you into some kind of framework?

Whereas with Bevy:

use bevy::prelude::*;

fn main() {
   App::new()
       .add_system(hello_world_system)
       .run();
}

fn hello_world_system() {
   println!("hello world");
}

See how this does lock me into a framework?

Is this the same case with orbtk?

[rzerres]

@Raj2032 i hope i got your question right.

have a look into

• orbtk_core/src/properties/mod.rs or
• utils/build.rs

where OrbTk itself is consuming PathBuf. When the Toolkit (or its crates) are depending on 3rd party crates, we try to consume best practice methods without reinventing the wheel. As a second driver it's attempting to gain platform agnostic ways to implement the UI traits/methods doing so.

If I'm don't miss the tartet, this hopefully explains why you are free to use things it as yo expect without locking you the way .add_system() from the bevy crate.

[Raj2032]

@rzerres I see thanks mate :)