mirror of https://github.com/AvengeMedia/DankMaterialShell.git synced 2026-08-02 03:28:28 -04:00

Files

T

Ron Harel dc75f1f01d feat(network): initial WiFi hotspot support (#2825 )

* Add hotspot contract layer with capability-gated dispatch.

Establish the interface and manager plumbing for hotspot support so backends can opt in without expanding the core Backend contract.
Only backends that implement HotspotBackend get hotspot state propagated; others are forced to unsupported regardless of what they self-report.

* Add IPC handlers and API docs for hotspot actions.

Wire up configure/ start/ stop hotspot through the request router so the QML service layer can drive hotspot operations.
Bump API version to 27 and document the capability-gating contract clients should follow.

* Implement NetworkManager hotspot backend.

Implement HotspotBackend on NetworkManagerBackend with DMS-owned profile management, AP capability detection, and band validation.
Device resolution is deferred to StartHotspot when no device is specified, so profiles survive hardware changes.

* Isolate client Wi-Fi state from AP-mode connections.

Filter AP-mode profiles and access points out of all client Wi-Fi paths so the DMS hotspot (and user-created APs) never appear as saved networks, visible networks, or connected state.
This protects existing client behavior before hotspot controls are exposed in the UI.

* Prefer idle radios for automatic hotspot device selection.

* Add hotspot properties and methods to QML service layer.

Expose hotspot state and actions through DMSNetworkService, NetworkService, and LegacyNetworkService.
Capability is gated on API version and backend-reported support, not backend name checks, and stays stable when Wi-Fi radio is disabled.

* Add hotspot controls to Settings and Control Center.

Settings shows a hotspot setup card as a sibling in the Wi-Fi tab with SSID, password, device, band, save, and start/ stop controls.
Control Center shows a compact row that toggles a configured hotspot or routes to Settings for initial setup.
Both stay visible when Wi-Fi is disabled, explaining the requirement instead of hiding.

* Add translator context to hotspot strings.

2026-07-20 09:29:54 -04:00

poexports

i18n: sync

2026-07-17 18:42:17 -04:00

check_term_freeze.py

i18n: term overhaul

2026-07-16 12:15:20 -04:00

check_term_variants.py

i18n: term overhaul

2026-07-16 12:15:20 -04:00

en.json

i18n: sync

2026-07-17 18:42:17 -04:00

extract_settings_index.py

greeter: more repairs for standalone package, scrap LegacyNetworkService

2026-07-19 17:05:38 -04:00

extract_translations.py

Squashed commit of the following:

2026-07-18 10:44:31 -04:00

README.md

switch hto monorepo structure

2025-11-12 17:18:45 -05:00

replace_qstr.py

switch hto monorepo structure

2025-11-12 17:18:45 -05:00

settings_search_index.json

feat(network): initial WiFi hotspot support (#2825 )

2026-07-20 09:29:54 -04:00

template.json

i18n: sync

2026-07-17 18:42:17 -04:00

WORKFLOW.md

switch hto monorepo structure

2025-11-12 17:18:45 -05:00

README.md

DankMaterialShell Translations

This directory contains translation files for DankMaterialShell extracted from all qsTr() calls in the QML codebase.

Files

en.json - Source language file with English strings and file references
template.json - Empty template for creating new translations
extract_translations.py - Script to regenerate translation files

POEditor Format

The JSON files follow POEditor's import format:

[
  {
    "term": "string to translate",
    "context": "file:line",
    "reference": "Modules/Settings/AboutTab.qml:45",
    "comment": ""
  }
]

Field Descriptions

term: The source string in English (from qsTr() calls)
context: Primary location where the string appears (file:line)
reference: All locations where this string is used (comma-separated)
comment: Additional notes for translators (currently empty)

How to Create a New Translation

Copy template.json to your language code (e.g., es.json for Spanish)

Fill in the translation field for each entry:

{
  "term": "Settings",
  "translation": "Configuración",
  "context": "Modals/Settings/SettingsModal.qml:147",
  "reference": "Modals/Settings/SettingsModal.qml:147",
  "comment": ""
}

Import to POEditor or use directly in your translation workflow

Regenerating Translation Files

To update the translation files after code changes:

cd /home/brandon/.config/quickshell/DankMaterialShellGit/translations
./extract_translations.py

This will scan all QML files and regenerate en.json and template.json.

Notes

Strings are deduplicated - if the same string appears in multiple locations, references are merged
File paths are relative to the project root
Line numbers are preserved for accurate context
Empty strings and comments are reserved for translator notes