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
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
Would it be possible for us to package all the stuff that got stripped out for Turbo into an AAR which could then get dynamically loaded from the SDcard like my Vuforia mod?
The text was updated successfully, but these errors were encountered:
So, one objection I came up with for this is that it prevents OBJ and Blocks modification. What if we included that code in the project still somehow? And just had a different gradle task to build it.
OnBotJavaManager actually copies the contents of Robotcore\assets\java to FIRST\java\lib already. Which would make it VERY easy to not include that stuff in the APK.
Javac.jar is already isolated, so it shouldn't be too hard to load that at runtime too. I think the biggest savings after that would be to put the org.firstinpires.ftc.robotcore.internal.android package into its own jar/dex. At that point, we can see how far we are size and method wise from Turbo. Of course, even if we decide that it's slim enough, we still should measure the impact of an option to disable the HTTP server and stuff.
Would it be possible for us to package all the stuff that got stripped out for Turbo into an AAR which could then get dynamically loaded from the SDcard like my Vuforia mod?
The text was updated successfully, but these errors were encountered: