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
I believe that both open projects have something in common: distrochooser and de_showcase.
but... why: de_showcase and distrochooser?
distrochooser makes life easier for people who don't know Linux through a question and answer questionnaire, depending on the question and the answer - a linux distro will be displayed as a result. So... this helps in decision making when you don't know which linux distro to choose to install or what problems you will face when you choose some desktop environment in terms of design, ui, ux or linux distro with some program package etc.
On the other hand, there are scripts to automate configurations of desktop environments by recording the screen in Linux. So... Desktop Environment Showcase or de_showcase is a small project meant to create screenshot of 'stock' configurations of most Linux desktop environments.
Note: Just like in the first case, in the second case, we have a tool to help users in general with some automations. This is the meeting point, the balance where projects in a different way for a common user can be interesting.
use case: de_showcase and distrochooser
The Distrochooser use case with de_showcase goes like this: Distrochooser needs to update GUIs from time to time. In this sense, having an up-to-date open source repository of graphical interface or desktop environment can contribute with Distrochooser.
why write this use case here?
I recently wrote an issue explaining the benefit of de_showcase with distrochooser, my hope is to unite the interests in both projects open to most linux users or linux beginners.
I would like to contribute to 2 open source communities: distrochooser and de_showcase
I would like to know if the idea is possible or not
question/feedback
What do you all think of the idea?
The text was updated successfully, but these errors were encountered:
I'm all for this idea, that's pretty much the goal of de_showcase.
The only problem I see, is that some distros add a theme to the gui, or set some custom wallpapers, which won't be shown on ArchLinux.
I'd be happy to make an API for distrochooser if this project is interested :)
"Update: So... the maintainer of the de_showcase repository is interested in helping distrochooser.
I talked to the main maintainer of the de_showcase project - and there might be a api for gui in distrochooser - So, this makes it possible to update distrochooser if there is a new graphical interface in any linux distro for distrochooser."
I'm waiting for a response from both open projects.
Hi all.
I believe that both open projects have something in common: distrochooser and de_showcase.
but... why: de_showcase and distrochooser?
Note: Just like in the first case, in the second case, we have a tool to help users in general with some automations. This is the meeting point, the balance where projects in a different way for a common user can be interesting.
use case: de_showcase and distrochooser
The Distrochooser use case with de_showcase goes like this: Distrochooser needs to update GUIs from time to time. In this sense, having an up-to-date open source repository of graphical interface or desktop environment can contribute with Distrochooser.
why write this use case here?
question/feedback
What do you all think of the idea?
The text was updated successfully, but these errors were encountered: