-
Notifications
You must be signed in to change notification settings - Fork 6
[Feature Request]: Pojav Launcher support #41
Comments
Just to clarify, we don't need to run this on the Android device running Pojav, this just simplifies the process of getting all the files ready correct? If we're running on Android, that might be a bit harder because I don't know if Qt for Python runs on Android, meaning we're stuck to the CLI (which ofc isn't ideal). |
|
Shouldn't we create a separate Kotlin/Java Project for Pojav? |
Well, I thought you could compile it with something like Jython. But if not, scrap this idea, as it's not worth creating a new project for, then it'd just wait for packwiz's implementation. |
We could also compile to an APK, allowing us to use the existing VI code base. Not sure if that's idea though. |
Sorry, but I don't think its not a good idea to simply compile it to an APK. It's not as easy as that. Python is just not made for mobile app developement. The closest thing to that would be that we could program an This repo's name is VanillaInstaller, so it wouldn't make sense to add any unrelated functionality. We should keep it lightweight. |
You can compile PySide6 to C++ which can then be compiled to an android APK, allowing this functionality. So I wouldn't rule it out in the future, but not for now. |
We could also make this somewhat of a monorepo if we wanted, although I'm not sure. TL;DR: Maybe at some point, but not high priority right now. |
This is probably way too cumbersome... |
|
Code of Conduct
Potential Enhancement
A checkbox users can enable to indicate they want to install to Pojav launcher
How it could be implemented
The user would download the installer as jar and check the checkbox. The installer would install to assigned path as before, but also unpack a set of patches to specified folders.
Anything else?
Low priority, get the main thing running first
The text was updated successfully, but these errors were encountered: