cunarist / rinf Goto Github PK

This can be done by removing the workspace crate. However, we need to first find out what happens when crate A and B depends on the same third-party crate but expect different version.

The web has very many restrictions due to the sandboxed environment. Native threads, atomics, and time are not possible in webassembly and therefore many features are missing from the Rust's std and other crates due to these limitations.

flutter_rust_bridge does provide some way to utilize web workers and streams thanks to its bindings with JavaScript. However, there are still additional support needed from various libraries.

We think that when Threads Proposal for WebAssembly is fully accepted and realized, support from Rust and various libraries will mature. For now, there is a long way to go.

When running

flutter build apk --release

the rust code is compiled in dev mode:

Finished dev [unoptimized + debuginfo] target(s) in 0.08s

Is it possible to pass --release flag to the rust build command?

https://stackoverflow.com/questions/54799931/how-to-localize-app-name-shown-in-launcher-using-flutter

Auto formatting with clilppy, dart fix, and black should be applied first.

When calling a string character, the data type must be converted once before it can be used

Flutter is a reactive framework and a widget gets updated every time when the underlying value changes(In this app, through StreamBuilder). Even if the viewmodel item uses the nested structure, when the Rust logic updates the viewmodel item multiple times, Flutter app will be re-build the relying widget multiple times. Therefore, there's no point of using nested structures on viewmodel items.

Viewmodel itself would be a nested hashmap, with only the simplest data types included, organized with an enum.

This idea can be also applied to the data model on the Rust side.

https://medium.com/google-design/designing-adaptive-icons-515af294c783

For developers, it should be written in README.md

The version of rust_in_flutter is 1.1.1 and running the official example packaged for Android gives the following error :

And also I would like to know where the built dynamic libraries are put by default ?

https://pub.dev/packages/window_manager

Use tokio futures for concurrency in a single thread

This package is currently building and shipping dead native code on every platform. If you use ffiPlugin: true instead of pluginClass those dummy native plugin implementations will no longer be necessary.

Balancing the performance and readability

More specifically:

• Merge bridge crate into hub
• Lower xcodeproj folder's presence

Some middle dependencies can be just removed since it is available to directly interact with Dart VM with allo-isolate.

https://cjycode.com/flutter_rust_bridge/feature/zero_copy.html