https://bugs.kde.org/show_bug.cgi?id=384153
Bug ID: 384153
Summary: Modernize the text messages handling
Product: ring-kde
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: elv1...@gmail.com
Reporter: elv1...@gmail.com
Target Milestone: ---
The text messages API was rushed and has major limitations that blocks 3.0.0
* Setting messages as unread is plain broken, so they stay red forever
* All text messages are loaded during startup, this freezes the app on slow
HDD and mobile devices
* Memory usage is out of control (dozens of useless megabytes are allocated
for nothing)
* Clearing doesn't work
* There some polling timers that eat battery life
I have to be careful with the fixes as they will impact future features and
maintainability. This needs to be implemented right and by taking into
consideration all use cases. I settled on a second layer of serialization to
keep track of the metadata separately from the text recordings themselves. This
will enable more lazy loading and reduce startup time. The text recordings
themselves will be moved to use shared pointers to avoid keeping everything in
memory. The API is being reworked to move the recorcing states (including
voicemails and in call recording) to a finite state machine. Some other work is
being done to improve the recording API.
--
You are receiving this mail because:
You are watching all bug changes.
