openmct/platform/commonUI
Charles Hacskaylo a65ca7cb1e [Frontend] Refactor Inspector to use s-status-editing
open #468
Removed ng-show="editMode" in object-inspector.html;
Refactored CSS as required in _inspector.scss;
Added opacity transition to splitter-inspect-panel and
split-pane-component pane bottom, but not working as desired currently:
entire inspector seems to be destroyed and recreated when switching into
and out of edit mode;
Moved <style> def for .location-item in object-inspector.html into .scss;
2016-01-08 16:47:11 -08:00
..
about [Code Style] Use prototypes in About bundle 2015-08-10 10:19:02 -07:00
browse [Frontend] Refactor to use s-status-editing instead of ng-class 2016-01-08 16:11:00 -08:00
dialog Made changes to error reporting 2015-11-04 22:07:26 -08:00
edit Disabled context menu for Location items in edit mode, and disabled context menu items for non-creatable objects 2015-12-10 17:39:56 -08:00
formats [Time Conductor] Update FormatService JSDoc 2015-11-02 12:30:18 -08:00
general [Frontend] Refactor Inspector to use s-status-editing 2016-01-08 16:47:11 -08:00
inspect [Frontend] Safety merge of master; minor fixes 2015-10-30 17:09:04 -07:00
mobile [Common UI] Test agentService.isBrowser 2015-12-04 14:12:00 -08:00
notification Fixed jslint issues 2015-11-04 20:48:22 -08:00
themes [Frontend] Refactor Inspector to use s-status-editing 2016-01-08 16:47:11 -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.