agateblue / tempo Goto Github PK

Instead of GitLab pages

Hi,

First of all thanks for taking the time to thoroughly document that tool for others. It is already really useful to me.

The synchronization features started to throw errors, but I only realized it when try to force sync and saw a not found message.
Here's a screenshot of what happens :

Maybe it's a problem on my side but I have no clue to debug it. Do you have any idea ?

Thanks and have a nice day.

It would be great that new blueprints were activated by default

I setup my CouchDB server on my home PC using docker. It is up and running, and I created a "tempo" database all ready to sync. However I cannot get tempo to sync. I get a "Sync OK!" message when I input my database information (I had to unblock insecure content on Vivaldi since I'm just using my local IP with insecure http://).

I checked developer console. It seems I get a 200 back for the _session request (which is sending my username and password in the request header). That's why I get a "Sync OK" message in my browser page.

When I try to actually sync, I get 401 unauthorized. It seems the credentials are not being sent in the request headers. Any help would be appreciated. Thanks.

When clicking on the home button "Tempo", in the top left corner, the URL changes and removes the tag query, but the tag isn't cleared, I think it would be nice to remove the tag by clicking the "Tempo" button instead of having to go to the Search bar and remove the tag. What do you think?

J'ai pu observer plusieurs comportements étranges sur le parsing de mood. Typiquement j'utilise souvent des -- pour séparer des éléments quand j'écris, ils sont ici parsés comme un tag de "bad mood":

Exemple:

#test

- test
a + b = c 
oh -- no ++ ? heeeh
--bad-mood
------very-bad-moood
++++++++yaay

++good_mood ?

Ici, le -- est considéré comme un marqueur de "bad mood", alors qu'il ne devrait pas. Ça ne le fait pas sur le ++.

Aussi il semble y avoir une limite sur le nombre de + à la suite (je suppose que c'est le même comportement pour les - ?), ça fait effectivement ptet pas trop de sens d'en mettre des tonnes, mais je sais pas si c'est nécessaire de mettre une limite ?

Lorsqu'on a des # dans un bloc de code, l'affichage déconne parce qu'il le traite comme un tag !

résulte en :

Right now, exporting data is made through two separate UIs:

• one in the Tasks tab
• in the Advanced tab, in the diary

Ideally, this should be doable in a single place.

To avoid weird duplicates because of extra whitespace

I noticed a bug with time display. For my timezone (eastern US), if I enter a diary entry beyond 7 PM, then the calculated time displaying in the diary is a negative number (-1, -2, -3, etc). I think there is a bug in this function:

Why not use built-in javascript function for displaying local time:

date.toLocaleTimeString([], { hour: 'numeric', minute: '2-digit', hourCycle: 'h24' }))

Hi !
Ok so this might be a weird one: I would like to be able to set the time of day at which the day begins. I know, it sounds weird, but hear me out. I will often add entries after midnight, but before sleeping. Ideally, I would like events before say 4AM to be added to belong to the day before. This has been one of my biggest frustrations with several mood trackers I've used in the past, and I feel it's way easier to implement it in JS than to go to bed early everyday.

What I'm seeing is something like this:

• at a "Shift start of day by" setting
• adjust dates in calendar
• fix groupByPeriod (this one might get pretty tricky) to enforce this as well
• fix the query filters as well

Coucou !

Bon j'ai un turbo bug sur les groupByPeriod dans les visualisation des blueprints, voici:

Je commence par aller sur l'onglet data, et pour le blueprint Diary, les données sont formatés de la facon suivante:

Si je veux changer l'affichage du groupByPeriod (j'ai pris l'exemple du day of the week, mais c'est buggy sur chaque truc), ça ne change rien cf:

En revanche, le comportement observé n'est pas le même dans la partie Visualisation quand on edit un blueprint:

Observation initiale:

Puis je change en day of the week, qui est bon:

Mais ensuite, si je veux re-changer pour un autre machin, bah ça reste sur le premier que j'ai pris ; ici ça continue d'afficher en Day of The week:

Le calcul de mood instability semble buggy, en effet:

• je fais une entrée avec des tags positif et négatif, le calcul qui va être fait pour cette entrée va donner une valeur + ou - en fonction de la somme des tags.
• Si le même jour je n'ai qu'une seule entrée dans laquelle je mets des tags + et -, le résultat c'est que dans le mood instability on se retrouve avec une valeur de 0, puisque la seule entrée a uniquement une valeur finale soit positive soit négative.

La solution temporaire c'est de split les entrées en une contenant tous les tag neg, et l'autre contenant que les tag positif, mais du coup je suppose que c'est un bug :D

Sometimes, you might want to easily reuse previously inputed values in a form.

Hey first off all nice and perfect software u created her. im using it since a few days and yeah didnt find something else that would be better in any possible way for my use Just perfect.

So i wanted too ask. Whether it would be possible to change the default blueprints.
These can currently only be viewed.
But I would like to add a few extensions to the mood "default" tag,
(wanna add a mood ground level like hows ur daily "mood" from 1-10points with a extra graph and some more details)
The main point would too change the Visualization or, more precisely, too change the art of the graphs from the defaults.

Idk but maybe something like a setting too unlock this so that any person that us it can not change anything unintentionally.
and "destroy" his complete tempo data.

ty for answers
mfg Alkralys

hope u can understand this bulli english from me xD

There is a small but annoying delay when a new note is created. We should remove it to improve UX and avoid confusion.

Hi! is there a way to filter out the blueprints data, I would like to see only the manual text entries, without having to add a tag to each of them, is this possible? :)

I tried to search for ! is:form, but it doesn't display anything.

Also, thanks for you work, tempo is amazing :3

When searching for a tag in the search bar, it needs to be written without the '#' in front of it, which might not be an habit for new people
It would be nice to be able to search both for #tag and tag all the same, what do you think? :)

When loading the app, and setting up a kanban board for the first time, the UI crashes, even though the config is saved.

Hello 😊

I am making a blueprint and wanted to add a time field but the "date" type field only allows for dates (hence the name, sure :D). But I think it would be nice to have a "time" type field, and maybe also a "datetime" type field too.

It would be useful, e.g for groceries or packing before a trip

It would be amazing to hook the ctrl+s keys to save the blueprint (because it's kind of a habit for many people) :D

When adding past date entries to the diary, they show up on top of the list instead of being sorted descending by date.

I have yet to reproduce this reliably, but there seems to be an issue with notes submitted around midnight getting a wrong or future date, which causes a crash.

The data visualization is amazing, but every time I want to check some graphs I have to got to the Data tab, and then select the proper blueprint to display, because I usually don't want to check my mood (yeah I know Tempo is a mood tracker :D). It would be amazing to be able to set another blueprint as default !

Hey there. I'd love to use Tempo alongside a Discord webhook, so that the diary entry appears on Discord every time I post one on the website.

The problem, is, Tempo doesn't seem to post the actual content of the entries. I checked with https://webhook.site, and it's just an empty request.

Description

When creating a new journal entry (with the default form or another) and setting a custom datetime, the date is ignored and the datetime is set to now instead.

Steps to reproduce

1. Write a new entry
2. Set a custom datetime
3. Save
4. The entry appears to have been written right now

Workaround

Editing the entry afterwards allows to set the right datetime (although this sometimes glitches too, sometimes the Save button just does not work.)

Extra info

Tested and found to occur on both Firefox 116.0 and Chromium 116.0.5845.96 (officially packaged versions) on a Debian Sid system.

Sometimes, I do repetitive tasks with many subtasks. Typically, doing groceries or packing my luggage often involve similar steps, and retyping everything everytime is annoying.

A thing I have in mind to help with that is to support saving tasks as "templates" that can be reused at a later time.

Quand on édite un tag annotation, le contenu n'est pas re-parsé, il faut nécessairement l'éditer dans les champs en dessous. Je pense que ça ferai sens d'avoir un re-parsing de l'entrée.

Par exemple, je veux créer 2 annotations:

Je me suis ratée, ça donne ça:

Donc j'édite pour remettre le retour à la ligne, ce qui donne:

Je pense qu'il serait préférable que la valeur du tag soit prise jusqu'au \n ou s'arrêter avant si il y a une autre annotation ? Et sinon juste pour l'édition, re-parser l'entrée pour corriger les valeurs.

CouchDB security is a little confusing. I have my "admin" account listed as an admin on my tempo database, but I have no "members" listed. According to CouchDB documentation, if no "members" are listed, the database is public. Therefore my tempo database is public, if someone gets my url and database name, they can see all my information. Not cool.

Now, as soon as I add a "member" to the database in CouchDB (whether that be an admin account or a regular user account), tempo webapp can no longer sync. As soon as I remove members (making my db public) it is able to sync again.

Can you check your pouchdb code and make sure that it is requiring CouchDB auth, not just for adding rows to the database, but also for retrieving rows. The current behavior makes me think that the tempo webapp is retrieving the database without sending authorization, and only uses authorization when adding rows to the database.

See pouchdb authentication recipes for more details on CouchDB security and settings for pouchdb.

Description

In the default diary view, notes are displayed in the order they were created (the most recently created first), instead of being ordered by timestamp. This means, for example, that notes created with a timestamp in the past are listed at the top of the list, above notes with a more recent timestamp.

Refreshing the window does not work. Even starting with a fresh browser and setting up CouchDB sync to pull the content results in the entries being listed in the incorrect order. The GIF below shows that.

Steps to reproduce

1. Create multiple notes with various dates in the past
2. The notes are listed in the (reverse) order they were created and not according to their date

Workaround

None that I could find.

Extra info

Tested and found to occur on Firefox 116.0 (officially packaged versions) on a Debian Sid system.

I was hoping you could add some documentation (to the readme file?) regarding how to use blueprints to visualize data.

For example, you show a little bit how you can use @ labels to document data points (lab values, weight, etc) , but I cannot figure out how to visualize that data on the graph section.

Thanks.