2021-11-15 08:22:34 +01:00
|
|
|
{
|
|
|
|
|
"name": "lama-cleaner",
|
|
|
|
|
"version": "0.1.0",
|
|
|
|
|
"private": true,
|
|
|
|
|
"proxy": "http://localhost:8080",
|
|
|
|
|
"dependencies": {
|
|
|
|
|
"@heroicons/react": "^1.0.4",
|
2022-05-21 09:13:09 +02:00
|
|
|
"@radix-ui/react-dialog": "0.1.8-rc.25",
|
2022-09-15 16:21:27 +02:00
|
|
|
"@radix-ui/react-popover": "^1.0.0",
|
2022-05-21 09:13:09 +02:00
|
|
|
"@radix-ui/react-select": "0.1.2-rc.27",
|
2022-04-12 14:58:57 +02:00
|
|
|
"@radix-ui/react-switch": "^0.1.5",
|
2022-04-17 17:31:12 +02:00
|
|
|
"@radix-ui/react-toast": "^0.1.1",
|
2022-06-13 10:50:51 +02:00
|
|
|
"@radix-ui/react-tooltip": "^0.1.7",
|
2021-11-15 08:22:34 +01:00
|
|
|
"@testing-library/jest-dom": "^5.14.1",
|
|
|
|
|
"@testing-library/react": "^12.1.2",
|
|
|
|
|
"@testing-library/user-event": "^13.5.0",
|
|
|
|
|
"@types/jest": "^27.0.2",
|
2022-07-18 16:43:55 +02:00
|
|
|
"@types/lodash": "^4.14.182",
|
2021-11-15 08:22:34 +01:00
|
|
|
"@types/node": "^16.11.1",
|
|
|
|
|
"@types/react": "^17.0.30",
|
|
|
|
|
"@types/react-dom": "^17.0.9",
|
|
|
|
|
"cross-env": "7.x",
|
2022-07-18 16:43:55 +02:00
|
|
|
"lodash": "^4.17.21",
|
2022-09-15 16:21:27 +02:00
|
|
|
"mitt": "^3.0.0",
|
2022-06-28 16:25:52 +02:00
|
|
|
"nanoid": "^4.0.0",
|
2021-11-15 08:22:34 +01:00
|
|
|
"npm-run-all": "4.x",
|
|
|
|
|
"react": "^17.0.2",
|
|
|
|
|
"react-dom": "^17.0.2",
|
2022-10-26 16:07:06 +02:00
|
|
|
"react-feather": "^2.0.10",
|
2022-09-15 16:21:27 +02:00
|
|
|
"react-hotkeys-hook": "^3.4.7",
|
2021-11-15 08:22:34 +01:00
|
|
|
"react-scripts": "4.0.3",
|
|
|
|
|
"react-use": "^17.3.1",
|
2022-02-06 03:37:22 +01:00
|
|
|
"react-zoom-pan-pinch": "^2.1.3",
|
Complete GUI Refactor
This patch brings in a massive number of changes to the frontend of the application. Please feel free to discuss the proposed changes with me at any time.
Implemented Recoil as a state management system.
Why Recoil? It is a robust library built by developers at Facebook for state management. It has an extremely simple API for implementation that is in sync with React syntax compared to any other state management system out there and works amazingly well. While the official release status is beta as it becomes fully featured, the library is already used in various systems at Facebook and is very stable for the use cases of this application.
Why global state management? One of the major issues I saw with the current file structure is that there is minimal code splitting and it makes further development of the frontend a cumbersome task. I have broken down the frontend into various easy to access components isolating the GUI from the logic. To avoid prop drilling, we need global state management to handle the necessary tasks. This will also facilitate the addition of any new features greatly.
Code Splitting. Majority of the components that can be isolated in the application have now been done so.
All New Custom CSS & Removal of Tailwind
While Tailwind is a great way to deploy beautiful interfaces quickly, anyone trying to stylize the application further needs to be familiar with Tailwind which makes it harder for more people to work on it. Not to mention, I am not a particular fan of flooding JSX elements with inline CSS classes. That makes reading the code extremely hard and bloats up component code drastically.
As a replacement to Tailwind, I implemented a custom styling system using SCSS as a developer dependency.
In the new system, all the general and shared styles are in the styles folder and all the component styles are in the same folder as the component for easy access.The _index.scss file now acts as a central import for every other stylesheet that needs to be loaded.
What Changed?
The entire application looks and feels like the current implementation with minimal changes.
The green (#bdff01) highlight used in the application has now been changed to a bright yellow (rgb(255, 190, 0)) because I felt it better suited the new Dark Mode (see below).
The swipe bar for comparing before and after images has now been removed and instead the comparison is a smooth fade effect. I felt this was better to analyze image changes rather than a swiper. // Can add the swipe back if needed.
Dark Mode
A brand new Dark Mode has been added for the application. Users can enable and disable by tapping the button in the header or by using the Shift + D hotkey.
Other Misc New Features
When the editor image is now zoomed out to its default size, the image now also gets centered back.
TODO
The currently used react-zoom-pinch-pan module is not mobile friendly. It does not allow brush strokes. Need to figure out a way to fix this.
Further optimization of the frontend code with better code splitting and performance.
When using the LaMa model, the first stroke has a delayed response from the backend but the ones that follow are almost immediate. I believe this is happening because of the initialization of the model on the first stroke. I wonder if either of us can look at it and see if this can somehow be preloaded so the user experience is smooth from the first stroke.
Enable threading for the desktop application mode so flaskwebgui does not block the main applications Python console.
2022-03-28 06:52:05 +02:00
|
|
|
"recoil": "^0.6.1",
|
2022-09-15 16:21:27 +02:00
|
|
|
"socket.io-client": "^4.5.2",
|
2021-11-15 08:22:34 +01:00
|
|
|
"typescript": "4.x"
|
|
|
|
|
},
|
|
|
|
|
"scripts": {
|
Complete GUI Refactor
This patch brings in a massive number of changes to the frontend of the application. Please feel free to discuss the proposed changes with me at any time.
Implemented Recoil as a state management system.
Why Recoil? It is a robust library built by developers at Facebook for state management. It has an extremely simple API for implementation that is in sync with React syntax compared to any other state management system out there and works amazingly well. While the official release status is beta as it becomes fully featured, the library is already used in various systems at Facebook and is very stable for the use cases of this application.
Why global state management? One of the major issues I saw with the current file structure is that there is minimal code splitting and it makes further development of the frontend a cumbersome task. I have broken down the frontend into various easy to access components isolating the GUI from the logic. To avoid prop drilling, we need global state management to handle the necessary tasks. This will also facilitate the addition of any new features greatly.
Code Splitting. Majority of the components that can be isolated in the application have now been done so.
All New Custom CSS & Removal of Tailwind
While Tailwind is a great way to deploy beautiful interfaces quickly, anyone trying to stylize the application further needs to be familiar with Tailwind which makes it harder for more people to work on it. Not to mention, I am not a particular fan of flooding JSX elements with inline CSS classes. That makes reading the code extremely hard and bloats up component code drastically.
As a replacement to Tailwind, I implemented a custom styling system using SCSS as a developer dependency.
In the new system, all the general and shared styles are in the styles folder and all the component styles are in the same folder as the component for easy access.The _index.scss file now acts as a central import for every other stylesheet that needs to be loaded.
What Changed?
The entire application looks and feels like the current implementation with minimal changes.
The green (#bdff01) highlight used in the application has now been changed to a bright yellow (rgb(255, 190, 0)) because I felt it better suited the new Dark Mode (see below).
The swipe bar for comparing before and after images has now been removed and instead the comparison is a smooth fade effect. I felt this was better to analyze image changes rather than a swiper. // Can add the swipe back if needed.
Dark Mode
A brand new Dark Mode has been added for the application. Users can enable and disable by tapping the button in the header or by using the Shift + D hotkey.
Other Misc New Features
When the editor image is now zoomed out to its default size, the image now also gets centered back.
TODO
The currently used react-zoom-pinch-pan module is not mobile friendly. It does not allow brush strokes. Need to figure out a way to fix this.
Further optimization of the frontend code with better code splitting and performance.
When using the LaMa model, the first stroke has a delayed response from the backend but the ones that follow are almost immediate. I believe this is happening because of the initialization of the model on the first stroke. I wonder if either of us can look at it and see if this can somehow be preloaded so the user experience is smooth from the first stroke.
Enable threading for the desktop application mode so flaskwebgui does not block the main applications Python console.
2022-03-28 06:52:05 +02:00
|
|
|
"start": "react-scripts start",
|
|
|
|
|
"build": "cross-env GENERATE_SOURCEMAP=false react-scripts build",
|
2021-11-15 08:22:34 +01:00
|
|
|
"test": "react-scripts test",
|
Complete GUI Refactor
This patch brings in a massive number of changes to the frontend of the application. Please feel free to discuss the proposed changes with me at any time.
Implemented Recoil as a state management system.
Why Recoil? It is a robust library built by developers at Facebook for state management. It has an extremely simple API for implementation that is in sync with React syntax compared to any other state management system out there and works amazingly well. While the official release status is beta as it becomes fully featured, the library is already used in various systems at Facebook and is very stable for the use cases of this application.
Why global state management? One of the major issues I saw with the current file structure is that there is minimal code splitting and it makes further development of the frontend a cumbersome task. I have broken down the frontend into various easy to access components isolating the GUI from the logic. To avoid prop drilling, we need global state management to handle the necessary tasks. This will also facilitate the addition of any new features greatly.
Code Splitting. Majority of the components that can be isolated in the application have now been done so.
All New Custom CSS & Removal of Tailwind
While Tailwind is a great way to deploy beautiful interfaces quickly, anyone trying to stylize the application further needs to be familiar with Tailwind which makes it harder for more people to work on it. Not to mention, I am not a particular fan of flooding JSX elements with inline CSS classes. That makes reading the code extremely hard and bloats up component code drastically.
As a replacement to Tailwind, I implemented a custom styling system using SCSS as a developer dependency.
In the new system, all the general and shared styles are in the styles folder and all the component styles are in the same folder as the component for easy access.The _index.scss file now acts as a central import for every other stylesheet that needs to be loaded.
What Changed?
The entire application looks and feels like the current implementation with minimal changes.
The green (#bdff01) highlight used in the application has now been changed to a bright yellow (rgb(255, 190, 0)) because I felt it better suited the new Dark Mode (see below).
The swipe bar for comparing before and after images has now been removed and instead the comparison is a smooth fade effect. I felt this was better to analyze image changes rather than a swiper. // Can add the swipe back if needed.
Dark Mode
A brand new Dark Mode has been added for the application. Users can enable and disable by tapping the button in the header or by using the Shift + D hotkey.
Other Misc New Features
When the editor image is now zoomed out to its default size, the image now also gets centered back.
TODO
The currently used react-zoom-pinch-pan module is not mobile friendly. It does not allow brush strokes. Need to figure out a way to fix this.
Further optimization of the frontend code with better code splitting and performance.
When using the LaMa model, the first stroke has a delayed response from the backend but the ones that follow are almost immediate. I believe this is happening because of the initialization of the model on the first stroke. I wonder if either of us can look at it and see if this can somehow be preloaded so the user experience is smooth from the first stroke.
Enable threading for the desktop application mode so flaskwebgui does not block the main applications Python console.
2022-03-28 06:52:05 +02:00
|
|
|
"eject": "react-scripts eject"
|
2021-11-15 08:22:34 +01:00
|
|
|
},
|
|
|
|
|
"eslintConfig": {
|
|
|
|
|
"extends": "react-app"
|
|
|
|
|
},
|
|
|
|
|
"browserslist": {
|
|
|
|
|
"production": [
|
|
|
|
|
">0.2%",
|
|
|
|
|
"not dead",
|
|
|
|
|
"not op_mini all"
|
|
|
|
|
],
|
|
|
|
|
"development": [
|
|
|
|
|
"last 1 chrome version",
|
|
|
|
|
"last 1 firefox version",
|
|
|
|
|
"last 1 safari version"
|
|
|
|
|
]
|
|
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
|
|
|
|
"@typescript-eslint/eslint-plugin": "^5.1.0",
|
|
|
|
|
"eslint-config-airbnb": "^18.2.1",
|
|
|
|
|
"eslint-config-prettier": "^8.3.0",
|
|
|
|
|
"eslint-plugin-import": "^2.25.2",
|
|
|
|
|
"eslint-plugin-jsx-a11y": "^6.4.1",
|
|
|
|
|
"eslint-plugin-prettier": "^4.0.0",
|
|
|
|
|
"eslint-plugin-react": "^7.26.1",
|
|
|
|
|
"eslint-plugin-react-hooks": "^4.2.0",
|
Complete GUI Refactor
This patch brings in a massive number of changes to the frontend of the application. Please feel free to discuss the proposed changes with me at any time.
Implemented Recoil as a state management system.
Why Recoil? It is a robust library built by developers at Facebook for state management. It has an extremely simple API for implementation that is in sync with React syntax compared to any other state management system out there and works amazingly well. While the official release status is beta as it becomes fully featured, the library is already used in various systems at Facebook and is very stable for the use cases of this application.
Why global state management? One of the major issues I saw with the current file structure is that there is minimal code splitting and it makes further development of the frontend a cumbersome task. I have broken down the frontend into various easy to access components isolating the GUI from the logic. To avoid prop drilling, we need global state management to handle the necessary tasks. This will also facilitate the addition of any new features greatly.
Code Splitting. Majority of the components that can be isolated in the application have now been done so.
All New Custom CSS & Removal of Tailwind
While Tailwind is a great way to deploy beautiful interfaces quickly, anyone trying to stylize the application further needs to be familiar with Tailwind which makes it harder for more people to work on it. Not to mention, I am not a particular fan of flooding JSX elements with inline CSS classes. That makes reading the code extremely hard and bloats up component code drastically.
As a replacement to Tailwind, I implemented a custom styling system using SCSS as a developer dependency.
In the new system, all the general and shared styles are in the styles folder and all the component styles are in the same folder as the component for easy access.The _index.scss file now acts as a central import for every other stylesheet that needs to be loaded.
What Changed?
The entire application looks and feels like the current implementation with minimal changes.
The green (#bdff01) highlight used in the application has now been changed to a bright yellow (rgb(255, 190, 0)) because I felt it better suited the new Dark Mode (see below).
The swipe bar for comparing before and after images has now been removed and instead the comparison is a smooth fade effect. I felt this was better to analyze image changes rather than a swiper. // Can add the swipe back if needed.
Dark Mode
A brand new Dark Mode has been added for the application. Users can enable and disable by tapping the button in the header or by using the Shift + D hotkey.
Other Misc New Features
When the editor image is now zoomed out to its default size, the image now also gets centered back.
TODO
The currently used react-zoom-pinch-pan module is not mobile friendly. It does not allow brush strokes. Need to figure out a way to fix this.
Further optimization of the frontend code with better code splitting and performance.
When using the LaMa model, the first stroke has a delayed response from the backend but the ones that follow are almost immediate. I believe this is happening because of the initialization of the model on the first stroke. I wonder if either of us can look at it and see if this can somehow be preloaded so the user experience is smooth from the first stroke.
Enable threading for the desktop application mode so flaskwebgui does not block the main applications Python console.
2022-03-28 06:52:05 +02:00
|
|
|
"prettier": "^2.4.1",
|
|
|
|
|
"sass": "^1.49.9"
|
2021-11-15 08:22:34 +01:00
|
|
|
}
|
|
|
|
|
}
|
