Announcement

Collapse
No announcement yet.

GNOME 41 Beta Released With "Calls" SIP/VoIP Support, Wayland Improvements

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • nado
    replied
    Originally posted by reba View Post

    I am complaining from the sidelines as I don't use GNOME. Hewever I stil have an opinion about how their decisions are made and, because GNOME to some degree represents Linux as a whole, I feel affected eventhough I don't use it. We/I/you have an opinion about Windows, Microsoft and Apple, without using it, not?

    Also GNOME devs have a... reputation... about not looking too fondly/ignoring/yelling about and at feedback from the userbase, shoving off work to interested people to do it for them and then rejecting their merge requests, etc.
    It is good to voice your opinions, but giving an opinion without an alternative/solution seems kind of pointless. Imagine being a developer and all you hear are the same complaints and no suggestion on how to change/improve? I do not know any of these developers, so I can't really comment on how they are as people.

    Imagine you are working for a company and that company has assigned you with improving or implementing a certain feature. So you implement this feauture and then people complain about it or want you to change it. As an employee who is paid for this task, you would be disobeying your employer if you were to listen to change this feature based on user feedback. Another thing is, you are using your time at work to implement this feauture and what time you have leftover is your spare time... so people who look at this from the outside may not take this into consideration either.

    The other alternative is that you are a volunteer who decided to help on a feature that interests you and you receive complaints or feedback on what others want instead of your work. Not only is this insulting and potentially demoralizing, it is counterproductive as well. Perhaps if they had not volunteered for that feature, they might not have got involved in this project at all? I think that unless we have something to provide that is useful and productive, then we should avoid criticizing or complaining what others use their time on.

    The only exception to this would be if we are the employer or someone who paid for a service to be performed.

    Edit: This "reputation" may be perceived as being unhelpful, but you could also consider that they have limited time/funds to implement a feature. They may also have been contractually bound to implement a feature in a certain way - changing this based on feedback may be breach of contract. Then there is also the fact that they simply may disagree with you for idealogical or practictal reasons, which is something that is only human as well. If they were to cater to every single person and their opinions, they would never get anything done either.
    Last edited by nado; 25 August 2021, 04:11 AM.

    Leave a comment:


  • LinAGKar
    replied
    Originally posted by uid313 View Post
    Imagine if it had support for RCS (the successor to SMS and MMS) too.
    It looks to me like this is intended for just calls, and not text messages. Matrix support would be nice though.

    Leave a comment:


  • reba
    replied
    Originally posted by nado View Post



    Whenever there's a post relating to GNOME it seems people can't help themselves, they have to complain. We should start tagging these posts with #complaints maybe. I don't really understand... if these same users don't like a certain feature, then why not file a bug report or if that doesn't work, change it themselves? It's open source so there is nothing stopping them.
    I am complaining from the sidelines as I don't use GNOME. Hewever I stil have an opinion about how their decisions are made and, because GNOME to some degree represents Linux as a whole, I feel affected eventhough I don't use it. We/I/you have an opinion about Windows, Microsoft and Apple, without using it, not?

    Also GNOME devs have a... reputation... about not looking too fondly/ignoring/yelling about and at feedback from the userbase, shoving off work to interested people to do it for them and then rejecting their merge requests, etc.

    Leave a comment:


  • nado
    replied
    Originally posted by reba View Post

    Ewww, you are right, this really looks like it is going into a bad direction.
    Now you can't even determine if that text is just a label, an action-button, a checkbox (gray backdrop), etc. Next step: they drop the down arrow for combo-boxes.
    They also should make up their mind if they want to go the icon-only route or the text-only route or the mixed-between they sometimes use, it's inconsistent. Is there a way to choose between having text-only or icon-only?

    And what's the meaning of a blue background (Scan (blue) <-> Open (not))?

    And why does the "Cacnel" button have a background color?
    Originally posted by Mez' View Post
    Also, isn't everyone sick of blue buttons, switches, toggles and highlights? I just can't bear that blue anymore.

    Then the border-radius of those corners makes adwaita irrelevant in itself for any decent use, it looks way too childish.

    Finally, we already see the limit of that all-for-CSD-none-for-settigs strategy, the bar is already getting crammed to a point buttons and text are not set apart enough from the next to be spottable at first sight. Soon enough, you're going to spend time finding the buttons you're looking for, especially since they are not at the same place from an app to the next.

    Whether Gnome devs like it or not, theming for Gnome is an absolute necessity.
    Whenever there's a post relating to GNOME it seems people can't help themselves, they have to complain. We should start tagging these posts with #complaints maybe. I don't really understand... if these same users don't like a certain feature, then why not file a bug report or if that doesn't work, change it themselves? It's open source so there is nothing stopping them.

    Leave a comment:


  • Mez'
    replied
    Originally posted by reba View Post

    Ewww, you are right, this really looks like it is going into a bad direction.
    Now you can't even determine if that text is just a label, an action-button, a checkbox (gray backdrop), etc. Next step: they drop the down arrow for combo-boxes.
    They also should make up their mind if they want to go the icon-only route or the text-only route or the mixed-between they sometimes use, it's inconsistent. Is there a way to choose between having text-only or icon-only?

    And what's the meaning of a blue background (Scan (blue) <-> Open (not))?

    And why does the "Cacnel" button have a background color?
    Also, isn't everyone sick of blue buttons, switches, toggles and highlights? I just can't bear that blue anymore.

    Then the border-radius of those corners makes adwaita irrelevant in itself for any decent use, it looks way too childish.

    Finally, we already see the limit of that all-for-CSD-none-for-settigs strategy, the bar is already getting crammed to a point buttons and text are not set apart enough from the next to be spottable at first sight. Soon enough, you're going to spend time finding the buttons you're looking for, especially since they are not at the same place from an app to the next.

    Whether Gnome devs like it or not, theming for Gnome is an absolute necessity.

    Leave a comment:


  • skeevy420
    replied
    Originally posted by reba View Post

    Ewww, you are right, this really looks like it is going into a bad direction.
    Now you can't even determine if that text is just a label, an action-button, a checkbox (gray backdrop), etc. Next step: they drop the down arrow for combo-boxes.
    They also should make up their mind if they want to go the icon-only route or the text-only route or the mixed-between they sometimes use, it's inconsistent. Is there a way to choose between having text-only or icon-only?

    And what's the meaning of a blue background (Scan (blue) &lt;-&gt; Open (not))?

    And why does the "Cacnel" button have a background color?
    At first glance I think someone fucked up. Cancel, and Close, is done with their semi-transparent toggle style background. Since both close the window they're technically not toggle buttons and shouldn't be using that visual style.

    Well, I read the fine text in the picture and apparently Cancel and Close get a special pass in regards to the semi-transparent background stuff to make them easier to distinguish visually.

    How about making the fuckers use a Bright Red X like everyone else?

    Also, Tabs use that same semi-transparent style. Basically, if it's semi-transparent that's where the GNOME design team ran out of ideas to make different visual cues.

    So, to answer your first question -- they just ain't had the time to make Scan and Open semi-transparent.

    Leave a comment:


  • ColdDistance
    replied
    Originally posted by jacob View Post

    Geary is unusable for me. I need an email center to have fully featured, fully supported PGP implementation front and centre.
    Geary is bad joke compared to Evolution. Geary is a simple email client and Evolution is powerful tool for personal organization with support for Microsoft technologies.

    If Evolution dies I think I could use GNOME Calendar app, but for email I would move to Thunderbird.

    And it seems that GNOME 41 will improve Wayland support, but there isn't official DMA-BUF support for Radeon GPUs yet.

    Leave a comment:


  • uid313
    replied
    Originally posted by reba View Post

    Ewww, you are right, this really looks like it is going into a bad direction.
    Now you can't even determine if that text is just a label, an action-button, a checkbox (gray backdrop), etc. Next step: they drop the down arrow for combo-boxes.
    They also should make up their mind if they want to go the icon-only route or the text-only route or the mixed-between they sometimes use, it's inconsistent. Is there a way to choose between having text-only or icon-only?

    And what's the meaning of a blue background (Scan (blue) <-> Open (not))?

    And why does the "Cacnel" button have a background color?
    Scan is blue because it is a primary button.
    Open is not blue because it is an ordinary button.

    I don't know why the Cancel button has a background color, maybe it is because it only have text which might make it difficult to determine if its just a label or a button. The other buttons either have an icon or a dropdown chevron or something that indicates that it is some type of button.

    Leave a comment:


  • Mershl
    replied
    > - GDM now allows user sessions for single GPU vendor NVIDIA systems.

    Seems a "wayland" is missing in this sentence.

    Leave a comment:


  • reba
    replied
    Ewww, you are right, this really looks like it is going into a bad direction.
    Now you can't even determine if that text is just a label, an action-button, a checkbox (gray backdrop), etc. Next step: they drop the down arrow for combo-boxes.
    They also should make up their mind if they want to go the icon-only route or the text-only route or the mixed-between they sometimes use, it's inconsistent. Is there a way to choose between having text-only or icon-only?

    And what's the meaning of a blue background (Scan (blue) <-> Open (not))?

    And why does the "Cacnel" button have a background color?

    Leave a comment:

Working...
X