QuestPDF Companion #621
Replies: 1 comment
-
I've upgraded the QuestPDF Companion project to Avalonia 11. While a few adjustments were needed, the official guide is detailed and accurate. I'm genuinely impressed with the new version's stability. Those quirks and glitches I ran into earlier are fixed now. Turns out they were library bugs, not my lack of understanding, which gives me more confidence. Kudos to the Avalonia team; the new version is very imposing! I am planning to share a few screenshots soon, followed by making the code public. While it's still a work in progress, the current version gives a glimpse into the direction I'm taking. I'm at a crossroads about continuing with Avalonia or switching gears to Flutter. However, it's less about the platform's evolution and more about the overall development paradigm. With rumors of Flutter possibly transitioning to the Propeler engine and away from Skia, I fear future integration challenges between QuestPDF and the Companion tool. This effort is not my highest priority at this moment, so there is still time for experimentation 😀 |
Beta Was this translation helpful? Give feedback.
-
Introduction
The QuestPDF Previewer application is an innovative tool designed to showcase a real-time, dynamic preview of a document presently under development, utilizing a hot-reload mechanism without requiring code recompilation. This concept, originally proposed and initiated by @bennetbo, has proven immensely beneficial and worth further enhancements.
Planned capabilities
The QuestPDF Companion is envisioned as an evolved successor to the Previewer application, offering a set of additional features and functionalities that include:
Current Status
This next-generation previewer project has been in active development for several months. While a considerable portion of the application has reached completion and demonstrates stability, I've encountered some peculiar issues while using Avalonia 10. These challenges could be attributed to my limited familiarity with the library, possible incorrect usage, or pre-existing bugs and issues. My daily work involves modern JavaScript technologies such as Vue.js, making the experience with Avalonia seem unproductive and unnecessarily complex.
Roadmap
In light of the frequent problems, while developing the new version's implementation, I have chosen to reassess my strategy. Currently, I am contemplating two potential paths:
Investigate Avalonia 11
This recent release appears to demonstrate superior quality. Many of my existing difficulties might be readily resolved, improving my satisfaction with this library as a solid foundation and enabling me to keep up the progress achieved over the past few months.
Investigate Flutter
This library, written in Dart and similarly built upon the Skia library, is architecturally closer to modern frameworks, potentially diminishing future development costs. Although my understanding of this library is still at a foundational level, I am notably impressed by it so far. Nevertheless, this route does present a handful of potential issues, for instance, the inability to release the application as a dotnet tool.
Afterword
Over the upcoming weeks, I will update you on the progress regularly and hopefully gather valuable feedback.
Beta Was this translation helpful? Give feedback.
All reactions