Timestamped notes

[robertmartin8]

Loving the project. One thing that would really make this ideal for me is the ability to timestamp notes, either by default or with a -t flag. I realise this may not be useful for everyone, so if you could point me in the direction of which file I should be modifying to achieve this (not too familiar with Go), I can just fork it and make those changes for personal use.

Robert

[sungwoncho]

Hi @robertmartin8. Notes are already timestamped. You can see the timestamp using view command.

▶ dnote v js 1
  • book name: js
  • note uuid: fd4f0711-8e69-4f33-85f0-5770c2e9575a
  • created at: Sep 13, 2017 10:42am (AEST)

------------------------content------------------------
case declarations do not create a new scope
-------------------------------------------------------

Is this what we need, and any other way we can improve it?

[robertmartin8]

Hi @sungwoncho, and apologies for the late reply.

I was thinking more as part of dnote ls. So right now if I type dnote ls reactjs, I get:

  (0) all class-based React.Component elements must have a render
  (1) in ES6, when the key and value are the same, you can just write { key }
  (2) when possible, use array.map rather than for loops

What would be nice is to have an option to view the timestamps (perhaps instead of the indices), so something like:

$ dnote ls reactjs -t

  (31/08/18 12:00) all class-based React.Component elements must have a render
  (02/09/18 16:45) in ES6, when the key and value are the same, you can just write { key }
  (02/09/18 18:30) when possible, use array.map rather than for loops

This is very much a personal preference thing, but I do think that this would greatly expand the functionality of dnote, allowing it to be used as a timestamped log. Often when I'm building projects I'd love to have a running log of what I'm trying, what I've just completed etc. dnote is the closest thing I've found, but it would be far more useful if I could see the timestamp right next to a list of the notes.

In any case, I respect your decision on your matter – this is a great project.

Best,
Robert

[sungwoncho]

I think timestamps can help with spaced repetition. Let's think about it.

Often when I'm building projects I'd love to have a running log of what I'm trying, what I've just completed etc.

That is a use case I haven't thought of, and I agree that timestamped list can be helpful. But it wasn't clear from your example. Could you explain a bit further?

[robertmartin8]

Sorry, the example was just meant to be what I envisaged a timestamp list would look like. With regard to the actual use case, imagine I'm doing some data science project.

 (31/08/18 12:00) Need to update my feature engineering. Going to start by denoising the variables.
 (31/08/18 13:05) Ran into a problem with data formatting. Normalised and removed missing data.
 (31/08/18 13:35) Fixed the features, now testing performance
 (31/08/18 13:46) Performance pretty awful, going to try [...]
etc

I appreciate that this is a pretty niche use, because I'm not sure how much people like to log what they're doing, but I personally find it useful to keep track of what I'm trying to implement and what bugs I face as I build the project. I could already use dnote for this in theory, but it's not ideal without the timestamp. I also think that this kind of logging is useful for transparency w.r.t paid development work.

[sungwoncho]

Interesting. I also do similar things with Dnote to log TODOs for immediate future. I might work on this feature later. In the meantime, I will consider a PR.

Meanwhile, if you would like to fork it and modify for your personal use, please look at this file
https://github.com/dnote/cli/blob/49754b58a407024f5280ce1f132ad61bf5d8eb56/cmd/ls/ls.go#L137-L146

To build the program, please run go build.

[robertmartin8]

Thank you for the pointer, will have a go at modifying it – but I don't trust my Go ability to submit a PR ;)

Robert