I'd like to fully adopt Zettlr but the inability to traverse related files is a bit of a bummer. I'm not a big fan of heirarchical data structures and I use Markdown as a form of knowledgebase alongside TheBrain. Given the craze around Roam Research and the ability to do backlinking, I think it would be a good enhancement. It would be nice to have the ability to configure the linking syntax alongside that which you can currently do. I'd like to be able to use the current default syntax ( ]) to do one-way links and the varient of ]] to have the backlink generated. If you don't use the new syntax a backlink won't be added to the destination file. I think this would be best suited as a varient of the current linking syntax. It's really cool to see truely opensource tools being developed actively :) DescriptionĪbility to have Zettlr automatically prepend backlinks to beginning of destionation files in the event they are linked to from another file.
#Zettlr alternatives Patch
On Jan– nine months ago – I released Zettlr 1.8.6, beginning the release notes with the sentence “This is the last patch before we begin working on Zettlr 1.9, which will feature much better flexibility in exporting.” How modest I was.Very briefly, I've just discovered Zettlr and I have to say, it's absolutely awesome. Instead, what we are looking at today is not Zettlr 1.9 but Zettlr 2.0, and we are not just looking at better flexibility in exporting. We are looking at a wholly new application! I think I decided to develop Zettlr 2.0 rather than 1.9 sometime in March, when I realized that the amount of changes I put in were already so many that I couldn’t justify just a minor revision – no, it had to be a major revision.Īnd here we are, after nine months of development, nights and weekends spent just to make this the best experience possible. It has been an incredible journey, and I learned so much along the way – not just in terms of coding because I finally understand the benefits of Maps and Sets, but also in interaction with you, the community. We now have a community Discord server (which I warmly invite you to join!) and more and more discussions on our new GitHub Discussions forum. In general, I think the community around Zettlr is finally flourishing, and it’s amazing to see!īut let’s return to the reason we are all here today: To celebrate the release of Zettlr 2.0! This blogpost will be structured as follows: First, I will say something general about what has changed in this release. Then I will go on to spotlight a few especially notable changes of which I’m specifically proud.
#Zettlr alternatives how to
In a third section, I will give you some advice on how to upgrade safely. Lastly, I will dedicate a section to the incredible support I had during development of 2.0, before closing with some final thoughts. What you are looking at today is the result of months of hard work. The driving force behind the fully rewritten and redesigned app was twofold: I really wanted to make Zettlr 2.0 the best version it could be, and I think I succeeded for the most part.
Zettlr is not a website or some web app, but a real desktop app. And as such, it should look and feel like a desktop app.
#Zettlr alternatives windows
To accomplish this, I read through and implemented the Apple Human Interface Guidelines, the Windows Metro UI Design Guidelines, and the GNOME Human Interface Guidelines. Zettlr 2.0 will look native on all platforms for the first time, and to the best of my knowledge, Zettlr 2.0 is the only Electron app that looks native.
But even then I knew that the real 1.0 release was still not ready yet, and in fact today I’m convinced that Zettlr 1.3 was the actual 1.0 release, where everything I initially envisioned was implemented.
0 kommentar(er)
