Replies: 2 comments
-
Kraft v2 is progressing in the branch newshared: https://github.com/dragotin/kraft/tree/newshared A few more features that already landed in the branch: Document LivecycleIn Kraft v2 there will be a new livecycle for documents. These are the states defined (today):
Downside is that users have to do a finalizing step to make the document final. However, that comes with many benefits, for example simpler deletion of draft docs and reminders for unpaid invoices. XML Document BasedTo be able to sync documents to private clouds, Kraft v2 is not longer storing documents in the database, but as individual XML documents in the file system. A file system structure and a file index for quick lookup of documents are already there. Also the number cycles are now stored in an XML file. Prompt PDF CreationKraft v2 generates the PDF not at the moment where user wants to open the document, but as soon as a change to the document is saved to disk. That gives a much better user experience because the PDF is opened immediately. Visual ChangesUse a consistent icon set (Tabler icons) also on the document overview pane. |
Beta Was this translation helpful? Give feedback.
-
🚀 The Kraft version 2 feature branch called newshared was merged into master today. 🎉 The next version that will be released from master is a Kraft version 2.x. It is not yet clear when that will be. For ongoing work on Kraft version 1.x the branch |
Beta Was this translation helpful? Give feedback.
-
After having Kraft 1.0 released, this should outline a plan for Kraft 2.0 and add more transparency to where Kraft is moving.
Please note: This is always subject to change! Also, the following list is probably too big and might be split to more major versions.
These are the big building blocks that are on the list:
Technical Debt
Here we talk about technical topics that need to be done just to keep up with the fast moving ecosystem.
Projects
A simple yet useful Project management that adds more organisation around connected documents (think offer->partial invoice->invoice) and for example payment information.
Private Clouds
Kraft should optionally integrate with private clouds such as ownCloud and Nextcloud. In fact, it does already today with the addressbook integration via Akonadi. But there could be much more, for example:
This has some technical implications such as: For example, the database should become a local storage only (Sqlite only) and there should not be a need to synchronize the DB.
Address Book Flexibility
The current Akonadi based addressbook is great and will continue to be the main integration. The problem with it is that it does not work with the AppImage. There needs to be a solution for this, most likely file based.
Features
There are many enhancement requests in the issue tracker.
Give your vote setting a 👍 or ❤️ emoji to the enhancements you would consider most valueable.
Beta Was this translation helpful? Give feedback.
All reactions