57a68a24de
* Hardcoded prototype - conditional styles for display layout or generator domain objects only. Needs Architectural review * Updates to ConditionalStylesView * Adds background colors list * Show conditional styles for subObjectViews and telemetryViews * Uses telemetry provider to determine which style is active Removes hardcoded conditionSet work used for prototype * Fixes failing test * Add default styles to conditionalStyles when a condition set is added to the domain object. * Use EventEmitter alias instead of eventEmitter3 in imports Change variable name for better readability and clarity Remove unused code * Change StyleRuleManager to accept conditionStyle objects instead of domainObjects * Uses a map for conditional styles instead of a list in order to improve performance * Use in-built api to check for identifier equality Pass missing arguments * Removes unnecessary object get call. * Conditionals styling WIP - Tweaks for layout/overflow issues; - Better header alignment; - Much better approach to "accordion" spacing; * Adds conditional styles for drawing objects * Fixes small bugs while adding or removing nested conditional styling * Removes hard coded conditionSetIdentifier * Fixes small conditionManager bug * WIP - Adds condition set selection dialog * WIP - Add condition set * Styling for tree dialog in selector - New `.c-selector` class; - Markup added to tree-item.vue to fix missing `c-object-label` wrapper; * Adds image url to styles inspector view * Adds highlight for selected conditionSet in selection dialog. * Conditionals Inspector styling WIP - Simplified Inspector markup; - Refined `.c-inspector` layout strategy; - Refined `.l-multipane` classes for better layout and scroll handling; - TODOs: styling for 'styles' section; unit test, find regressions, fix; * Read-only mode changes for the styles inspector * Adds basic styling for styles inspector view * Removes unused code * Displays condition set name * Display description for conditions * Conditionals Inspector styling WIP - Add new ObjectName component to Inspector; - Add supporting styles; * Conditionals Inspector styling WIP - Refactor for better usage of c-object-label; - Refactor `c-properties` classes to `c-inspect-properties`; * Conditionals Inspector styling WIP - Introduce `c-inspect-styles` class; - Markup refined in ConditionalStylesView.vue; * Conditionals Inspector styling WIP - Fix unintended regression in `c-object-label`; * Makes inspector view tabs sticky. Shows errors if either telemetry or conditions are missing Refresh conditionStyles when styles inspector is loaded to show new conditions that might be added to the conditionSet * Conditionals styling WIP - Added title to Condition Set selector dialog; * Conditionals styling WIP - CSS and markup changes; * Conditionals styling WIP - Markup changes; * Componentize conditional style editor, condition description and condition error * Conditionals styling WIP - Conditional styling elements in Inspector, significant refinements; - Condition description formatting; - Significant markup simplification in StyleEditor.vue; - Moved `.c-inspect-styles` into conditional-styles.scss; * Conditionals styling WIP - Added menu positioning css; * Conditionals styling WIP - Display images in StyleEditor `c-style-thumb` element; * Use the condition description component to show the condition description in condition set views * Conditionals styling WIP - New `u-alert` and `u-error` classes and mixin; - New $colorError theme constants; * Conditionals styling WIP - Fixed background: cover or c-style-thumbs; * Conditionals styling WIP - Add navigate-or-preview functionality to attached Condition Set used for conditional styling (thank you Deep!); - Better theme-compliant box-shadowing on c-style-thumb; - Added default color property to cClickIcon SCSS mixin; * Fixes ConditionDescription and ConditionErrors views * Allow static styles for domain Objects and display layout items * Consolidate handling of 'none' style to the object styles mixin * Adds visibility option to child items * Conditionals styling WIP - Add `is-style-invisible` class; - Better color approach for table headers to support domain object styling; * Change visibility to isInvisible class * Fixes visibility for object views and telemetry views * Fixes selection of condition set from tree view * Conditionals styling WIP - Added new $glyph-icon-eye-disabled font symbol and related class; - Modded glyphs used for visibility toggle button; - Modded StyleEditor thumb preview to reflect visibility setting; - Tweaked `is-style-invisible` opacity property; - Code cleanup; * Conditionals styling WIP - Display disabled toolbar for Inspector styles in Browse mode; - Better approach to 'is-style-invisible' `c-style-thumb` with new bgCheckerboard mixin; - Moved `$controlDisabledOpacity` into a theme constant; - Refined spacing in Inspector grid; * Fixes linting issues * Fixes telemetry metadata name * criterion descriptions is now an array of strings * Fixes spacing * Removes commented out code. * Remove v-if Co-authored-by: charlesh88 <charlesh88@gmail.com>
Open MCT 
Open MCT (Open Mission Control Technologies) is a next-generation mission control framework for visualization of data on desktop and mobile devices. It is developed at NASA's Ames Research Center, and is being used by NASA for data analysis of spacecraft missions, as well as planning and operation of experimental rover systems. As a generalizable and open source framework, Open MCT could be used as the basis for building applications for planning, operation, and analysis of any systems producing telemetry data.
Please visit our Official Site and Getting Started Guide
See Open MCT in Action
Try Open MCT now with our live demo.
Building and Running Open MCT Locally
Building and running Open MCT in your local dev environment is very easy. Be sure you have Git and Node.js installed, then follow the directions below. Need additional information? Check out the Getting Started page on our website. (These instructions assume you are installing as a non-root user; developers have reported issues running these steps with root privileges.)
- Clone the source code
git clone https://github.com/nasa/openmct.git
- Install development dependencies
npm install
- Run a local development server
npm start
Open MCT is now running, and can be accessed by pointing a web browser at http://localhost:8080/
Open MCT v1.0.0
This represents a major overhaul of Open MCT with significant changes under the hood. We aim to maintain backward compatibility but if you do find compatibility issues, please let us know by filing an issue in this repository. If you are having major issues with v1.0.0 please check-out the v0.14.0 tag until we can resolve them for you.
If you are migrating an application built with Open MCT as a dependency to v1.0.0 from an earlier version, please refer to our migration guide.
Documentation
Documentation is available on the Open MCT website.
Examples
The clearest examples for developing Open MCT plugins are in the tutorials provided in our documentation.
We want Open MCT to be as easy to use, install, run, and develop for as possible, and your feedback will help us get there! Feedback can be provided via GitHub issues, or by emailing us at arc-dl-openmct@mail.nasa.gov.
Building Applications With Open MCT
Open MCT is built using npm and webpack.
See our documentation for a guide on building Applications with Open MCT.
Plugins
Open MCT can be extended via plugins that make calls to the Open MCT API. A plugin is a group of software components (including source code and resources such as images and HTML templates) that is intended to be added or removed as a single unit.
As well as providing an extension mechanism, most of the core Open MCT codebase is also written as plugins.
For information on writing plugins, please see our API documentation.
Tests
Tests are written for Jasmine 3 and run by Karma. To run:
npm test
The test suite is configured to load any scripts ending with Spec.js found
in the src hierarchy. Full configuration details are found in
karma.conf.js. By convention, unit test scripts should be located
alongside the units that they test; for example, src/foo/Bar.js would be
tested by src/foo/BarSpec.js. (For legacy reasons, some existing tests may
be located in separate test folders near the units they test, but the
naming convention is otherwise the same.)
Test Reporting
When npm test is run, test results will be written as HTML to
dist/reports/tests/. Code coverage information is written to dist/reports/coverage.
Glossary
Certain terms are used throughout Open MCT with consistent meanings or conventions. Any deviations from the below are issues and should be addressed (either by updating this glossary or changing code to reflect correct usage.) Other developer documentation, particularly in-line documentation, may presume an understanding of these terms.
- plugin: A plugin is a removable, reusable grouping of software elements. The application is composed of plugins.
- composition: In the context of a domain object, this refers to the set of other domain objects that compose or are contained by that object. A domain object's composition is the set of domain objects that should appear immediately beneath it in a tree hierarchy. A domain object's composition is described in its model as an array of id's; its composition capability provides a means to retrieve the actual domain object instances associated with these identifiers asynchronously.
- description: When used as an object property, this refers to the human-readable description of a thing; usually a single sentence or short paragraph. (Most often used in the context of extensions, domain object models, or other similar application-specific objects.)
- domain object: A meaningful object to the user; a distinct thing in the work support by Open MCT. Anything that appears in the left-hand tree is a domain object.
- identifier: A tuple consisting of a namespace and a key, which together uniquely identifies a domain object.
- model: The persistent state associated with a domain object. A domain object's model is a JavaScript object which can be converted to JSON without losing information (that is, it contains no methods.)
- name: When used as an object property, this refers to the human-readable name for a thing. (Most often used in the context of extensions, domain object models, or other similar application-specific objects.)
- navigation: Refers to the current state of the application with respect to the user's expressed interest in a specific domain object; e.g. when a user clicks on a domain object in the tree, they are navigating to it, and it is thereafter considered the navigated object (until the user makes another such choice.)
- namespace: A name used to identify a persistence store. A running open MCT application could potentially use multiple persistence stores, with the