https://github.com/Ebonsignori/obsidian-timeline-schedule

Inline timelines generated from human-readable time strings, e.g. 'Walk dog (30min)' in a ```schedule codeblock.
https://github.com/Ebonsignori/obsidian-timeline-schedule

Last synced: 5 months ago
JSON representation

Inline timelines generated from human-readable time strings, e.g. 'Walk dog (30min)' in a ```schedule codeblock.

• Host: GitHub
• URL: https://github.com/Ebonsignori/obsidian-timeline-schedule
• Owner: Ebonsignori
• License: mit
• Created: 2023-09-09T07:57:26.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-12-24T01:59:15.000Z (over 1 year ago)
• Last Synced: 2024-11-29T00:51:20.521Z (5 months ago)
• Language: TypeScript
• Size: 1.39 MB
• Stars: 14
• Watchers: 1
• Forks: 0
• Open Issues: 4
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• jimsghstars - Ebonsignori/obsidian-timeline-schedule - Inline timelines generated from human-readable time strings, e.g. 'Walk dog (30min)' in a ```schedule codeblock. (TypeScript)

README

        
# Obsidian Timeline Schedule

Inline timelines generated from human-readable time strings, e.g. 'Walk dog (30min)' in a ```schedule codeblock in [Obsidian](https://obsidian.md).

You can set if you want to enable pretty preview and/or autofill from the plugin's settings.

## Only autofill, no pretty preview

![Only autofill, no pretty preview demo gif](./docs/v1-with-autofill-no-preview.gif)

A `[Start]` and `[Finish]` block will always be present during autofill, and each line between them will be prepended with a time block e.g. `[9:30 AM]:`.

Each human-readable time string you add to the end of a line will be added to the next time block.

For instance, `Grind beans (3m)` sets the time from `[7:05]` to `[7:08]` in the next line.

In this mode, when your cursor exits the codeblock it will preview as a standard Obsidian code block.

While possible, autofill is **not recommended** within [callouts](https://help.obsidian.md/Editing+and+formatting/Callouts). I recommend writing your schedule outside of a callout, then pasting the codeblock in a callout to be rendered in pretty preview. 

## Only pretty preview, no autofill

![Only pretty preview, no autofill demo gif](./docs/v1-with-preview-no-autofill.gif)

In this mode, you don't need date blocks, e.g. (`[Start]`, `[Finish]`), the `start` date is set from whatever you put at the beginning e.g. "Start: 08/10/2023 08:00 AM"

If you omit a start line, the current date & time will be used.

# Both autofill and pretty preview (default)

![Both autofill and pretty preview demo gif](./docs/v1-both-modes.gif)

You can change the name for `Start` and `Finish` as well as the formats of the start, end, and event dates in the plugin's settings.

## Styling

See [styles.css](./styles.css) for a list of classes you can override.

## Installing

Search "Timeline Schedule" via the [built-in community plugin browser](https://help.obsidian.md/Extending+Obsidian/Community+plugins) in Obsidian.

## Contributing

Please [open an issue](https://github.com/Ebonsignori/obsidian-timeline-schedule/issues/new) with any suggestions or bug reports.

See [developer docs](docs/development.md) if you'd like to open a PR.

## Acknowledgements

[The Obsidian team](https://obsidian.md/about) for creating a wonderful product :purple_heart: