This media is not supported in your browser
VIEW IN TELEGRAM
i really wanna know if it can handle 60fps
🔥5
wx_pty_x.zip
3.7 KB
🚀 WebUI X v131 is Here — A Massive Leap Forward!
You might be wondering why the v131 update is so much larger than before. That’s because we’ve completely opened up the system to support a powerful, stable plugin architecture. Now, developers can seamlessly integrate their own custom interfaces — whether written in Kotlin, Java, Rust, or C/C++.
🔧 Introducing PTY X
This release also marks the launch of PTY X, a full pseudoterminal integration for WebUI X — enabling advanced terminal-based interactions right within the WebUI X environment.
📦 Download PTY X APK:
👉 https://github.com/MMRLApp/PTY-X/releases/tag/v10
💻 Get the Latest WebUI X: Portable (v131):
👉 https://github.com/MMRLApp/WebUI-X-Portable/releases/tag/v131
You might be wondering why the v131 update is so much larger than before. That’s because we’ve completely opened up the system to support a powerful, stable plugin architecture. Now, developers can seamlessly integrate their own custom interfaces — whether written in Kotlin, Java, Rust, or C/C++.
🔧 Introducing PTY X
This release also marks the launch of PTY X, a full pseudoterminal integration for WebUI X — enabling advanced terminal-based interactions right within the WebUI X environment.
📦 Download PTY X APK:
👉 https://github.com/MMRLApp/PTY-X/releases/tag/v10
💻 Get the Latest WebUI X: Portable (v131):
👉 https://github.com/MMRLApp/WebUI-X-Portable/releases/tag/v131
🔥5❤1
Please open Telegram to view this post
VIEW IN TELEGRAM
🤣13😁9😭5👎1😐1
Do you think the FileSystem API could use a rework?
I'm considering doing it through the new plugin system 🤔. It allows for a quick fix for module developers—just update wxu.dex instead of requiring users to update the entire WebUI X.
I'm considering doing it through the new plugin system 🤔. It allows for a quick fix for module developers—just update wxu.dex instead of requiring users to update the entire WebUI X.
Anonymous Poll
75%
Yes — do it via the plugin system (wxu.dex update is perfect!)
18%
Needs more discussion — maybe, but let's refine the plan first
7%
No — the current system works fine as-is
MMRL App
Do you think the FileSystem API could use a rework?
I'm considering doing it through the new plugin system 🤔. It allows for a quick fix for module developers—just update wxu.dex instead of requiring users to update the entire WebUI X.
I'm considering doing it through the new plugin system 🤔. It allows for a quick fix for module developers—just update wxu.dex instead of requiring users to update the entire WebUI X.
A small note: The current FileSystem Implementation won't be removed.
Please open Telegram to view this post
VIEW IN TELEGRAM
Proof of concept for JavaScript-to-Java/Kotlin reflection using the WXU Plugin for WebUI X
https://gist.github.com/DerGoogler/a67a57f4cbd7cc3a8fa2dea99c9d6736
You also can even build entire ProcessBuilders!
WebUI X is not for beginners and it's the most advanced WebUI that ever exist!
https://gist.github.com/DerGoogler/a67a57f4cbd7cc3a8fa2dea99c9d6736
You also can even build entire ProcessBuilders!
WebUI X is not for beginners and it's the most advanced WebUI that ever exist!
🤣6🔥2
Forwarded from MMRL/WXP CI
WebUI-X-v194-release.apk
21.2 MB
WebUI X: Portable
#ci_194
What's new?
- Add input validation for cachingMaxAge field
- Refactor config file reading logic
- Translated using Weblate (Polish)
- Disable exit confirm switch when JS back interceptor is used
- Replace finish() with handleNativeBack() on back press
- Add SuFile text read/write extensions and JSONCollection types
- Add WebUI config options for CSP and caching
- Refactor FeaturedManager to use WorkingMode and add SukiSU
- Switch module storage to internal app filesDir
- Add composable error screens for WebView errors
- Refactor WebView initialization and add debug helpers
- Refactor noscript injection and cleanup unused variables
- Prevent handling of data: URLs in WXClient
- Refactor WebUI clients and split Chrome/RenderProcess logic
- Refactor JavaScript interface removal in WebUIView
- Translated using Weblate (Polish)
- Translated using Weblate (Turkish)
- Translated using Weblate (Turkish)
See all changes here
Workflow run
#ci_194
What's new?
- Add input validation for cachingMaxAge field
- Refactor config file reading logic
- Translated using Weblate (Polish)
- Disable exit confirm switch when JS back interceptor is used
- Replace finish() with handleNativeBack() on back press
- Add SuFile text read/write extensions and JSONCollection types
- Add WebUI config options for CSP and caching
- Refactor FeaturedManager to use WorkingMode and add SukiSU
- Switch module storage to internal app filesDir
- Add composable error screens for WebView errors
- Refactor WebView initialization and add debug helpers
- Refactor noscript injection and cleanup unused variables
- Prevent handling of data: URLs in WXClient
- Refactor WebUI clients and split Chrome/RenderProcess logic
- Refactor JavaScript interface removal in WebUIView
- Translated using Weblate (Polish)
- Translated using Weblate (Turkish)
- Translated using Weblate (Turkish)
See all changes here
Workflow run
👍5
Forwarded from Googlers Repo
A personal statement from Der_Googler.
Please translate it yourself into your language.
Please translate it yourself into your language.
Anscheinend mögen manche Leute meine App-Entwicklung oder generell meine Projekte entweder sehr – oder überhaupt nicht.
Die Android-Community war leider schon immer toxisch, und es sieht nicht so aus, als würde sich das jemals ändern. Es ist einfach nur frustrierend.
Ständig beschwert sich jemand darüber, dass dieses oder jenes nicht funktioniert – dabei wird kaum Rücksicht auf den Entwickler selbst genommen. Viele vergessen, dass wir nicht rund um die Uhr Zeit haben. Manche von uns haben einen Vollzeitjob und investieren zusätzlich ihre Freizeit, um überhaupt etwas zu entwickeln. Das wird oft nicht wertgeschätzt – stattdessen wird verlangt, dass man sofort alles umsetzt oder Probleme löst.
Ich arbeite 40 Stunden pro Woche und habe schlichtweg weder die Energie noch die Zeit, mich zusätzlich um alles zu kümmern. Ja, ich habe mir das ausgesucht – aber man sollte sich trotzdem mal vor Augen führen, wie viel Arbeit in solchen Projekten steckt.
Wenn man sein eigenes Werk verteidigt, wird man dann auch noch beleidigt – teils anonym, teils direkt. Ich werde keine Namen nennen, weil es mir nicht um Einzelpersonen geht, sondern um ein generelles Verhalten. Ich selbst habe noch nie jemanden beleidigt oder personenbezogene Daten veröffentlicht – und das wird auch so bleiben. Ich bin strikt dagegen.
Ich werde sachlich bleiben – aber ich werde künftig deutlich weniger tolerieren.
Demnächst werde ich auch Entscheidungen darüber treffen, wie es mit meinen persönlichen Projekten, Googlers Repos und der MMRLApp weitergeht.
👍5