Hosted Program Page Routing with Custom Rendering Paths
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current page routing in hosted programs, such as mini programs, lacks customization and optimization, leading to a single page presentation effect and an unnatural user experience during page switching.
Innovation Solution
Implement custom routing by acquiring page navigation parameters, determining rendering engine identifiers, and establishing a page tree to render pages based on these parameters, allowing developers to set custom routing information and improve personalization and flexibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If default routing manner is used (page pushed from right end to left end), then implementation is simple, but page presentation effect is single and customization is difficult
Solution Approach 1:
The routing system is segmented into multiple rendering engines (first rendering engine and second rendering engine) that can be selectively used. The page tree structure segments the navigation path into multiple pages, allowing different rendering engines to handle different pages based on customization requirements. This segmentation enables flexible routing configurations without requiring complete system redesign.
Solution Approach 2:
The routing system transitions from a static default routing manner to a dynamic configurable system. The page navigation parameters include routing parameters that can be dynamically adjusted to specify different routing manners (e.g., slide from right, slide from left, pop-up). The system can adapt the routing behavior based on the specific page requirements and user needs, making the routing mechanism flexible and versatile.
2Ease of operation
If default routing manner is used, then implementation is straightforward, but user experience during page switching is unnatural and smoothness is insufficient
Solution Approach 1:
The routing parameters in the page navigation parameters can be changed to control different routing manners. By adjusting parameters such as routing direction, animation type, and transition effects, the system can achieve natural and smooth page switching experiences. Different routing parameters can be configured for different pages or navigation scenarios to optimize user experience.
Solution Approach 2:
The page tree structure acts as an intermediary between the navigation request and the rendering process. It mediates the routing by establishing a hierarchical navigation path and coordinating between different rendering engines. The page tree enables smooth transitions by managing the state and position of pages during navigation, facilitating natural user interaction.
3Adaptability or versatility
If custom routing information is implemented, then developer customization and optimization capabilities are improved, but system complexity increases
Solution Approach 1:
The rendering engine framework is designed with multi-functionality to handle both default routing and custom routing scenarios. The same rendering engine infrastructure can support various routing manners by processing different routing parameters, eliminating the need for separate specialized systems. This universality reduces overall system complexity while maintaining high flexibility.
Solution Approach 2:
The page tree is established in advance based on the page identifier and navigation parameters before actual rendering occurs. This preliminary structure preparation simplifies the rendering process by pre-organizing the navigation path and page relationships. The routing parameters are processed and configured beforehand, allowing the rendering engine to execute custom routing operations more efficiently without increasing runtime complexity.
Data Source
AI summary
Some aspects of the disclosure provide a page processing method. In some examples, an electronic device executes a host program that provides a host environment for a hosted program. Page navigation parameters of the hosted program are acquired, the page navigation parameters include address information of a first target page in the hosted program and custom routing information of the first target page. A rendering engine identifier for a rendering engine and a page identifier of the first target page are determined. A page tree is established in the hosted program according to the page identifier. The rendering engine is called to render the first target page based on the page tree and the page navigation parameters. Apparatus and non-transitory computer-readable storage medium counterpart embodiments are also contemplated.