feat: Initial spatial control and aggressive feature stripping #1881
+166
−59
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Project Goal: Transform Wolvic into a spatial multi-viewer for video content,
optimized for minimal resource consumption and device heat.
Current Task: Establish core spatial control over a single existing browser
tab/window and aggressively strip browser features.
Changes Implemented:
1. Spatial Control Foundation (C++):
* Added `debugWidgetHandle` and `debugWidgetTransform` to
`BrowserWorld` to allow overriding a specific widget's transform.
* Hardcoded `debugWidgetHandle` to `0` for initial testing.
* Modified `BrowserWorld::LayoutWidget` to apply this debug
transform, bypassing normal layout calculations for the targeted widget.
* Implemented a programmatic X-axis oscillation animation for the
debug widget's transform, primarily in `BrowserWorld::TickImmersive`.
2. Aggressive Feature Stripping - Phase 1 (UI & High-Level Java Logic):
* In `VRBrowserActivity.java`:
* Disabled instantiation and usage of major UI components:
`NavigationBarWidget`, `TrayWidget`, and `TabsBar`.
* Updated `addWidgets` to only include essential widgets:
`RootWidget`, `KeyboardWidget` (retained for potential future basic
URL input), and `WebXRInterstitialWidget` (for core WebXR).
* Added null checks for remaining Java-level code paths that might
reference the stripped UI components.
* Ensured new windows/sessions default to a blank page (see item 4).
3. Aggressive Feature Stripping - Phase 2 (Backend Services & AndroidManifest):
* In `app/src/main/AndroidManifest.xml`:
* Commented out `CrashReporterService` and `FileProvider`.
* Removed permissions: `ACCESS_COARSE_LOCATION`,
`ACCESS_FINE_LOCATION`, `REQUEST_INSTALL_PACKAGES`, and the
app-specific crash receiver permission.
* In `VRBrowserApplication.java`:
* Commented out the initialization of backend services/managers:
`Places` (bookmarks/history), `Services` (dependent on Places),
`LoginStorage`, `Accounts`, `DownloadsManager`, and `Addons`.
4. Refined Initial Window Setup:
* Analyzed `Windows.java`, `Session.java`, and `SessionStore.java` to
understand initial window and URL loading mechanisms.
* Modified `Session.getHomeUri()` in `Session.java` to ensure that
newly created non-private sessions default to loading `"about:blank"`,
providing a clean and minimal initial page. This works in conjunction
with `WindowWidget.loadHome()` which also points to this.
The application is expected to launch with a significantly reduced UI,
displaying a single animated window with `about:blank`.
The next steps involve building, testing these changes on a device, and
addressing any runtime issues or crashes that may arise from the
stripping process.
|
Hi @westbrookbr, thanks for your contributions. I wonder what's your plan for this change. We are definitely not going to upstream those changes that remove most of the UI from Wolvic, so I wonder what you had in mind. If you need just a browser window have you evaluated the option of using Wolvic in kiosk mode? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Project Goal: Transform Wolvic into a spatial multi-viewer for video content, optimized for minimal resource consumption and device heat.
Current Task: Establish core spatial control over a single existing browser tab/window and aggressively strip browser features.
Changes Implemented:
Spatial Control Foundation (C++):
debugWidgetHandleanddebugWidgetTransformtoBrowserWorldto allow overriding a specific widget's transform.debugWidgetHandleto0for initial testing.BrowserWorld::LayoutWidgetto apply this debugtransform, bypassing normal layout calculations for the targeted widget.
debug widget's transform, primarily in
BrowserWorld::TickImmersive.Aggressive Feature Stripping - Phase 1 (UI & High-Level Java Logic):
VRBrowserActivity.java:NavigationBarWidget,TrayWidget, andTabsBar.addWidgetsto only include essential widgets:RootWidget,KeyboardWidget(retained for potential future basicURL input), and
WebXRInterstitialWidget(for core WebXR).reference the stripped UI components.
Aggressive Feature Stripping - Phase 2 (Backend Services & AndroidManifest):
app/src/main/AndroidManifest.xml:CrashReporterServiceandFileProvider.ACCESS_COARSE_LOCATION,ACCESS_FINE_LOCATION,REQUEST_INSTALL_PACKAGES, and theapp-specific crash receiver permission.
VRBrowserApplication.java:Places(bookmarks/history),Services(dependent on Places),LoginStorage,Accounts,DownloadsManager, andAddons.Refined Initial Window Setup:
Windows.java,Session.java, andSessionStore.javatounderstand initial window and URL loading mechanisms.
Session.getHomeUri()inSession.javato ensure thatnewly created non-private sessions default to loading
"about:blank",providing a clean and minimal initial page. This works in conjunction
with
WindowWidget.loadHome()which also points to this.The application is expected to launch with a significantly reduced UI, displaying a single animated window with
about:blank. The next steps involve building, testing these changes on a device, and addressing any runtime issues or crashes that may arise from the stripping process.