mskorkowski

This weekend I'm working on the reordering of records in the store on the store view side. It's already second week I'm working on that and I don't know if...

## Goals My short term goal is to make state management easier for sufficiently big application From my experience with `Relm4` it boils down to 1. Efficiently manage business model...

@AaronErhardt `cargo run --package=relm4-store-examples --example todo_2_single_scroll` is an example where using store and view you can scroll across 10 000 000 records without any gobject. It was even easier then...

I've more or less finalized the way you can define a behavior of the store view in presence of the new data. I also wrote a bunch of docs which...

Micro components still had an issue of chicken and the egg. So I've ended up writing my own component based on that. Now I'm polishing the new approach and rewriting...

Plans for near future (next week or two) in data-store repo: 1. Remove unnecessarily restrictive limitations 1. Get rid of single store-view for component limitation 2. Figure a way to...

## Update on the current status of the data-store repo I consider housekeeping phase done * Using data-store is much simpler now * `Widgets` and `widgets` macro now can be...

Changes last week on the `sorting` branch - There is sorted in memory backend ready for small amounts of data `relm4_store_backend_inmemory::SortedInMemoryBackend`. (I wouldn't use it above 10k records) - Some...

I've manage to find a bit of time this weekend and I've started writing unit tests - I've added `DummyBackend`. It's another data store implementation. It's just extra dumb and...

Store behaves more like a component and store view works like a factory. So I don't see any reason to make it broken with new architecture. I can run all...