Rnote, an open-source vector-based drawing application, continues to evolve with significant recent activity aimed at improving user experience and expanding its global reach through localization.
Recent issues and pull requests (PRs) highlight ongoing challenges and enhancements in user input handling, particularly with stylus interactions. Notable issues include problems with the selection tool (#1225) and platform-specific build failures on Windows (#1228). Feature requests for UI improvements, such as fullscreen mode adjustments (#1229), indicate a focus on usability.
Felix Zwettler (flxzt)
github-actions[bot]
Weblate (bot)
RayJW
Doublonmousse
michal-mnich
The development team is actively addressing bugs and enhancing the user interface, indicating a strong focus on improving user experience. Translation efforts are robust, showcasing community engagement and a commitment to internationalization.
Timespan | Opened | Closed | Comments | Labeled | Milestones |
---|---|---|---|---|---|
7 Days | 10 | 4 | 19 | 3 | 1 |
30 Days | 26 | 13 | 54 | 4 | 1 |
90 Days | 56 | 34 | 132 | 6 | 1 |
1 Year | 252 | 147 | 638 | 14 | 1 |
All Time | 720 | 456 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
Developer | Avatar | Branches | PRs | Commits | Files | Changes |
---|---|---|---|---|---|---|
Felix Zwettler | 2 | 4/2/1 | 8 | 55 | 7576 | |
Weblate (bot) | 1 | 2/2/0 | 2 | 13 | 1724 | |
MichaĆ Mnich | 1 | 1/1/0 | 1 | 1 | 422 | |
Doublonmousse | 1 | 1/2/0 | 2 | 8 | 292 | |
RayJW | 1 | 2/1/0 | 1 | 1 | 53 | |
github-actions[bot] | 1 | 0/0/0 | 2 | 1 | 8 | |
EDllT (EDLLT) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (OB0NE) | 0 | 2/0/1 | 0 | 0 | 0 | |
zefr0x (zefr0x) | 0 | 1/0/0 | 0 | 0 | 0 | |
None (TecCheck) | 0 | 0/0/1 | 0 | 0 | 0 | |
None (anesthetice) | 0 | 1/0/2 | 0 | 0 | 0 | |
Ethan Martin (yuckdevchan) | 0 | 1/0/0 | 0 | 0 | 0 | |
Jonathan Niklasson Godar (JonathanGodar) | 0 | 0/0/1 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Rnote project has seen significant recent activity, with 264 open issues and a variety of feature requests and bug reports being actively discussed. Notably, issues related to user input, such as stylus behavior and touch interactions, dominate the conversation, indicating potential usability challenges for users relying on these features.
Several issues reveal recurring themes, particularly around input handling and UI responsiveness. For instance, users report problems with the selection tool not functioning as expected when using stylus buttons (#888) and lag during drawing (#653). Additionally, there are multiple requests for enhanced features like customizable shortcuts (#590) and improved document management (#911).
Here are some of the most recently created and updated issues:
Issue #1232: Ability to select one object by tapping when in "Select with a polygon" or "Select with a region"
Issue #1229: Hide headerbar in fullscreen mode
Issue #1228: Cannot build on windows
Issue #1225: Selection tool selects the PDF instead of annotations
Issue #1224: Add an option to make the imported PDF replace the canvas
Issue #1222: Unable to select text using stylus
Issue #1220: "Copy Cut Paste" menu appearing when it should not
Issue #1217: Enormous PDFs Exports
Issue #1215: Canvas goes crazy after moving or zooming it
Issue #1212: Add canvas rotation, not only zoom and move.
The issue regarding the selection tool selecting PDFs instead of annotations (#1225) highlights a significant usability concern that could frustrate users who rely on precise interactions within their notes.
The inability to build on Windows (#1228) indicates potential platform-specific challenges that could hinder user adoption among Windows users.
Requests for enhancements like hiding the header bar in fullscreen mode (#1229) and adding canvas rotation (#1212) reflect a desire for improved user experience and customization options.
The ongoing discussions about performance issues related to input lag (#653) and cursor misalignment (#779) suggest that these are critical areas needing attention to enhance overall application responsiveness.
In summary, while Rnote shows promise as a versatile note-taking tool, addressing the highlighted issues will be crucial for improving user satisfaction and broadening its appeal across different platforms and user scenarios.
The analysis of the pull requests (PRs) for the Rnote project reveals a dynamic development environment with active contributions aimed at enhancing functionality, improving performance, and expanding localization. The PRs cover a wide range of topics, from bug fixes and feature additions to updates in dependencies and improvements in user interface elements.
glib-compile-resources
before falling back to the glib_build_tools
crate.glib::clone
macro, improving code maintainability and compatibility with newer versions of libraries.cargo-nextest
for improved testing workflows, though it was not merged.The PRs indicate a healthy mix of maintenance work, feature development, and community-driven localization efforts. The presence of PRs like #1227 and #1223 shows active bug fixing and enhancement of build processes, which are crucial for maintaining software quality and developer productivity.
Localization efforts are evident from PRs like #1219 and #1202, highlighting the project's commitment to reaching a wider audience by supporting multiple languages. This is further supported by community contributions through platforms like Weblate.
Feature enhancements such as those proposed in PRs #1211 and #1210 suggest an ongoing effort to expand Rnote's functionality, making it more versatile for users. The addition of support for Windows ARM64 is particularly notable as it reflects an effort to broaden the platform compatibility of Rnote.
The closed PRs also reveal a focus on updating dependencies and improving code quality through refactoring (as seen in PR #1218). This is essential for long-term sustainability as it helps in keeping the codebase modern and easier to work with.
However, there are instances where proposed changes were not merged (e.g., PR #1209), which could indicate either incomplete implementations or changes that require further discussion or refinement before they can be integrated into the main branch.
Overall, the pull request activity in the Rnote project demonstrates a vibrant development ecosystem with active contributions from both core developers and the community. The focus on bug fixes, feature enhancements, localization, and code quality improvements suggests a well-rounded approach to software development that prioritizes user experience and software reliability.
Felix Zwettler (flxzt)
github-actions[bot]
Weblate (bot)
RayJW
Doublonmousse
michal-mnich
Active Development: The team has been actively fixing bugs, particularly around user interface interactions and document management features. This indicates a focus on improving user experience.
Translation Efforts: There is a strong emphasis on internationalization, with multiple contributors involved in updating translations across various languages, showcasing community engagement.
Collaboration: The development process involves collaboration among team members, especially in translation efforts where multiple contributors co-author updates.
Refactoring and Dependency Management: Recent commits show a trend towards refactoring code and managing dependencies effectively, which is crucial for maintaining code quality as the project evolves.
User-Centric Improvements: The focus on fixing silent failures in export functionalities suggests a commitment to enhancing the reliability of core features that users depend on.
Overall, the development team is making consistent progress towards enhancing Rnote's functionality while fostering community involvement through translation contributions.