How abatbeliever/internetstroller_project4_memoria_webbrowser works
Project Type & Purpose
• This is not a traditional full-stack web application but rather a lightweight, HSP-based web browser that leverages WebView2. The README makes it clear that ISMemoria is an HSP (Hot Soup Processor) project that creates a minimalistic browser with features such as RSS support, script integration, PDF output, and various UI functions.
• Its intended usage is “to take your USB stick for an internet stroll” – meaning it is portable, self-contained (all settings and history stored locally), and optimized for performance and light resource usage.
Analyzing the File Structure
• Top-Level Files:
• Files like InternetStroller.hsp, Build.ini, and TMPDeleter.bat indicate the application’s main entry point, build configuration, and cleanup routines.
• .pak files (e.g., hsc.pak, html.pak, iE.pak, etc.) likely bundle resources or modules required by the software.
• Source Directory (src):
• Two main subdirectories: “Dynamic” and “Static.”
• The “Dynamic” directory houses components that drive runtime behavior – modules such as Graphic.hsp, LoadWebView.hsp, MultiDialog.hsp, and others that suggest dynamic UI functions, event handling (SetEvent.hsp), and system dialogs.
• The “Static” directory is further broken down into:
▪ EVENT: Files like CMD.hsp, TAB.hsp, WM.hsp, and WebView.hsp denote predefined event handlers or messaging constructs.
▪ Extend: Files here (e.g., Execute6.hsp, IScript.hsp, ManaPAD.hsp, RSSer.hsp, URLPush.hsp) provide extension points to add functionality like script execution or RSS handling.
• Additionally, files like HSC.hsp and StatusBar32.hsp are also likely core components managing specific parts of the UI or configuration.
Key Components & Relationships
• Core Application Engine:
• InternetStroller.hsp serves as the main executable entry point.
• Build.ini orchestrates the build and configuration settings.
• Dynamic Modules (src/Dynamic):
• Responsible for runtime tasks such as graphics, dynamic event binding, loading the WebView, and managing dialogs (e.g., modTaskDialog, MultiDialog).
• Static Modules (src/Static):
• EVENT Subsystem: Manages static event handling which coordinates user actions with system responses (e.g., CMD, TAB, WM events).
• Extend Subsystem: Encapsulates extension functionalities such as executing scripts, managing a custom text editor component (ManaPAD), controlling RSS feeds, and URL push events.
• External Dependencies:
• The project leverages WebView2 (via WebView2Loader.dll) for rendering web content, ensuring modern browsing capabilities.
• Other external libraries such as hspinet.dll facilitate networking capabilities.
Architectural Patterns & Design Principles
• Separation of Concerns:
• Modular Design:
• The use of “Dynamic” and “Static” subdirectories indicates that functionalities are compartmentalized into self-contained modules. This makes it easier to extend or modify individual aspects of the browser.
• Portability:
• That all settings and history are stored locally—the design supports a portable solution without complex dependency on an external configuration or database system.