Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avalonia #325

Merged
merged 109 commits into from
Feb 1, 2023
Merged

Avalonia #325

merged 109 commits into from
Feb 1, 2023

Conversation

ForNeVeR
Copy link
Owner

@ForNeVeR ForNeVeR commented Dec 30, 2022

Closes #17.

TODO (extracted from #17 for convenience)

  • solve Extract WPF-dependent code into a separate project #63 in the branch
  • Deal with Merge branch 'master' into 'feature/17-avalonia' #347
  • Fix compilation
  • Fix tests
  • remove the code duplication (at least most of it) — that's why Extract WPF-dependent code into a separate project #63 was necessary
  • update the documentation
  • check issue \colorbox renders root index invisible #128: it should'nt be reproducible for WPF and for Avalonia
  • currently we're planning to only allow for solid colors in the portable code base; we'll have to think about supporting for non-solid colors (aka Brushes) for WPF- and Avalonia-dependent code
    • platform-specific IBrush instances allow that
  • Make sure the resources (.xml and .ttf) are deduplicated properly.
  • after all of that, Avalonia may land into the master branch
  • Check if we still need to override AvaloniaUseExternalMSBuild.
  • add Linux and macOS CI
  • Make sure the CI still works
  • Make sure to add the Avalonia assemblies into the API tests
  • WpfMath.Shared: make sure the framework list is correct (add netstandard)
  • Separate NuGet package for Avalonia
  • Separate NuGet package for WpfMath.Shared
  • Figure out and document the API changes
  • Share the versioning and copyright details
  • Update the maintainership documentation
  • nuget.yml: make sure it uses the same runner image as the main.yml
  • Merge with master, make sure the CI is still okay

Before merge

  • Review
  • TODO monitoring
  • Update GitHub Actions branch protection rules to use the new names

After merge

  • Create an issue about test suite refactoring: split tests into WPF-specific + Avalonia-specific + Shared
  • Create an issue about sharing the .ttf files somehow
  • Update the GitHub Action secrets
  • Create an issue on documenting the supported rendering targets
  • Create an issue on better control API documentation (e.g. the ErrorTemplate doesn't seem to be explained well)

ahopper and others added 30 commits December 5, 2018 14:05
- Custom fonts are not working (math symbols are not working)
- Positions of the formula symbols are incorrect
- Project Properties removed as interrupting build

The added code was moved to another directory so it won't break the
original WPF code. ~ F. v. Never
# Conflicts:
#	appveyor.yml
#	src/WpfMath/WpfMath.csproj
# Conflicts:
#	README.md
#	WpfMath.sln
#	appveyor.yml
#	scripts/nuget-pack.ps1
#	src/SharedMath/Atoms/BigDelimeterAtom.cs
#	src/SharedMath/DefaultTexFont.cs
#	src/SharedMath/TexFontUtilities.cs
#	src/SharedMath/XmlUtilities.cs
#	src/WpfMath/TexFontInfo.cs
@ForNeVeR ForNeVeR marked this pull request as ready for review January 31, 2023 23:42
Otherwise, tests may be unstable.
@ForNeVeR ForNeVeR mentioned this pull request Feb 1, 2023
1 task
@ForNeVeR ForNeVeR merged commit 42b0754 into master Feb 1, 2023
@ForNeVeR ForNeVeR deleted the feature/17-avalonia branch February 3, 2023 23:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avalonia support
3 participants