How nhmsv/supporter works
Mobily Supporter is a PHP web app for finding and composing customer-support replies, with language-specific reply boundaries, signatures, favorites, and reply-use history. A user enters the main page or invokes an AJAX action; the app initializes shared services, presents replies, and supports search, insertion, copying, and preference changes. The graph emphasizes those domain stages and the shared initialization layer. Some page and action code is unsampled, so only documented or excerpt-visible relationships are connected.
Main entry points: init.php Application initialization · index.php Reply workspace · db Application database · class_preferences.php User preferences
Components 20
Web entry and views
- Reply workspace
index.php - Navigation and search
views/header.php - Workspace scripts
views/footer.php
Reply workflows
- Reply AJAX actions
views/actions/ajax.php - Reply search
views/actions/replies.php - History search
views/actions/replies-history.php - Start boundary
views/actions/ajax-replies-start.php - End boundary
views/actions/ajax-replies-end.php
Shared application services
- Application initialization
init.php - Shared reply helpers
lib/functions.php - Reply operations
lib/class_replies.php - Core settings and stats
lib/class_core.php - User management
lib/class_user.php
Persistence and preferences
- Database client
lib/class_db.php - Application database
db - User preferences
lib/class_preferences.php - Language resources
lib/class_language.php - Service registry
lib/class_registry.php - Request filtering
lib/class_filter.php
Other components
- Support agent
Connections 28
- Support agent → Reply workspace: opens
index.php - Reply workspace → Application initialization: requires
index.php - Reply workspace → Navigation and search: renders
index.php - Reply workspace → Workspace scripts: renders
index.php - Reply workspace → Reply operations: constructs
index.php - Application initialization → Database client: loads and connects
init.php - Application initialization → Service registry: registers services
init.php - Application initialization → Shared reply helpers: loads
init.php - Application initialization → Request filtering: loads and creates
init.php - Application initialization → Core settings and stats: creates
init.php - Application initialization → Reply operations: creates
init.php - Application initialization → User management: creates
init.php - Application initialization → User preferences: creates
init.php - Application initialization → Language resources: creates
init.php - Database client → Application database: connects
- Reply search → Application initialization: requires
views/actions/replies.php - Reply search → Application database: queries replies
views/actions/replies.php - History search → Application initialization: requires
views/actions/replies-history.php - History search → Application database: queries history
views/actions/replies-history.php - Reply AJAX actions → Application initialization: requires
views/actions/ajax.php - Reply AJAX actions → Reply operations: updates counter
views/actions/ajax.php - Reply AJAX actions → User preferences: changes language
views/actions/ajax.php - Start boundary → Application initialization: requires
views/actions/ajax-replies-start.php - Start boundary → User preferences: updates boundary
views/actions/ajax-replies-start.php - End boundary → Application initialization: requires
views/actions/ajax-replies-end.php - End boundary → User preferences: updates boundary
views/actions/ajax-replies-end.php - Reply workspace → Application database: reads favorites
index.php - Workspace scripts → Application database: reads autocomplete terms
views/footer.php