refactor,feat: show location, use exif creation date

[ananasmoe]

[THEGOLDENPRO]

yeah so in the last few commits I moved some source files...

but we can fix this

[ananasmoe]

what the fuck?

alright i'm too tired for this shi, fix the merge conflicts pls thanks :3

[THEGOLDENPRO]

fix the merge conflicts pls thanks :3

no worries, will do

[THEGOLDENPRO]

ReverseGeocoder::new() takes too long to initialize, there's an actual delay until image info opens, although no need to worry because I was planning to make ExpensiveData::new() run in an asynchronous manner anyways as checking the size of a file may also take a while too.

This should be possible with just normal rust threading and putting ExpensiveData behind a Mutex<T>, then try_lock while trying to read it for the grid fields. If it fails to lock that means the thread is still writing to the data hence we should just set the specific field (e.g: file size) to something like unknown or loading, then when the data is available it will automatically allow us to lock and read.

[THEGOLDENPRO]

Also I'll like a config to disable this feature. Not sure where to put though, most likely under [ui].

[THEGOLDENPRO]

Oh write we should also fallback to file creation date for originally created exif tag. I should have wrote that in a comment sorry.

[ananasmoe]

I'll try implementing the try_lock stuff and you mean that the location can be disabled in the config?

[THEGOLDENPRO]

Yeah I was thinking of a config to hide it but maybe the setting should also disable initing ReverseGeocoder completely.

[ananasmoe]

@THEGOLDENPRO

[THEGOLDENPRO]

I'm on mobile right now so I can't see all the code properly yet but why didn't you just thread it on line 440 (where we do get_or_insert)? That was my plan and I think it would have been a lot easier. You wouldn't have needed to change anything on ExpensiveData.

[ananasmoe]

I'm on mobile right now so I can't see all the code properly yet but why didn't you just thread it on line 440 (where we do get_or_insert)? That was my plan and I think it would have been a lot easier. You wouldn't have needed to change anything on ExpensiveData.

honestly uhm, it just didn't pop into my head that i could do that.

[THEGOLDENPRO]

btw I'll fix the merge conflicts for you dw.

[THEGOLDENPRO]

This is a really cool feature btw, thanks.