pajoma / vscode-journal

Lightweight journal and simple notes support for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=pajoma.vscode-journal
GNU General Public License v3.0
233 stars 40 forks source link

[Feature Request] scaffolding a whole year or a month #83

Open mameen opened 3 years ago

mameen commented 3 years ago

I like to propose a scaffolding feature where I can create a skeleton for the whole year.. this is just 365 files few bytes each!

I have many projects, and some are long running, some are personal diaries.. setting the root folder is great way to switch between them.. (maybe making this simples would be great!) but to get back to the topic! I sometimes like to create a new journal.. and want to populate it to help me plan the whole year or migrate my work from last year..

This great extension changed my life.. let me thank you again here.!

pajoma commented 3 years ago

This is an interesting idea.

First to your point about making switching a journal simpler: The journal supports scopes for notes and tasks. Not for journal itself, though. I could add a command to switch the default scope, which would also enable journal pages (because then also the shortcuts work). I am still not sure, if you still want aggregated views showing for example all tasks from all scopes on a single page.

Regarding scaffolding:

mameen commented 3 years ago

Regarding scaffolding, thanks for considering / thinking about it.. I believe less is better.. the bare minimal seems start / end date.. and skip weekends can be a global option to the whole journal..

. regarding migration I think external tool can take care of it.. hard-core geeks like myself even have their journal in a git repo.. so thank you for making our life easy.. but don't put too much in.. “Perfection is Achieved Not When There Is Nothing More to Add, But When There Is Nothing Left to Take Away :-P

pajoma commented 3 years ago

Scopes and Scaffolding don't mix. You can switch Journals by switching projects (and have different default base paths). I guess you can still link the two through scopes (Journal "website_a" with scope "private" and Journal "private" with scope "website_a"). The global journal setting would have "private" as base path, the workspace setting in the project "website_a" would override the base path.

Regarding scaffolding:

I add a new command "Generate journal entries". It starts a wizard with the following inputs 1) start date (full iso date, eg. 2022-01-01) 2) end date (full iso date, eg. 2022-12-31) 3) only workdays (yes/no)

The new entries will be generated in the currently defined base path (either in workspace settings or user settings)

mameen commented 3 years ago

That sounds good.. :-).. Thank you.. now I can enjoy using it without doing the work myself.. heheh..

in my attempt I was going to call it refill and was planning to ignore the weekend with the plan to have it in the settings to be shared maybe with the -view extension..

Thanks for taking care of us and the extension... i'm using it 80% of the time now.. the only missing piece now is not related to the extension but the fact there is no good base64 encoder for images .. that makes it annoying to store images when I do copy paste.. but this is a markdown issue the extension is very useful as is..

In the far far future maybe we can add archive option just to help with keeping historical records of old years.. :-) see I'm planning to use it for a long time..