openmct/platform/commonUI
Charles Hacskaylo 164d959f60 [Frontend] Significant markup/CSS mods for splash screen
#164
Markup in index.html and about-dialog.html
changed to simplify and use :before/:after psuedos;
CSS in _logo-and-bg.scss modded for same;
Added _startup.scss to hold general CSS for
the startup screen;
Renamed startup.scss to startup-open.scss;
Modified SplashScreenManager.js to target renamed
outer container .l-splash-holder;
Added media query for startup screen on phone;
Cleanup: moved classes out of _effects into _global;
Still to-do: apply to WARP and VISTA, including needed
mods to their About dialog screens;
2016-02-23 18:30:21 -08:00
..
about [Frontend] Significant markup/CSS mods for splash screen 2016-02-23 18:30:21 -08:00
browse Merge pull request #642 from nasa/open460 2016-02-08 12:21:01 -08:00
dialog [Tests] Remove suite.json files 2016-02-02 09:35:50 -08:00
edit [Create] Always allow cloning self 2016-02-10 13:49:15 -08:00
formats [Tests] Remove suite.json files 2016-02-02 09:35:50 -08:00
general [Frontend] Significant markup/CSS mods for splash screen 2016-02-23 18:30:21 -08:00
inspect [Tests] Remove suite.json files 2016-02-02 09:35:50 -08:00
mobile [Tests] Remove suite.json files 2016-02-02 09:35:50 -08:00
notification [Tests] Remove suite.json files 2016-02-02 09:35:50 -08:00
themes Merge branch 'master' into open639 2016-02-23 10:46:33 -08:00
README.md [Stylesheets] Add documentation 2015-01-14 17:07:16 -08:00

This directory contains bundles containing common user interface elements of Open MCT Web; that is, the user interface for the application as a whole (as opposed to for specific features) is implemented here.

Extensions

This bundles adds a stylesheets extension category used to inject CSS from bundles. These extensions are declaration-only (no scripted implementation is needed or used); a single property, stylesheetUrl, should be provided, with a path to the relevant CSS file (including extension) relative to the resources directory for that bundle.

Links to these CSS files are appended to the head when the application is started. These are added in standard priority order (see documentation for the framework layer); the order of inclusion of style sheets can change the way they are handled/understood by the browser, so priority can be used to provide control over this order.