# HTML Content Display ## Goal Display local HTML content (terms & conditions, privacy policies, help documentation, offline content). ## Actions Required | Action | Purpose | | --------------------- | ------------------------ | | WebViewCreateInstance | Creates WebView instance | | WebViewLoadHtmlString | Loads HTML string | | WebViewShow | Displays WebView | ## Variables Needed * webViewInstance (Object): Stores the WebView instance * htmlContent (String): HTML content to display * baseURL (String): Base URL for relative resources (optional) ## Implementation Steps ### 1. State: PrepareHTML Load HTML content from file or construct programmatically. **Option A: From Resources** ``` Use PlayMaker action to load TextAsset from Resources folder Store in htmlContent variable ``` **Option B: Constructed HTML** ``` Set htmlContent = "

Terms

..." ``` ### 2. State: CreateWebView **Action:** WebViewCreateInstance * **Outputs:** * webViewInstance → Store in FsmObject variable * **Next:** LoadHTML ### 3. State: LoadHTML **Action:** WebViewLoadHtmlString * **Inputs:** * webViewInstance → From variable * htmlString → htmlContent variable * baseURL → Optional (e.g., "file:///android\_asset/" for local resources) * **Next:** ShowWebView **Note:** baseURL is used to resolve relative paths in HTML (images, CSS, etc.) ### 4. State: ShowWebView **Action:** WebViewShow * **Inputs:** * webViewInstance → From variable * **Events:** * successEvent → End * failureEvent → ShowError ## Common Issues * **Images don't load**: Provide correct baseURL for relative image paths * **Styles not applied**: Use inline CSS or embedded `

Terms & Conditions

Last Updated: January 1, 2025

1. Acceptance of Terms

By accessing this app, you agree to be bound by these terms...

``` ### Privacy Policy ```html

Privacy Policy

We respect your privacy...

``` ### Help Documentation ```html

Help & FAQ

Q: How do I create an account?
A: Tap the "Sign Up" button on the main screen...
Q: How do I reset my password?
A: Go to Settings > Account > Reset Password...
``` ## Advanced: Dynamic Content Construct HTML dynamically with player data: ``` State: BuildHTML Set htmlContent = "" Concat htmlContent += "

Player Stats

" Concat htmlContent += "

Name: " + playerName + "

" Concat htmlContent += "

Score: " + playerScore + "

" Concat htmlContent += "" → CreateWebView ``` ## Localization Support Load different HTML based on language: ``` State: DetermineLanguage If Application.systemLanguage == English: → LoadEnglishHTML Else If Application.systemLanguage == Spanish: → LoadSpanishHTML Else: → LoadDefaultHTML LoadEnglishHTML: Load TextAsset: "Terms_EN" Store in htmlContent → CreateWebView ``` ## Images in HTML **Option 1: Base64 Embedded Images** ```html Logo ``` **Option 2: Resources with BaseURL** ```html Logo baseURL = "file:///android_asset/webview_assets/" (Place logo.png in StreamingAssets/webview_assets/) ``` **Option 3: External URLs** ```html Logo ``` ## Styling for Mobile Always include viewport meta tag: ```html ``` Use relative units: ```css body { font-size: 16px; /* Base size */ padding: 5vw; /* Responsive padding */ } h1 { font-size: 1.5em; /* Relative to body */ } ``` ## Interactive HTML Combine with JavaScript (Use Case 2) for interactive content: ```html

Accept Terms?

``` Then use Custom URL Schemes (Use Case 3) to handle button clicks in Unity. ## File Organization Recommended structure: ``` Assets/ Resources/ WebViewContent/ Terms_EN.txt Terms_ES.txt Privacy_EN.txt Privacy_ES.txt Help_EN.txt Help_ES.txt StreamingAssets/ webview_assets/ logo.png icon.png style.css ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://assetstore.essentialkit.voxelbusters.com/features/web-view/playmaker/use-cases/use-case-5-html-content.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.