knt_isolate library

Classes

Backend

Backend - is the second part of your two-classes logic component, which will live in a separated isolate and will have no effect on the UI thread. In the Backend, you should place all (heavy or not) your logic and data.

BackendActionInitializer<Event>

Helper class to register Backend's actions

BackendArgument<T>

Wrapper for data, which will send to Backend, when Frontend will initialize that

FrontendActionInitializer<Event>

Class

FrontendActionSubscriber<Event>

Class

InteractorOf<BackendType extends Backend>

Class

KntIsolate

KntIsolateEvent

KntIsolateUnit

Maybe<T>

Class

Packet<T>

Class

Packet10<T, T2, T3, T4, T5, T6, T7, T8, T9, T10>

Class

Packet2<T, T2>

Class

Packet3<T, T2, T3>

Class

Packet4<T, T2, T3, T4>

Class

Packet5<T, T2, T3, T4, T5>

Class

Packet6<T, T2, T3, T4, T5, T6>

Class

Packet7<T, T2, T3, T4, T5, T6, T7>

Class

Packet8<T, T2, T3, T4, T5, T6, T7, T8>

Class

Packet9<T, T2, T3, T4, T5, T6, T7, T8, T9>

Class

Mixins

Frontend

This is the first part of two-class component. Frontend will run in the UI-thread and its purpose is to update the UI after getting messages from the Backend or after calling Backend's methods

Functions

enableSingleThreadMode() → void

In some versions of Flutter you can see, that Hot Reload take a very much time. See: https://github.com/flutter/flutter/issues/84347 And this:https://github.com/flutter/flutter/pull/84363 To solve this problem - you must have as least isolates as possible and with this method you can use Isolator in single thread mode for developing, to have fast Hot Reload as usual and enable multi-thread (standard) mode only for checking that all works fine and for production.

Typedefs

BackendInit = Future<void> Function(KntIsolateUnit)

FrontendInit = Future<KntIsolateUnit> Function()