Feat: Drop down button for langage selection

[fe51]

Pitch

Currently, the language (see screenshot below) is selected via two separate buttons (one for French, one for Spanish).

In order to make the platform more user-friendly and to be able to integrate more languages, it would be great to have a drop-down button for language selection.

Suggestion

• Replace the two langages button to a drop down button, below some screenshots suggesting design (but open to ideas :) )
• It might be nice if the language the mouse hovers over came with a darker background.

Happy to discuss it, thanks a lot 🥳

Actual

Design Suggestions

[Matthew-DErrico]

Hi, I'd love to work on this issue! I'm a Computer Science student at the University of Florida, and I'm excited to contribute to improving the platform's usability. I'll start working on replacing the language buttons with a dropdown and implementing the hover effect for better visibility. Looking forward to getting this done! 🚀

[fe51]

Hi Matthew,

Glad to see you're taking care of this issue and your motivation 🚀
Thank you very much and I look forward to seeing the PR coming soon :)

The README should help you get the project running locally!
Also, don't hesitate to make an initial proposal if you're unsure about the design =)

[fe51]

Hi @Matthew-DErrico, how the implementation is going ?
Have a good day !

[Matthew-DErrico]

Hi @fe51 , I've had a lot of work lately so I apologize for the late response, but the plan is to have it done and submitted by this Monday,
Have a great rest of your day.

[fe51]

HI @Matthew-DErrico, that is perfect, I was just wandering, no rush (it can clearly be later than monday, manage as you can don't worry) and good luck with your work !
Have a good day :)

[Matthew-DErrico]

Hi @fe51, I'm embarrassed to say but I've been having trouble trying to run the the program which has stopped me in my tracks for a bit. I initially tried without needing to install poetry but eventually caved in and did it the correct way, however, now I am having issues with getting the API information set up within the .env file. I've created one but don't have the credentials to make it work and before going through all the work to get them I was wondering if all that was even necessary if I just want to run it locally in order to work on the drop down menu. And if so, I could use a little guidance as I've stared at the screen for so long that I'm starting to back track.

I do have docker (desktop) and poetry installed and have forked the repo onto my machine, I just can't seem to get it all running at http://localhost:8050/. And if it turns out i do need the credentials for the env. file then how would i got about that also?

Sorry for the hold up and thank you in advance!

[Matthew-DErrico]

@fe51
As a follow up, I have since tried to install Pyronear API in hopes that I can get the .env file credentials and be able to then run the Pyronear Platform, however, despite following the Pyronear API's instructions, I ironically encountered issues preventing me to get it running such as 'setup-s3.sh' being in CRLF instead of LF, needing a 'requirments.txt' file which didn't exist, 'alembic not found', etc, and I'm still debugging.

All that being said, I would really appreciate some help trying to get this platform running in order to be able to work on it as it does also relate to a course assignment yet I also want to do this right in order to benefit the platform.

[fe51]

Hi @Matthew-DErrico, thanks for the feedback.

I think the readme and the guidelines for running the whole project locally proprely need to be improved. I will get back to you as soon as I can with, I hope, the recipe to ensure that everything goes smoothly so that you can get on with the issue :)

I'm really sorry for the time lost launching the project !

[fe51]

Hi @Matthew-DErrico,

The project README has been updated to make it more clear the process of launching the project locally (by also launching, via a docker-compose, the services replicating the api and alerts).

If would be great if you can try again following the readme (and this section will be of particular help https://github.com/pyronear/pyro-platform?tab=readme-ov-file#run-the-service-via-a-development-environment)

Do not hesitate to provide us some feebacks about launching the service, it will be very helpful. In a way, it's the first form of contribution to make the repo more accessible in the future.