Timeline cascade maker
Use it here.
Setup should be as simple as
npm i and
npm run dev.
Thank you for the great tool! I love it! I noticed that the group and section features don't support nesting. It would be great to have that functionality so that more structure could be provided entries!
I want to be able to use a counter (that represents an arbitrary thing, not just dates) as the basis for events. For example,
5-20: Event 1 90-150: Event 2 45-68: Event 3
When I tried this in the live example, it treated it like a percentage and only went up to 100. It won't let me zoom out any more
Clicking on the Create Username button doesn't do anything. This makes cascade pretty much useless for me.
Chrome: Version 96.0.4664.110 (Official Build) (64-bit).
I'll take a look at the code
There isn't a single agreed standard about notating tasks in Markdown, but many tools now support something like
- [ ] incomplete task * [x] complete task
You have % completion. In order to improve interoperability with markdown used in other editors and task systems (e.g. NotePlan), please consider supporting at least the
[x] syntax to indicate 100% completion.
It would be awesome if the markwhen.com site could autosave and could present a list of timestamped autosave versions with an ability to jump back to an earlier version.
Hi. The tool is really good. I just have this feature req, which I believe many people would find useful.
In many cases events or project tasks need to have set their duration in a number of “workdays” ignoring weekends and maybe Public holidays. You could define your own public holidays in some array.
The idea is to set task durations in for example 7 workdays which will translate into a whole week plus 2 days long … so 9 natural days long.
Then if something moves in the project everything can be updated accordingly… discounting weekends.
I love this project. Apologies if you've already explained elsewhere, but should any assumptions be made on how long the server app will be up and running? In other words, is this an experiment, or is it meant to last for the long term? Many thanks.
I've tried and so far failed to be able to express my plan in Markwhen. The challenge in this case is it's not a forward-waterfall plan, but a working-back-from-an-immovable-deadline plan.
Ideally I want to write something like:
title: Annual Meetings 2023 (Markwhen plan) description: A summary of what's needed and when dateFormat: d/M/y #announcements: red before !ACM 2 month: revise voting eligibility list before !ACM 6 weeks: publish notice of ACM #announcements before !ACM 2 weeks: publish revised voters list 10/4/2023: ANNUAL CHURCH MEETING !ACM after 1 week: publish results of elections #announcements
The 'before' syntax isn't available, so I tried negative relative dates:
title: Annual Meetings 2023 (Markwhen plan) description: A summary of what's needed and when dateFormat: d/M/y #announcements: red --- after !ACM -2 month: revise voting eligibility list after !ACM -6 weeks: publish notice of ACM #announcements after !ACM -2 weeks: publish revised voters list 10/4/2023: ANNUAL CHURCH MEETING !ACM after 1 week: publish results of elections #announcements
but this doesn't work.
Is there an existing way to do this? If not, please add support for this kind of use case.
It would be great to have a VS Code extension, like PlantUML has, to edit and generate timelines in the IDE. It will make it quicker to iterate timelines.
~~When changing Tabs the site can become unresponsive on Firefox/Ubuntu.~~
By unresponsive I mean, that I can no longer input text in the editor and I can also no longer click anything in the UI/renderer.
I don't know whether they are related but I'm also getting several errors in Console saying:
Uncaught ReferenceError: TouchEvent is not defined r NuxtJS
These errors are being thrown when I move the cursor.
I also get the following error:
Error: Promised response from onMessage listener went out of scope
Foremost: I love this project. I have been playing around with it for hours and I want to use it for many things both private and at work. I would love it, if I could specify expandable / nested dates. Usecases are: Changing position at the same company, creating some kind of high/low level structure. I am not expecting you to implement this, after all, you have already selflessly open sourced this great project. Just in case you are looking for additions worth implementing, I would vote for this one!
Hi, thanks so much for this very nice tool. One thing that is missing is the ability to mark one task as dependent on another task. I think this is a fairly common feature and it can be quite useful as well. For example, I am imagining that you could have something like
11/2022-12/2022: Create Project Plan #Plan 2/2023-12/2023: Do project #after:Plan
and then you will get an arrow from the end of the "Create Project Plan" bar to the start of the "Do project" bar. Though I'm not sure how hard it would be to implement, I think it would be quite useful.
Currently, an event only supports Google Photo links, but it would be natural to support Markdown-style images as well.
I had looked into the code a bit and found it easy to implement within 30 lines using existing infrastructure (tested locally): https://github.com/utensil-contrib/markwhen/commit/aa046c277328ae9db4f68fd53c12ac931c2c7ac2 .
Since this repo is behind the developing repo, just post the code here to see if it could be useful somehow.
I may have missed this somewhere, but it would be nice if there were a button or keyboard shortcut to go back to "now" or whatever the current date/time is.
It would also be nice if you could command + click or ctrl + click to go to beginning or end of an event or time range so one could more easily jump around.
Then after jumping around, easily go back to "now".
TImeline in question (<50 events). The same behaviour applies to the
Be patient, it could take up to 30 seconds to generate as this is a server side opertion.
However, no output is generated even after 3 minutes.
Trying Markwhen now and love it!
However, the timeline I’m trying to do needs many instances of the same event on the same line returning several times in time, with breaks/cuts. Syntax-wise, it could be done with a comma:
1991-04 / 2009-08, 2010-06 / 2010-08, 2014-07 / 2015-02: Event name // This event returns a three different date ranges
Any name, colour, location, image added to the event will be kept across all the returns of the events. It would be laid out on the same line.
Apologies if this is already possible but I missed it or if it has already been discussed somewhere else.