jgamboaandClaude
7b15e0982e
Two requests, plus a correctness bug the first one exposed. Drop shadow removed: the frame keeps only 7.css's inset 1px glass highlight. That highlight shares the `box-shadow` declaration with the drop shadow, so it has to be restated rather than the shorthand cleared. With no shadow there is nothing to reserve a gutter for, so the window is full-bleed 100vh again instead of inset by 9/13px. Dark theme retoned after the Ares reference: the glass goes near-black (--w7-w-bg #101013, #060607 on the darker tone) with a white caption, and 7.css's own alpha streaks/highlights become the gloss. Blue stays in the accents — selection, sorted column, active tab — not in the glass. Two literals 7.css hardcodes had to be themed for this: the caption text (black + an 8-fold white halo, which is invisible on black) and the glass streak gradient (its two #fff5 corner shines washed a dark caption silver). The bug: those dark restatements were keyed on [data-theme='dark'], which matches ONLY the forced-dark path. SYSTEM dark sets no attribute — it runs through the prefers-color-scheme media query — so every literal I had restated for the ListView and menu was silently reverting to its light value for anyone on system dark. Rather than duplicate each rule, the restated literals are now tokens (--w7-lv-*, --w7-mn-*, --w7-cap-*, --w7-glass-title) declared in :root.win7 with 7.css's own light values and overridden in BOTH existing dark blocks, which is the pattern this file already uses. The rules themselves are written once and theme through the tokens. Also: the accent -> --w7-w-bg mapping is now light-only, or picking an accent repaints the Ares glass with it. Verified zoomed in both themes: light renders identically to 7.css's reference beside it; dark shows black glass, white caption, subdued streaks. Co-Authored-By: Claude <noreply@anthropic.com>
Ui
This project was generated using Angular CLI version 22.0.6.
Development server
To start a local development server, run:
ng serve
Once the server is running, open your browser and navigate to http://localhost:4200/. The application will automatically reload whenever you modify any of the source files.
Code scaffolding
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-name
For a complete list of available schematics (such as components, directives, or pipes), run:
ng generate --help
Building
To build the project run:
ng build
This will compile your project and store the build artifacts in the dist/ directory. By default, the production build optimizes your application for performance and speed.
Running unit tests
To execute unit tests with the Vitest test runner, use the following command:
ng test
Running end-to-end tests
For end-to-end (e2e) testing, run:
ng e2e
Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Additional Resources
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.