1,946 karma · joined March 18, 2017
rob@markwhen.com
This came to be because, while working on markwhen.com, I realized I wasn't doing enough marketing or just talking about what I was working on in general. So I'm using the thing I'm working on to blog about it.
I hope to eventually include the ability to cross post to other platforms and maybe also send out emails.
jQuery('body').bind('cut copy paste', function (e) { e.preventDefault(); });
jQuery("body").on("contextmenu",function(e){ return false; });
Like, holy hell, I'm just trying to keep the lights on by doing some small thing every day. Apparently it pays off over time though, and it's helpful to have someone point that out to you.
I think sometimes it's easy to forget how far you've come when you're in the thick of it day in and out.
Compared to what I'm currently working on (markwhen.com), what I like most about this old version is there are only two buttons. The cognitive load for someone using this old page is much lower because there's quite simply less you can do.
Total Requests PER MONTH --- PRICE PER MONTH
Up to 500 --- $149.00
Up to 1000 --- $289.00
Up to 2,500 --- $699.00
Up to 5,000 --- $1,299.00
Up to 10,000 --- $2,499.00
[0]: https://en.wikipedia.org/wiki/Kramatorsk_radiological_accide...
I think taps are supported, I don't even know if you can scroll in a widget?
Obviously I have feature requests for supporting both larger and smaller time scales so I'll have to figure something else to do. My initial inclination is to virtualize the scrolling, so the element has a minimum and maximum width, and when the user zooms in and out (beyond/close to the min/max) I reset the view and the scroll position. You definitely have to hide the scroll bar in this scenario as it would be jumping all over the place.
[0]: https://github.com/mark-when/markwhen/blob/9823e44d0445d3bf1...
[1]: https://github.com/mark-when/markwhen/blob/main/src/Views/Ti...
> As we port screens to RN, we also look out for opportunities to improve the UX of the app.
I would be curious to hear more about how this went - in my experience trying to do two things at the same time can lead to trouble, tempting as it may be (was it the migration or the upgrade we did along the way that caused this new bug?).
In a similar vein except for plotting events that I've been working on
I wanted to make my own but ended up making a timeline maker and have kept working on it since (markwhen.com)
Something for next time, you might get faster/more visibility if you put the url in the link field. I had to scour for it in the description (not really, but you know)
I'd be interested to see what you're working on!
So cheeaun here posted his life timeline project[0] 9 years ago (!) to hacker news[1] and I always thought it was pretty neat. I made a tool to make timelines like that and it has since evolved into markwhen.
[0] https://github.com/cheeaun/life [1] https://news.ycombinator.com/item?id=6833565
`2022-08-02T23:00:00.000Z - 2022-08-03T00:00:00.000Z: Event`
but in general I do need to figure out a way to allow more customizable date parsing.[0]
The upstream repo that the live site uses is available to sponsors.
I’ve used it personally to help plan and coordinate my own wedding (https://markwhen.com/rob/wedding) and for keeping track of life events, and I’ve seen it used for event planning, project management, and to visualize historical events or periods of time.
I personally like tools that let you immediately start using them, and I set out to do that here with markwhen.
Let me know if you have any questions!
Make timelines from markdown-ish text.
All I ask is that you think of something better than putting “Scan Me” next to or inside the QR code.