![]() Those people, due to the virtue of their skills, are very good at designing things, but not necessarily at making an app that feels “right” to users. This also determined the structure of those who would make use of Electron: Web developers. When Electron was first announced, many people took the opportunity to write a desktop-ready app, but with web technologies. The first goal I had was mainly driven by discussions internal to the Electron community. No more sluggish start up times and slow writing anymore! As a user, you will notice that when using it: Zettlr now feels snappy, fast, and reliable. But now, after four years of experience, my skills have advanced far enough that I can state that even internally, Zettlr will now look like a mature, production-ready app. But even in 1.3, and all the versions that followed, many aches plagued the app, because as I have pointed out on numerous occasions, before starting the development of the app in the Summer of 2017, I had close to no knowledge of JavaScript. 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. When I first announced Zettlr 1.0 it was rather because it felt nice to release 1.0 stable after exactly one year of development. Fix all the remaining teething troubles.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. 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. And as such, it should look and feel like a desktop app. Zettlr is not a website or some web app, but a real desktop app. ![]() 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. What you are looking at today is the result of months of hard work. Lastly, I will dedicate a section to the incredible support I had during development of 2.0, before closing with some final thoughts. In a third section, I will give you some advice on how to upgrade safely. Then I will go on to spotlight a few especially notable changes of which I’m specifically proud. 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. 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. 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 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. 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. 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. Announcements, Releases on October 15, 2021
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |