You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@PotatoPalooza
Member PotatoPalooza commented on Mar 1, 2023
Currently the web-server's model's are outdated and do not properly encapsulate the features we are planning to add for the MVP live release. The current DB scheme will have to be rewritten to further separate currently nested objects and allow greater flexibility with adding new queries and features. These new schema should be documented in the refactor section of the web-server readme.
Additionally the new models should centralize file operations. All loading and saving of image and video data should be handled in the models section of the code so the data base and file operations are hidden from the rest of the code base. We will need to decide if Video and Image objects are able to save themselves or if additional managers should handle these operations.
I recommend checking out this video as it goes into a design pattern perfect for this issue. Once these models are complete we will begin updating the rest of the codebase to use this new scheme.
The text was updated successfully, but these errors were encountered:
Should be handled by V3. ALmost all services are now injected and further decoupled. DB Schemas have been expanded for more functionality. See go-web-server wiki for DB changes
From NeRF-or-Nothing/vidtonerf#74
@PotatoPalooza
Member
PotatoPalooza commented on Mar 1, 2023
Currently the web-server's model's are outdated and do not properly encapsulate the features we are planning to add for the MVP live release. The current DB scheme will have to be rewritten to further separate currently nested objects and allow greater flexibility with adding new queries and features. These new schema should be documented in the refactor section of the web-server readme.
Additionally the new models should centralize file operations. All loading and saving of image and video data should be handled in the models section of the code so the data base and file operations are hidden from the rest of the code base. We will need to decide if Video and Image objects are able to save themselves or if additional managers should handle these operations.
I recommend checking out this video as it goes into a design pattern perfect for this issue. Once these models are complete we will begin updating the rest of the codebase to use this new scheme.
The text was updated successfully, but these errors were encountered: