I just updated to Core 183 and now can confirm the problems that other users already mentioned: 1) Color: too bright 2) Missing penguin: looses personality 3) New font: readability suffers a lot. It's too thin and small. 4) What is the underscore in "IPFire_" (in the title) supposed to mean? Looks like a typo. For reference: https://community.ipfire.org/t/core-183-update-feedback/11111/5 https://community.ipfire.org/t/cu-183-testing-ipfire-logo-broken/10949/21 I didn't find the option for changing to another theme in GUI settings. Maybe this has been removed before, but it would be a nice way to keep the new design while also keeping users happy that prefer the classic design.
Hello, thank you for your feedback, but this is a lot that is very late. The design has been developed over a long time and we have taken certain decisions. I have commented on that in length on IPFire Community. Since this isn't a proper bug that requires action, I will close this.
Many people don't like the new look and complain about it, but it's too late to change something? Adding a separate theme is too late?
(In reply to Larsen from comment #2) > Many people don't like the new look and complain about it, but it's too late > to change something? Adding a separate theme is too late? It is not too late to change things, but we are not going to change the main choices on the new design. We have removed support for multiple themes a while ago, but if patches for that would be submitted, I do not see why those could not be merged. However, any alternative themes would have to be reviewed and approved by the development team. I don't think that there is any benefit in adding a large number of additional themes.
a fail in ergonomics is a design-bug and the feedback shows it is a big one. at least a simple choice between the existing/working classic-calm-viewable-unique-tuxed-theme and an all-new-fresh-shining-exiting-crazy-colored-theme should be considered for ergonomics.
(In reply to current user from comment #4) > a fail in ergonomics is a design-bug and the feedback shows it is a big one. That is incorrect. We have received a lot of positive feedback. Way more than negative. Sadly the negative feedback is going on at length on our forum, but that doesn't mean there is more people sharing that view. The new web site and the entire new design as received way more positive than negative feedback. > at least a simple choice between the existing/working > classic-calm-viewable-unique-tuxed-theme > and an > all-new-fresh-shining-exiting-crazy-colored-theme > should be considered for ergonomics. We have considered it, but it just creates too much work for us to make a few people happy. We have more urgent things to work on than keeping an old design alive. And to be honest, the entire time that I have spent now reading posts of this kind would have probably been better invested into improving what we have. Is it perfect? No, but we can make it better so that it becomes closer to perfect.
> We have more urgent things to work on than keeping an old design alive. Then why work on a new design in the first place?
looks we are on a dead end here. you are the dev and build the release, we no-devs have to accept that and respect your invisible big amount of exited feedback. other projects or a colorimeter are no valid source of data for stress on human eyes. i was not aware that i am considered a troll in the forums who wastes invalueable resources. i have to review my codebase.
(In reply to Larsen from comment #6) > > We have more urgent things to work on than keeping an old design alive. > > Then why work on a new design in the first place? I wasn't going to. It was an ask of the development community on the monthly call to align the web UI with the website. I said that I will do what I can with little effort as the UI has a lot of issues which don't allow us to make big changes. The patches were on the development list for about two weeks for review and received no feedback which is why I merged them in the end. (In reply to current user from comment #7) > i was not aware that i am considered a troll in the forums > who wastes invalueable resources. i have to review my codebase. I do consider this trolling because we are not moving anywhere in this conversation. I have other projects and commitments to work on and I won't change it. Volunteers have not come forward either (maybe Larsen is in the process of doing so?). I believe we have all said what we had to say.
(In reply to Michael Tremer from comment #8) > The patches were on the development list for about two weeks for review and > received no feedback which is why I merged them in the end. development list ≠ ipfire-community @larsen are you capable of bringing the patches to the development list to fix this?
(In reply to current user from comment #9) > (In reply to Michael Tremer from comment #8) > > The patches were on the development list for about two weeks for review and > > received no feedback which is why I merged them in the end. > development list ≠ ipfire-community It is. There is a clear development process. > @larsen > are you capable of bringing the patches to the > development list to fix this? I would rather invest time into a proper dark mode theme instead of bringing back old things.
> are you capable of bringing the patches to the > development list to fix this? No. Also, IMHO it would make more sense to revert the commit that removed theme support. The code has been there so there is no need to reinvent the wheel. >> development list ≠ ipfire-community > > It is. There is a clear development process. Not exactly. The dev list is just a part of the community. It's not like every single user is reading the dev list. In fact, I'd guess that only a very, very tiny percentage of non-devs does. Same goes for the reoccuring problem of "nobody with XYZ tested the dev release": Not everyone has subscribed to the blog and not everyone has the possibility to test a new version before release. So naturally, bugs will go unnoticed (and I don't blame you).