Hi everyone!

This discussion is opened as I am preparing to release RichCanvas v3.0.0, the most mature and reliable version so far. I've been working on this for more than 2 years (since v2.4.2 was released). I know it's been a long time, but hopefully from now on RichCanvas will improve further and with a more constant pace.

I want to say thank you for your patience and for sticking around, providing input or simply using the library and giving the repository a star ⭐. I hope RichCanvas still fits your needs, if not I hope the next versions will do 😄.

⚠️ Disclaimer: This roadmap is informative, it represents my ideas of what I think RichCanvas needs or misses in terms of features and it's still subject to changing. Any feedback or ideas is welcomed that's why this is an open discussion. Bare in mind that bugs or issues with versions should be raised accordingly in the Issues section.

🧪 UI Automation Tests

As of v3.0.0, UI Automation Tests were added, together with a new App needed for the tests. The test project is based on FlaUI library. With this addition I aim to make RichCanvas a more reliable, scalable, maintainable and robust library where new features can be adopted easily without breaking existing ones.

• Streamlining UI Automation Tests API - improve AutomationElement classes for RichCanvas and RichCanvasContainer controls to have a reusable API with their default functionalities.

• Refactor UI Automation Tests Project - refactor the project, use the improved API from above, improve tests. Make them as small as possible, easy to read and understand. Better separation inside the project structure. Make tests layout and size agnostic and fetch visual points and data from the app without hard coding them.

• Refactor UI Automation Tests App - refactor the WPF application used for UI Automation Tests, make it more user-friendly. It should showcase all possible features from RichCanvas. Make it easy to use outside testing project, as a demo app.

🆕 New features

Next features planned for future versions, check the table below for priorities (or comment below if any feature should take priority). Of course, this can change based on your feedback, any technical constraints or just priorities shifting.

• Sizeable RichCanvas - RichCanvas v2.0.0 added a new feature trying to limit size of scrolling and panning (ExtentSize and EnableNegativeScrolling properties). The feature was removed completely with v3.0.0. The idea of the new feature is to have the possibility to define a size for your RichCanvas and all functionalities that depend on the size of the control should be limited to that.

• Selection Mechanisms - adding new selections mechanisms like appending, restarting selection, canceling, etc. (feedback suggestion are welcomed) with new configurable input gestures.

• Auto-Panning Edge Distance - as suggested in issue Improving AutoPanning #28, improving auto-panning by adding an edge distance.

• Bring into view feature - the possibility to bring into RichCanvas viewport any RichCanvasContainer.

• Fit to screen feature - fit as many items as possible in the viewport using necessary zoom updates.

🛣️ Roadmap planning

Table below shows the rough roadmap of plans above. The priority it's from top to bottom ( 🧪 UI Automation Tests epic has the highest priority).