Commit Graph

30 Commits

Author SHA1 Message Date
17cf0cf1e6 Render main and inspector using angular 2018-08-16 16:37:48 -07:00
0d53898af9 Build refactor to webpack (#2139)
* Move to webpack build
* Use webpack for building openmct.  Move SCSS to one folder and load
all core css up front.  Remove bower, begin removing gulp in favor
of npm run.
* Uses eslint instead of jshint and jscs.  Merge style checking rules
into .eshintrc.js, carrying over core parts of crockford style and
our adaptations.  Current code base fails to pass the linter, want
to separate linter changes from fixes to linting rules.
* Support for Vue SFC with example
* Remove outdated examples
* Use HTML loader for html (supports relative imports of resources e.g.
images) and raw-loader for when javascript must be loaded as text.
2018-08-07 14:47:50 -07:00
c55eaeb193 [Copyright] Update copyright year across platform code references
Fixes #2034.
2018-05-14 15:46:17 -07:00
185567cf29 [Licenses] Update copyright year to 2017
Fixes #1517
2017-04-05 14:52:46 -07:00
c8898ac6aa [Documentation] Updated copyright statement. Fixes #1081 2016-07-12 16:55:57 -07:00
0b11ddbcfd [Build] Satisfy JSHint
Restore globals lost during removal due to merge, remove unused
variables and use threequals in new scripts.
2016-04-08 16:22:40 -07:00
5088453712 [Build] Remove use strict, global
Remove usages of use strict and global declarations that are
no longer necessary with JSHint configuration, from files
added/changed since #724
2016-04-08 16:11:12 -07:00
a8f7bc01c3 [Build] Redeclare globals 2016-03-04 10:53:12 -08:00
ac5ac8d34e [Build] Remove boilerplate from scripts
No longer necessary after JSHint configuration.
2016-03-04 10:46:38 -08:00
3a4f6a7229 [Build] Update dependency references
...to reflect movement of third-party libraries to
bower_components.
2016-01-28 11:18:57 -08:00
69c5b110bf [API Refactor] Move out non-global require config 2016-01-13 12:41:15 -08:00
52579fefe1 [API] Simplify RequireJS config 2016-01-07 15:29:19 -08:00
a39e8e44f0 [API] Load bundles from imperative registry 2016-01-06 11:22:44 -08:00
65fb5ab2a5 [API] Move angular dependency inward 2016-01-06 11:15:36 -08:00
9f66f39d8d [API] Add a top-level main.js
...which can depend upon the bundle registry, as well
as a set of installed bundles.

https://github.com/nasa/openmctweb/issues/450
2016-01-06 10:59:21 -08:00
fdc875379f [API] Refactor out application initialization
...to simplify insertion of an imperative bundle registry,
WTD-450.
2016-01-06 10:44:53 -08:00
31eb366e7f [JSDoc] Add namespace docs
WTD-1482.
2015-08-07 12:13:15 -07:00
c08a460d30 [JSDoc] Add annotations
Bulk-add JSDoc annotations, WTD-1482.
2015-08-07 11:44:54 -07:00
10863514cb [Licenses] Add license headers
WTD-1051.
2015-05-13 16:43:30 -07:00
c0163d2d60 [Logging] Wire in log levels
Wire in log levels to allow specifying as a query string
parameter; defaults to logging only warnings and above,
for WTD-793.
2015-02-03 18:42:30 -08:00
9d8885d48f [Framework] Add extension sorter
Add priority ordering to loaded extensions in each category;
this allows control over the resulting order of extensions
acquired and used within the application. WTD-590
2015-01-07 16:39:57 -08:00
96aaea5e58 [Framework] Add RequireJS configurator
Add a configuration step (as part of the resolve phase)
to the framework layer, where bundle-defined paths and shims
are passed to RequireJS configuration. This permits both
the use of non-AMD modules and the exposure of libraries
across bundles. WTD-568.
2015-01-02 17:46:50 -08:00
08ff75c9c0 [Framework] Bring in changes from sandbox
Bring in changes from 'sandbox' branch. These include:

* Reconfiguring require's baseUrl such that relative
  paths work as expected in define call dependencies.
  Previously this only worked as expected in the
  framework bundle, since data-main points there.
* Add support for a 'constants' category of extension,
  to define application constants from bundles. This
  allows services to treat static values (such as
  persistence URIs) as injectable dependencies.
* Various assurances that properties from extension
  definitions will be exposed upon resolved
  implementations, even after partial construction.

WTD-572.
2014-11-20 10:37:27 -08:00
73e767228f [Framework] Refactor source folder
Refactor framework source folder; move each initialization
stage into its own directory. WTD-518.
2014-11-05 12:18:19 -08:00
dbd5b148e2 [Framework] Add comments, logging
Add additional comments and logging to components
of the framework layer. WTD-518.
2014-11-04 17:17:35 -08:00
ed4c178a76 [Framework] Log application bootstrapping
Log bootstrapping phase of framework layer initialization.
WTD-518.
2014-11-04 16:13:09 -08:00
86df248096 [Framework] Add angular-route
Add angular route library and utilize when instantiating
framework-driven module. This allows invocation of ng-view
by way of defined routes. WTD-518.
2014-11-04 14:38:49 -08:00
19bfeb4d03 [Framework] Wire up framework layer
Wire up and invoke framework layer components for
application start up, from main point-of-entry.
WTD-518.
2014-11-04 13:46:17 -08:00
0e82250c84 [Framework] Continue implementing fundamentals
Continue implementing classes which represent fundamental
concepts within the framework layer. WTD-518.

In particular, add methods which will be useful during the
extension resolution phase of framework start up.
2014-11-03 08:45:14 -08:00
de409fd8e7 [Framework] Begin work on main point-of-entry
Add main point-of-entry script for framework layer; performs
only minimal tasks of loading framework dependencies
and demonstrating that bundle list can be loaded
using these. WTD-518.
2014-10-31 16:43:18 -07:00