#kdepim — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kdepim, aggregated by home.social.
-
I am a long-term #KDEPIM user and recently read that due to progress in #SQLite’s performance #Akonadi is now defaulting to that DB on a fresh install.
A few days ago I took the chance and ran `akonadi-db-migrator --newengine sqlite` and it was both painless and I definitely see both lower resource consumption and the PIM suite seems much snappier too!
-
I am a long-term #KDEPIM user and recently read that due to progress in #SQLite’s performance #Akonadi is now defaulting to that DB on a fresh install.
A few days ago I took the chance and ran `akonadi-db-migrator --newengine sqlite` and it was both painless and I definitely see both lower resource consumption and the PIM suite seems much snappier too!
-
I am a long-term #KDEPIM user and recently read that due to progress in #SQLite’s performance #Akonadi is now defaulting to that DB on a fresh install.
A few days ago I took the chance and ran `akonadi-db-migrator --newengine sqlite` and it was both painless and I definitely see both lower resource consumption and the PIM suite seems much snappier too!
-
I am a long-term #KDEPIM user and recently read that due to progress in #SQLite’s performance #Akonadi is now defaulting to that DB on a fresh install.
A few days ago I took the chance and ran `akonadi-db-migrator --newengine sqlite` and it was both painless and I definitely see both lower resource consumption and the PIM suite seems much snappier too!
-
I am a long-term #KDEPIM user and recently read that due to progress in #SQLite’s performance #Akonadi is now defaulting to that DB on a fresh install.
A few days ago I took the chance and ran `akonadi-db-migrator --newengine sqlite` and it was both painless and I definitely see both lower resource consumption and the PIM suite seems much snappier too!
-
@ervin, I see you’ve been at #Akademy and held a #KDEPIM BoF.
There was a topic on how to gather more info from users.
As an avid user of #KMail, #KOrganizer and #Zanshin, I have (quite) some feedback and bug reports to provide. But whenever I try to, it seems to end up in the void.
I think a first step would be concentrate on the number of communication channels that devs can actually manage. For both their sanity and the users’.
1/🧵
-
@ervin, I see you’ve been at #Akademy and held a #KDEPIM BoF.
There was a topic on how to gather more info from users.
As an avid user of #KMail, #KOrganizer and #Zanshin, I have (quite) some feedback and bug reports to provide. But whenever I try to, it seems to end up in the void.
I think a first step would be concentrate on the number of communication channels that devs can actually manage. For both their sanity and the users’.
1/🧵
-
@ervin, I see you’ve been at #Akademy and held a #KDEPIM BoF.
There was a topic on how to gather more info from users.
As an avid user of #KMail, #KOrganizer and #Zanshin, I have (quite) some feedback and bug reports to provide. But whenever I try to, it seems to end up in the void.
I think a first step would be concentrate on the number of communication channels that devs can actually manage. For both their sanity and the users’.
1/🧵
-
@ervin, I see you’ve been at #Akademy and held a #KDEPIM BoF.
There was a topic on how to gather more info from users.
As an avid user of #KMail, #KOrganizer and #Zanshin, I have (quite) some feedback and bug reports to provide. But whenever I try to, it seems to end up in the void.
I think a first step would be concentrate on the number of communication channels that devs can actually manage. For both their sanity and the users’.
1/🧵
-
@ervin, I see you’ve been at #Akademy and held a #KDEPIM BoF.
There was a topic on how to gather more info from users.
As an avid user of #KMail, #KOrganizer and #Zanshin, I have (quite) some feedback and bug reports to provide. But whenever I try to, it seems to end up in the void.
I think a first step would be concentrate on the number of communication channels that devs can actually manage. For both their sanity and the users’.
1/🧵
-
#KDE has long had a technology called #KParts. Basically you can set up something (including a full app) as a #KPart component and use it elsewhere as part of another (tools bars and menus will merge).
My understanding is that #Kate & #KWrite are a good example. Both now use the same editor component, but Kate adds a LOT of extra functionality to it. The #KDEPIM suite uses the same trick with it's components - they can run separately or as one combined app (#Kontact).
I'm not fully across the technology, so if any experts wish to correct me, feel free. 🤠
-
#KDE has long had a technology called #KParts. Basically you can set up something (including a full app) as a #KPart component and use it elsewhere as part of another (tools bars and menus will merge).
My understanding is that #Kate & #KWrite are a good example. Both now use the same editor component, but Kate adds a LOT of extra functionality to it. The #KDEPIM suite uses the same trick with it's components - they can run separately or as one combined app (#Kontact).
I'm not fully across the technology, so if any experts wish to correct me, feel free. 🤠
-
#KDE has long had a technology called #KParts. Basically you can set up something (including a full app) as a #KPart component and use it elsewhere as part of another (tools bars and menus will merge).
My understanding is that #Kate & #KWrite are a good example. Both now use the same editor component, but Kate adds a LOT of extra functionality to it. The #KDEPIM suite uses the same trick with it's components - they can run separately or as one combined app (#Kontact).
I'm not fully across the technology, so if any experts wish to correct me, feel free. 🤠
-
#KDE has long had a technology called #KParts. Basically you can set up something (including a full app) as a #KPart component and use it elsewhere as part of another (tools bars and menus will merge).
My understanding is that #Kate & #KWrite are a good example. Both now use the same editor component, but Kate adds a LOT of extra functionality to it. The #KDEPIM suite uses the same trick with it's components - they can run separately or as one combined app (#Kontact).
I'm not fully across the technology, so if any experts wish to correct me, feel free. 🤠
-
#KDE has long had a technology called #KParts. Basically you can set up something (including a full app) as a #KPart component and use it elsewhere as part of another (tools bars and menus will merge).
My understanding is that #Kate & #KWrite are a good example. Both now use the same editor component, but Kate adds a LOT of extra functionality to it. The #KDEPIM suite uses the same trick with it's components - they can run separately or as one combined app (#Kontact).
I'm not fully across the technology, so if any experts wish to correct me, feel free. 🤠
-
Today was my last day on #KDE #akademy , so here are some personal highlights regarding #kdepim
▶️ #akonadi resources in #rust are now closer to reality
▶️ Akonadi Resource for Outlook/Microsoft365 is being worked on (in Rust :rust_ferris: !!)
▶️ We have a dedicated EWS server for testing, expect bugfixes!It was amazing being on Akademy again after 5 years and seeing all my KDE friends. Thanks everyone for a great Akademy and see you next year :ablobcatheartsqueeze:
-
A nice side effect of the #KDE PIM sprint is that there is now a migration paths from KNotes to Marknote. It will allow us to archive KNotes and all the infrastructure behind it while making sure that your don't loose your notes and can use a nice and maintained app instead.
-
A nice side effect of the #KDE PIM sprint is that there is now a migration paths from KNotes to Marknote. It will allow us to archive KNotes and all the infrastructure behind it while making sure that your don't loose your notes and can use a nice and maintained app instead.
-
A nice side effect of the #KDE PIM sprint is that there is now a migration paths from KNotes to Marknote. It will allow us to archive KNotes and all the infrastructure behind it while making sure that your don't loose your notes and can use a nice and maintained app instead.
-
A nice side effect of the #KDE PIM sprint is that there is now a migration paths from KNotes to Marknote. It will allow us to archive KNotes and all the infrastructure behind it while making sure that your don't loose your notes and can use a nice and maintained app instead.
-
A nice side effect of the #KDE PIM sprint is that there is now a migration paths from KNotes to Marknote. It will allow us to archive KNotes and all the infrastructure behind it while making sure that your don't loose your notes and can use a nice and maintained app instead.