[x] Create and edit pages are just basic ones for all the info we need.
[x] No delete for this point.
Then:
[x] Research an implement an efficient way to stream images from the database to the browser. Don't want the memory usage to spike 200% again... See notes
[x] Allow an image to be uploaded for each animal.
[x] Turn the table index into something that reflects the design of the old farm master.
Then:
[x] Add a characteristics table (and support for it in the database) on the edit page, this shouldn't actually be too bad, since the characteristics HTML is stored in its own template, and the AJAX callbacks are super simple to make.
Then:
[x] Add ability to create and attach life events to animals.
Then:
[ ] Add in the ability to delete/hiding animals, as they're the main focus in this system, we'll likely have to go the route of marking animals as "End of system" rather than flat out deleting them.
Considerations for future and present:
Once an animal reaches end of system, should we only keep one of their images? Images take up a fair amount of space that I don't have the money to keep extending (though, once it's ready for AIM and Andy's paying for the servers and stuff, then it's his problem >:D).
Notes:
I completely give up on trying to make uploading an image not explode the RAM usage. This version seems much better than the old version though, as a singular user can constantly upload images with a stable amount of memory (except it jumps up ~200MB the first time, before stabilising), which I suspect is down to my preemptive use of reusing memory (C# makes this harder than it should be btw).
Downloading images from the server is infinitely more better than before though, hardly any impact on memory, I think the old version may have been going through EF when it shouldn't have, likely causing the massive spikes.
To start:
[x] Index is just a normal table index.
[x] Create and edit pages are just basic ones for all the info we need.
[x] No delete for this point.
Then:
[x] Research an implement an efficient way to stream images from the database to the browser. Don't want the memory usage to spike 200% again... See notes
[x] Allow an image to be uploaded for each animal.
[x] Turn the table index into something that reflects the design of the old farm master.
Then:
Then:
Then:
Considerations for future and present:
Notes:
I completely give up on trying to make uploading an image not explode the RAM usage. This version seems much better than the old version though, as a singular user can constantly upload images with a stable amount of memory (except it jumps up ~200MB the first time, before stabilising), which I suspect is down to my preemptive use of reusing memory (C# makes this harder than it should be btw).
Downloading images from the server is infinitely more better than before though, hardly any impact on memory, I think the old version may have been going through EF when it shouldn't have, likely causing the massive spikes.