MyFavMirrors
/
moonfire-nvr
mirror of https://github.com/scottlamb/moonfire-nvr.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
moonfire-nvr/package.json

42 lines
1.2 KiB
JSON
Raw Normal View History

add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
{
"author": "Scott Lamb <slamb@slamb.org>",
"bugs": {
"url": "https://github.com/scottlamb/moonfire-nvr/issues"
},
"scripts": {
Changes to allow active development of UI using webpack and hotloading. (#22) * Changes to allow active development of UI using webpack and hotloading. * Update to webpack 4 (will make this work) * Update webpack.config.js accordingly * Move webpack.config.js to its own directory * Split webpack.config.js into base.config.js, dev.config.js and prod.config.js * Update configs to be "right" for development vs production using --mode * Want configuration through (optional) local file that is not checked in * Updated package.json for newer babel-loader * Put in a proxy to localhost port 8080 for evelopment server. This allows "yarn start" to work on the machine where MoonFire's server is running. This would be the default situation. Users in a different setup can change the proxy settings.
2018-03-07 20:34:08 -05:00
"start": "webpack-dev-server --mode development --config webpack/dev.config.js --progress",
fix js lint errors
2020-05-08 21:43:05 -04:00
"build": "webpack --mode production --config webpack/prod.config.js",
"lint": "eslint ui-src"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
},
"dependencies": {
"jquery": "^3.2.1",
"jquery-ui": "^1.12.1",
Settings can now be taken from separate file with local override. * Various settings in settings-nvr.js module * settings-nvr-local.js can override settings-nvr.js * settings-nvr-local is unchecked file * Both files can be straight maps, or functions returning maps * webpack env and args available to those functions
2018-03-07 16:09:43 -05:00
"moment-timezone": "^0.5.13"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
},
"homepage": "https://github.com/scottlamb/moonfire-nvr",
"license": "GPL-3.0",
"name": "moonfire-nvr",
"repository": "scottlamb/moonfire-nvr",
"version": "0.1.0",
"devDependencies": {
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"@babel/core": "^7.8.6",
"@babel/preset-env": "^7.8.6",
"babel-loader": "^8.0.6",
"babel-plugin-transform-imports": "^2.0.0",
"clean-webpack-plugin": "^3.0.0",
"compression-webpack-plugin": "^3.1.0",
"css-loader": "^3.4.2",
"eslint": "^6.8.0",
"eslint-config-google": "^0.14.0",
"file-loader": "^5.1.0",
Major refactoring of UI code, small UI changes. (#48) * Major refactoring of UI code, small UI changes. * Single file index.js split up into separate modules * Modules for handling UI view components * Modules for handling JSON/Model data * Modules for support tasks * Module to encapsulate Moonfire API * Main application module * index.js simplified to just activating main app * Settings file functionality expanded * UI adds "Time Format" popup to allow changing time representation * CSS changes/additions to streamline looks * Recordings loading indicator only appears after 500ms delay, if at all * Address first set of PR change requests from Scott. * Add copyright headers to all files (except JSON files) * Fix bug with entering time values in range pickers * Fixed an erroneous comment and/or spelling error here and there * Fixed JSDoc comments where [description] was not filled in * Removed a TODO from NVRApplication as it no longer applies * Fixed bug handling "infinite" case of video segment lengths * Fixed bug in "trim" handler and trim execution * Retrofit video continues loading from separate PR Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com> * Address PR comments Signed-off-by: Dolf Starreveld <dolf@starreveld.com>
2018-03-20 10:03:12 -04:00
"html-loader": "^0.5.5",
upgrade minimum nodejs version, yarn dev deps Looks like I basically had to do this to keep up. With nodejs version 12 (current LTS), the version of fsevents I installed wouldn't build. A "yarn upgrade" by itself resulted in a new problem as described in #69. Conversely, the new versions don't install with nodejs 8. So I bit the bullet and upgraded all the dev dependency stuff and the nodejs at once. nodejs 10 seems capable of running either the old or new, fwiw. I'm a little sad that this seems to have made the UI bundle 5% larger. Before, "yarn build" said 350 KiB. After, 369 KiB. A little bit in several places. For example, jquery-ui.bundle.js went from 156 KiB (in 2 chunks) to 160 KiB (in 1 chunk) for some reason.
2020-03-02 00:57:51 -05:00
"html-webpack-plugin": "^3.2.0",
"prettier": "1.19.1",
"style-loader": "^1.1.3",
"webpack": "^4.41.6",
"webpack-cli": "^3.3.11",
"webpack-dev-server": "^3.10.3",
"webpack-merge": "^4.2.2"
add a basic Javascript UI The Javascript is pretty amateurish I'm sure but at least it's something to iterate from. It's already much more pleasant for browsing through videos in several ways: * more responsive to load only a day at a time rather than 90+ days * much easier to see the same time segment on several cameras * more pleasant to have the videos load as a popup rather than a link that blows away your position in an enormous list * exposes the fancier .mp4 generation options: splitting at lengths other than the default, trimming to an arbitrary start and end time, including a subtitle track with timestamps. There's a slight regression in functionality: I didn't match the former top-level page which showed how much camera used of its disk allocation and the total duration of video. This is exposed in the JSON API, so it shouldn't be too hard to add back.
2017-10-22 00:54:27 -04:00
}
}