[feature request]: add categories for pomodoro

[wennerryle]

Is your feature request related to a problem? Please describe.
Hello! I'm a developer, and I get paid by period of time spended on task.
The problem is that I have different projects, and they paid seperately.

Describe the solution you'd like
I'd like to see that the app have categories, and iternal database (for example - sqlite) for saving pomodoras with timers.
Then I wanna have ability to import table through CSV, JSON / NDJSON format, "SQLite format 3" without WAL (or do "PRAGMA wal_checkpoint" before import)

OR

Have hooks to extend your app with different one. After pomodoro is over your app calling user defined shell command with predefined by pomatez syntax.
For example:

# for work period
pomatezHandler work 50m

# for break period
pomatezHandler break 10m

Describe alternatives you've considered
Currently I saving notes to Pocketbase, I created two tables:

• Categories (id, name)
• Pomodoros (id, category_id, minutes, description)

And saving pomodoras manually.

Additional context

[sekwah41]

I have one or two projects im working on atm that have deadlines but unless someone gets to it first I am planning to move the data from the browser storage into a user directory for storage in some sort of format likely json or toml and having separate files though sqlite would be an option.

There are also requests to track time spent on tasks. Are you saying you would also like a backlog of the times you completed periods of work stored against the tasks or stored against categories?

The plan is to try to abstract the storage format to some degree so we can allow import/export between the different formats implemented, as people have requested being able to back up to places like cloud storage plans.

[wennerryle]

I think tasks and categories are nearly equals entities, so.. category can be represented as never endless task. In that way, if users want to have tasks, and I wanna have category, then I'll fine with tasks.

I also think that storing data in text formats are kinda strange, because if you wanted to change schema there's no tools for it (and you have to write it manually). So.. I prefer SQLite over any text format because of:

• De facto standart for any andorid app
• I can import data to any format from SQLite
• I like to write SQL for data analyzing in DuckDB

For example, a piece of code from DuckDB:

SELECT * FROM 'myfile.csv';
SELECT * FROM 'myfile.parquet';

I'd like to continue this topic in this theme -> #711

Maybe later I'll design table schemas, but until now I definetely say one thing:
If people wanted to count their time on task, let be this time be counted by aggregate function like:

SELECT SUM(minutes) FROM LOG l WHERE l.task_id = 'meow' AND l.status = 'work'

Also this cool, because you can draw diagrams with it 💃🏻

And I wanted to have created_at timestamps.

gracias amigo!

PS:
we can continue topic at #711. i'll keep this issue open, please close it after reading

[sekwah41]

You have a very good point about schema change. I also agree that it is far more dev friendly for purposes like you have outlined. I also haven't done any native android development in years and forgot that was used as the standard so thanks for pointing that out :D

The main reason I was looking at json or toml is because I'm quite used to using gson or serde for serialisation and deserialisation for other projects mostly around the Minecraft space.

Main reason I was asking about categories was if the log of time spent wanted to be on a task or category.

Given these are small pieces of data it would take ages for the data to get to any size that would be a problem but it would be good to have ways to clear/manage history which will likely have to slowly be added so its not a tonne of new UI in one go.

This would also help for some of the other feature requests e.g. git style burndowns for sessions done.

[wennerryle]

Main reason I was asking about categories was if the log of time spent wanted to be on a task or category.

I'm personally would like to keep it as a category, because I don't use tasks in App (i have github/gitea issues for it).
But, as I said there's no big difference between category and task, so I can use tasks as a category instead. If you'd like to seperate these entities on UI level, we can just add boolean column at the table that indicates that it's a category.

[sekwah41]

Tbh being able to track against a category itsself would be handy as i do work on things while not on tasks ive written out. I think i misunderstood what you meant by using tasks as categories earlier.

[wennerryle]

Okay.. Look:

Category:

• id
• name
• description
• created_at

Task:

• id
• name
• description
• created_at
• status (I could use task as category, and just don't change status.. so it'll be always open task)

Log:

• minutes
• type
• task_id

It's almost the same thing, they self replacable
Or..
Task that includes other tasks is a category (but, if we want to implement it that way, we should add parent_task_id)