features/changes for new version

[chindaronit]

1. adding widgets
2. option to change icons of work-spaces
3. adding import/export
4. encrypted backup
5. more languages support
6. adding markdown support with rich text editor
7. adding custom repetition to habits and events for eg. currently all the habits are repeating daily, but some habits are done only on weekdays and some on alternating days, some only on weekends or any custom day of the week.
8. making ui more intuitive
9. Adding theme palettes

[pacjo]

[chindaronit]

Yes, dynamic theme part is done.
But i have a question there's a option to lock the workspace , so if its locked should we allow the widgets ?

[atikiNBTW]

Hello, what about "ADHD controller" type feature? What I mean by that is that Flux will block access to user-defined list of applications (maybe even workspace-defined) until the given task/tasks are completed? I don't think this feature is exactly aligned with Flux's purpose but what do you think?

[chindaronit]

Yeah this can be a good feature, we can think about it, for future releases.

[atikiNBTW]

so I'm trying to implement this in my free time, will open a PR when a first working version is done

[chindaronit]

2. 8 -> Done.

[chindaronit]

3 Done.
5 - French added

[speedit43]

There are still a lot of hardcoded words, so I'm going to do that

[atikiNBTW]

what versioning scheme are you following? cuz version 2 should introduce a lot of breaking changes

[chindaronit]

Actually there's been many changes to the entire structure of the application so either way existing user shifting from version 1.0 to 2.0 has to reinstall the application instead of updating, that's why I have used version 1 to database as migration can't be possible from having multiple databases for every table (earlier) to only one db now

[chindaronit]

So I'm thinking of version 2.0 of the application instead of 1.1, and for the new flux database to be version 1, now any new changes to this db can be migrated as there won't be much restructuring.

[atikiNBTW]

i think there should be migration from old DBs to the big new one, i don't think users would be happy to delete all of their data

[chindaronit]

Yeah, you're right I thought the same, i may sound stupid but i thought there won't be much users currently using the application so at the initial stages i can pull out this change, also i was finding it difficult to map the data by deleting all those database .kt files and map all the data to new database.

[chindaronit]

9 -> done

[chindaronit]

7->Done.

[chindaronit]

6->done

[chindaronit]

Features in Version 3.0:

• Markdown Support in Notes & Journal.
• Share Notes and Journal as markdown, html, image, pdf.
• Improved To-do UI
• Merged Calender with Events and Journal.