You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To keep the core repo clean and slim, have you thought about moving those different integrations (Android, .Net) into separate repos? Or do you feel there will be too much dependencies and boilerplate that can slow you down too much?
I have thought of this but it does not make a lot sense. Here my thoughts on that
The platform specific integrations are typically quite slim from the amount of code they add to the repo. My goal is rather to port the C#/Kotlin specific parts over to TypeScript too, and then rely fully on transpiling.
The main part of the library still is living here and is based on transpiling. Usually there is the base/core library and then the platform specific controls on top. I could pull the main repo as submodule and run transpiling there but this would then just be a shift of the CI/CD to a different repo, there is not any real gain on this but rather effort to get it running clean.
The only thing I want to maybe move out, and also extend are the samples. They are not needed for development of alphaTab itself and rather hidden/confusing for integrators the way they are today.
In short: A split into a polyrepo will just generate effort, and make the whole development chain more complicated.
Once we have the base code translated to Kotlin the next level is build proper native android controls for integration into apps.
The text was updated successfully, but these errors were encountered: