Using types to check your code for possible logical errors is one of the most efficient ways to check, for instance, that you are indeed working with a file descriptor, or rather with just a number. Indeed, having the option to code using TypeScript was one of the biggest blessings of the year. This has enabled two things: First, the size of the app was drastically reduced, and second, due to the availability of TypeScript I have managed to kill off a lot of bugs that went unnoticed so far.
While it did have quite some bugs for some time, the work did pay off, because now a lot more is possible with regard to file management (and only a few dozen lines of code divide Zettlr from a full code editor such as VS Code).īut there was an additional improvement that has done even more for Zettlr: The switch to Electron forge and the beginning TypeScript migration in 1.8. The first big improvement this year was the File System Abstraction Layer that was implemented in version 1.7.
But, additionally, this year I had much more time to work on Zettlr in my free time – it seems as if it does save time when you don’t go to the pub every other day ) Of course, this was a mixture of different aspects – I am a much better JavaScript developer now than three years ago, so my development speed had to increase either way. However, instead of becoming less productive, I was able to cramp more and more features and enhancements into the app than ever before. I won’t go over all the nifty details again as I did last year, but provide a more broad overview over what has happened in this crazy year.Īs so many other things, the development of Zettlr has been influenced by the year 2020 quite fundamentally. I can't stand one more MS magic trick to auto-formatting on copy-paste (while mangling half of the.Three years ago, the first version of Zettlr has been released to the public.
I have moved them to the WYSIWYG-on-Markdown editor Zettlr, and my non-technical writers have praised it for being "almost-not-techie at all". I've been using MS Word with a heavy reliance on Track Changes for years, and I'm converting my technical writing department to use Markdown as fast as I can. And you can access and edit the same collection of notes (which is just a bunch of. It's open source, gratis, and based on markdown, so you neither have to pay anything nor worry about the future of your notes. r/askphilosophy Open Discussion Thread | December 13, 2021 Zettlr is open source and has export-to-PDF. Typora alternative? (or any desktop Markdown editor with export to PDF?)
But most of those bullet points will be linked to separate notes for each major NPC, location, and handout (along with PC notes and. The actual session prep is short, with maybe a dozen bullet points total across the different categories. In the campaign I've been running this summer, I use Obsidian (), with a template for session prep loosely derived from Sly Flourish's Lazy Dungeon Master. Hey Keepers, how and how much do you prepare your Sessions? Do you even prepare things or do you improvise? Old-school with a big folder or using your laptop? Would love to hear that! Cheers! ) It’s completely cross platform, with Windows/Linux/macOS/Android/iOS versions.