Congratulations on the release. I've been following this project for a while and it's great to see this. I agree with many others here about an obsidian plugin but no rush. The work you've done here is amazing.
Show HN: Markwhen: Markdown for Timelines
51–60 of 60 posts
Re: Show HN: Markwhen: Markdown for Timelines
#52This timeline component is gorgeous, I would love to use it as a lib for some other project
Re: Show HN: Markwhen: Markdown for Timelines
#53The pricing structure I'm going for is offline == free, online/collaborate == paid. There's a promo code on the most recent blog entry ( https://blog.markwhen.com ) for those who are interested
As others said, markwhen is awesome, but I'm not sure I'd use it as a standalone tool. I would definitely pay for a VSCode and Obsidian plugin to easily integrate it in existing workflows.
Is there any way to accept pledges for such plugins to gauge how many people would really pay for it, and how much?
Re: Show HN: Markwhen: Markdown for Timelines
#54Great work. Nice blend of aesthetics and simplicity of building the timeline.
Along with embed link, I was wondering if there is a way to download the HTML of the rendered timeline directly. I use static pages for my blog and would love a way to add the rendered output directly.
Re: Show HN: Markwhen: Markdown for Timelines
#55Great work. Nice blend of aesthetics and simplicity of building the timeline. Along with embed link, I was wondering if there is a way to download the HTML of the rendered timeline directly. I use static pages for my blog and would love a way to add the rendered output directly.
The CLI[0] outputs html in one self-contained file
Re: Show HN: Markwhen: Markdown for Timelines
#56Earlier quoted context omitted.
I vouched for this because while it does not relate to using markdown to create gantt & timeline charts, it does relate to using code to create said charts and is therefore IMHO a relevant comparable tool. See https://mermaid.js.org/syntax/gantt.html and https://mermaid.js.org/syntax/timeline.html Having said that, it's late tonight but I plan to give this markwhen a good look tomorrow when I'm fresh, because even be…
PlantUML does Gantt charts too completely off line if you want. Kinda ugly but surprisingly powerful. I have managed whole giant projects this way.
Thanks for the idea, I hadn't considered checking if PlantUML could do that...that's what I get for pidgeon-holing that tool for hierarchical state machines I guess.
Re: Show HN: Markwhen: Markdown for Timelines
#57I wanted this to be awesome, but on iPad (Safari/WebKit) all entries in the example are dots with no time length.
Oh :/ Even after zooming in? Or zooming in doesn’t work?
Ok, indeed: default zoom is 1920 to 2140, just in case my projects last 120 years.
If I zoom to 2023 to, say, 2025, it makes visual sense.
Do you have or plan to let timelines or subsets of timelines be embedded with kroki.io and/or Mermaid, and later support for e.g. pandoc (.svg and .png fallbacks)?
Re: Show HN: Markwhen: Markdown for Timelines
#58Random feedback: - On an iPad Pro (iPadOS 16.1.1 - not sure how current that is offhand), the UI is extremely unintuitive and/or broken. Tapping the example landed me in an editor that then took far too long to figure out how to get out of. - It remembers that the editor is up. Once up, getting out and back to the homepage is next to impossible until you figure out the UI (clearing cookies probably would have worked,…
Thank you for the candid feedback.
> on iPad the UI is extremely unintuitive and/or broken
The benefit of the desktop is being able to hover over buttons, most have tooltips with descriptions. This is not an excuse necessarily but I would liken it to landing on github.dev or vscode.dev without having seen or used VS code before. I really hate walkthroughs with tooltips (both as a user and a developer) but maybe I'll have to do something like that. What I do like about the current UI is that, by keeping control elements on the side and tabs on the bottom, I can have a consistent experience across devices and screen sizes.
Drawing more attention to the fact that there is a tabbed interface might help, seems like that was an issue.
Re: markwhen's syntax - I'll tell you what I like about it first, and then get into some of your points. I like that it is quite progressive. You don't need a header to start, nor groups, nor ranges necessarily, and you shouldn't have to think much about date formatting.
``` 1 Aug 2023: hi ``` is a valid markwhen document. If a list of dates like that is all you need, that's great. If you need ranges you can add ranges. Need groups, add groups. Need metadata, add a header. I like that it follows a new user's experience, you don't necessarily have to start with everything from the beginning.
On groups and sections, people wanted nesting, soooo the simple hashtag syntax wasn't going to work without an end hashtag or something. So it doesn't mean nothing, it means the end of the group or section. Idk, I'm open to suggestions about it. I personally don't use nested groups and sections that much but people wanted it. There has to be some endGroup or endSection syntax I think, even if it's not those specific words
Re: Show HN: Markwhen: Markdown for Timelines
#59Wow! This is cool. Love how the documentation is done
Re: Show HN: Markwhen: Markdown for Timelines
#60Hi Rob, I love the concept. I've played around with it for about 20 minutes now. I use obsidian for almost all my notes and documentation because I like keeping everything as close to plaintext as possible. I also currently use Omniplan for timelines and Gantt charts, so that is what I would be comparing Markwhen to, in terms of functionality. Omniplan is a very mature app and I recommend giving it a try if you haven…
Also agree, Obsidian plugin would be amazing!