MyFavMirrors/moonfire-nvr
1
0
Fork 0
mirror of https://github.com/scottlamb/moonfire-nvr.git synced 2024-12-26 23:25:55 -05:00
Code Issues Packages Projects Releases Wiki Activity
e7527af24c
moonfire-nvr/ui/package.json

71 lines
2.0 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
{
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"name": "ui",
"version": "0.1.0",
"private": true,
"dependencies": {
upgrade to @material-ui 5.0 alphas (and various other lockfile upgrades. "npm audit" is clean.) The date picker to use with 4.0 is unmaintained, and the new one is apparently quite different. Given that 5.0 is expected to be released this quarter, I prefer to jump straight to the new one and get things working with it, even if it means using an alpha in the short-term.
2021-02-22 19:45:53 -05:00
"@emotion/react": "^11.1.5",
"@emotion/styled": "^11.1.5",
"@material-ui/core": "^5.0.0-alpha.25",
"@material-ui/icons": "^5.0.0-alpha.24",
"@material-ui/lab": "^5.0.0-alpha.25",
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"@types/jest": "^26.0.20",
"@types/node": "^14.14.22",
"@types/react": "^17.0.0",
"@types/react-dom": "^17.0.0",
upgrade to @material-ui 5.0 alphas (and various other lockfile upgrades. "npm audit" is clean.) The date picker to use with 4.0 is unmaintained, and the new one is apparently quite different. Given that 5.0 is expected to be released this quarter, I prefer to jump straight to the new one and get things working with it, even if it means using an alpha in the short-term.
2021-02-22 19:45:53 -05:00
"@fontsource/roboto": "^4.2.1",
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"gzipper": "^4.4.0",
"react": "^17.0.1",
"react-dom": "^17.0.1",
"react-scripts": "4.0.1",
"typescript": "^4.1.3"
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
},
"scripts": {
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"start": "react-scripts start",
"build": "react-scripts build && gzipper compress --exclude=png,woff2 --remove-larger ./build",
"test": "react-scripts test",
"eject": "react-scripts eject",
"format": "prettier --write src/ public/",
"check-format": "prettier --check src/ public/",
restructure into "server" and "ui" subdirs Besides being more clear about what belongs to which, this helps with docker caching. The server and ui parts are only rebuilt when their respective subdirectories change. Extend this a bit further by making the webpack build not depend on the target architecture. And adding cache dirs so parts of the server and ui build process can be reused when layer-wide caching fails.
2021-01-22 17:43:41 -05:00
"lint": "eslint 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
},
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
],
"rules": {
"no-restricted-imports": [
"error",
{
"name": "@material-ui/core",
"message": "Please use the 'import Button from \"material-ui/core/Button\";' style instead; see https://material-ui.com/guides/minimizing-bundle-size/#option-1"
},
{
"name": "@material-ui/icons",
"message": "Please use the 'import MenuIcon from \"material-ui/icons/Menu\";' style instead; see https://material-ui.com/guides/minimizing-bundle-size/#option-1"
}
]
}
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
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
},
"devDependencies": {
start a new React-based UI (#111) This doesn't do much yet but should provide a better foundation for improvement than the jQuery UI, as described in the github issue.
2021-02-01 00:55:25 -05:00
"@testing-library/jest-dom": "^5.11.4",
"@testing-library/react": "^11.1.0",
"@testing-library/user-event": "^12.6.3",
"http-proxy-middleware": "^1.0.6",
"msw": "^0.26.1",
"prettier": "2.2.1"
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
}
}
Reference in New Issue Copy Permalink