LycheeOrg / Lychee

A great looking and easy-to-use photo-management-system you can run on your server, to manage and share photos.

Home Page:https://lycheeorg.github.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Enhancement] timeline view of photos

oliverrahner opened this issue · comments

I come from using DS Photo, the proprietary solution from DiskStation. I don't like it mainly for being closed source and for its performance, that's why I'm trying to switch to Lychee.

Anyways, they provide a feature which helped me a lot while navigating through my big, messy, unsorted pile of photos:

Show all images from the whole gallery, ordered by time.
Of course this could be accompanied by lots of other filters for tags, location [don't know if the database exposes that information in suitable way currently], albums...

I'm thinking about hacking together some sort of solution for Lychee only for myself but decided to check if other people needed this as well, and then maybe put in some more effort.

I like the idea.

The details of implementation are a bit more complex as I am currently rewriting the front-end to work with Livewire.

location [don't know if the database exposes that information in suitable way currently]

We do have an opt-in reverse location search.

So, if I started working on this, should I wait for something from your side to be finished or base off a certain branch for efficiency?

Not necessarily.

I would enable the livewire mode in your .env by adding a line LIVEWIRE_ENABLED=true.

And then you can navigate to https://example.com/livewire/ to see what the new layout look like.
Do note that:

  1. it aims to be visually the same (as close as possible, there will be modifications)
  2. it is barely functional (it is pretty much a "read only", there is no mouse interaction yet -- right click)
  3. it does not depends on JS that much anymore => the heavy lifting is now done in blade-php.

From there you can add a new livewire route in web.php and start hacking a new timeline page.

Sure your functionality will not be available directly, but this will avoid to do double the work
(one for the JS front-end, one for the future front-end).

I let you decide which you prefer.

Also know that @nagmat84 is doing a significant refactoring of the back end at the moment.
I don't know how much progress he made on that. :)

Hey, this is something that I would also be very interested in.

Tnx :)