ikarago / scanning Goto Github PK

Currently the SettingsPage is a seperate page. This needs to be moved to a Dialog like the other Ikarago-apps.

The InkPage is not capable of open in PDF and XPS documents. When a document has been scanned in such an unsupported format for the Editor, show an alternative page and display a button to open them in an alternative app.

Add an AboutDialog like the other Ikarago-apps to display the apps version and extra info.

Seperate the logic and XAML for the Detailed view to a seperate XAML-page, code behind and ViewModel so it can operate independently from the MainPage. (handy for allowing it to edit in a seperate Window and such.

The app isn't handeling removals of the currently selected scanner well. Write exception cases for this and maybe auto-select another scanner while providing feedback about this to the user

Automatically set the default settings for the found scanner(s) so the user can rapidly start scanning

Check the supported settings of the selected scanner and allow the user to change this in the supported range of the Scanner.

Let the app ask for a app closer confirmation when a document has been scanned but not been saved.

Build the base UI align the Windows Scan-app by Microsoft and this early mockup:

Build the basic scanning logic for the code behind so the user can actually scan their documents and save the base image.

A lot of the options have to be checked manually. This should be seperated into a seperate Helper or Service method to keep the main code clean.

Document this as well, as the current Scanner API is a mess and see if the documentation on Microsoft Docs (https://docs.microsoft.com/en-us/windows/uwp/devices-sensors/scan-from-your-app) can be improved so others can make better use of it.

Open the just scanned image in an Windows Ink element and allow the user to save the image.

Allow the user to toggle between Dark and Light modes for the background in the scan editor so they can see the outlines of the document

Migrate the logic of the MainPage.cs as much as possible to the MainViewModel to decouple UI and Logic to allow for huge reworks of the UI without risk of breaking functionality.