Paving the Way for OCR & smarter settings

[BrycensRanch]

As everyone here knows, SnapX is our ambitious cross-platform port of ShareX. I've already made the monumental leap of removing the original WinForms UI code, which is precisely why SnapX compiles at all today. That was a necessary, foundational step to liberate the project from its Windows-only shackles.

However, the reality I'm facing is that while the old UI code is gone, its pervasive influence lingered. The core application logic in what is now SnapX.Core was so tightly interwoven with the UI that its removal has left us with a series of unimplemented features and functionalities. The core application cannot complete or interact with vital parts due to its design assuming direct calls to old UI components.

Consider features like OCR'ing a portion of your screen. This capability has been a major blocker because the underlying core couldn't properly interact with the UI to select that screen region. Similarly, vital parts of the application needed to communicate with UI elements for tasks such as displaying notifications or showing error dialogs.

This refactoring is crucial. The focus is not on complex coding patterns, but on establishing a stable release path. Now, our SnapX.Avalonia UI and any other UI we build simply chat with SnapX's core. So, if the core says, "Hey, let the user select a region," Avalonia figures out the rest, completely separate from the core's own business.

The refactor is expected to be completed in the bi-weekly v0.4.0 pre-release.

[ok-coder1]

Related items:
#260
#262