Maintenance Plan

[Mehmetyaz]

As you know, I haven't been able to work on the package for quite some time. The fact that the package has received more interaction than I expected and that many people are interested in it encourages me to change this situation.

Unfortunately, I can't commit to a specific amount of time to work on updating the package. However, we can collectively make the necessary updates to the package and fix any bugs together.

Besides the bugs, we need an architectural change in the package. Observant reviewers will notice that there are two different architectures within the package. Halfway through development, I realized the needs had changed, so I altered the architecture. This makes it difficult for the community to develop new features.

Let's use this issue to list possible features and determine what needs to be changed in the architecture over the next two weeks (I’m open to new and creative features that excite me). After that, I’ll make the necessary fundamental changes to the architecture and wait for the community's contributions with the new structure. In other words, I’d like to complete additional features with the community's help.

Since there is such interest in the package, I promise that I’ll make time for maintenance (but not for active development).

Here are some features I’d like us to discuss:

1 - Making calculations multi-threaded
2 - Swap #13
3 - Allowing the developer more control over items and layout with the controller.

[Mehmetyaz]

Additional feature: SliverDashboard