tzoannop wrote:3. Submitting Bugzilla reports about Gnome is even more pointless than trying to reassemble Humpty Dumpty. The main problem with Gnome 3 is more its design than its execution. Bugs are usually the product of bad execution. Here, we're talking about a workflow that doesn't work, a complete lack of ergonomics and absolutely pointless hardware requirements.
When you have an issue that is not a Bug, but a most basic design flaw that is without dysfunctional computer code, where exactly do you file it so that Gnome Listen - take notice - and even consider acting upon it?
Does Bugzilla input need to be prefixed and run with Sudo, Pseudo or even GKPseudo? Is that the issue?
I am aware that it has been highlighted for some time - but it would seem that the wrong channels have been used, else there is a deafness issue that defies reasonable adjustment - let alone basic logic and real world living!
All that has been needed for so long is Sort of like getting a Redmond and selecting "Classic"!... or "The Right"
as end user, and the opportunity, to right click and make the naughty Launcher move where is most accessible for you and your needs - and does not cause detriment and or disability due to anti social programming attitudes that only comply with one Standard - The Social Model Of Disability - Fail Section!
I keep wondering where do you file the Social Model Of Disability - FAIL
as a Bug where GUI designers are concerned?
It just does not seem to Compile or Run in Python - Ruby - Java - C.... in fact it seems to require a whole new Compiler to be built and designed to get into, and even have basic root access to, some "Wetware"
that is already hard coded all the wrong way - and beyond obsolete!
Is it a Bios issue or a Bias issue?
Where is there a Bugzilla option that deals with poorly coded and dysfunctional Wetware
at the Gnome end?
Lets have a look at a basic of Interface design, Ergonomics and Work flow that has been about for nearly 20 years.
Gnome 3? Unity? Can an end user readily and easily shift the primary input focus/Task Bar/Primary Launcher selector to the right side of the screen (or for that matter any place on the screen which meets their access needs) with minimal mouse clicks - that is "Right Click" - "Properties" - select "Right" - "Close" - get on with using the DUMB Machine in an accessible and rational manner and without needing Third Party intervention, Program or Auxiliary Aide?
That is - does the End user have personal power, free of third party intervention, be that person of application, to alter the desktop in the most basic fashion, following basic GUI Design and known and established best practice, to overcome basic access issues caused by Disability?
And the answer is...........?
It's been standard interface design and practice as disability adjustment ever since it was first raised with some folks in Seattle back in the 90's. Some other interface designers and OS manufacturers were dismissive at the time.... but even they caught on to the commercial value of end user experience - and have been ever so fruity about it ever since.
Some even see selecting a theme as just a personal choice - and yet because it does not have any significance to them, they do not grasp that Overall theme colour and presentation can alter the ability of a Neuro Diverse person to be able to use a system. It's not just High Contrast - or colour blindness that is the issue!
Some defaults and readily accessible options are there for very good reason - and it seems that rational reasoning has become lost in the mists of time and the view of some that the basics
don't apply to them.
- what is the point of doing a whole degree in I.T. and Psychology - designing GUIs as you go - and integrating accessibility at all stages as a core requirement and design imperative?
It's all just so 1984 and last Century!
Some have just followed along and never grasped the underlying Logic and even Legal Obligations that they are are addressing by default
Why has it been there for so long?
It costs next to nothing to maintain and complies with all relevant codes of practices - best practice - and even legal obligations in Disability Access and prevention of Discrimination by Service Providers ... and even prevents one from being sued and facing massive legal costs - loss of reputation etc....!
It aint the programmers who can get sued - it's people such as Governments, Institutions and end service providers if they use a GUI that lacks basic disability access Functionality - like moving the Task Bar - Primary Interface Portal - The Big Button with the logo on it..... where it is most accessible to the End User!
It even respects the work of so many - across so many fields of disability who have been advising, testing and even requiring access since the dawn of the PC ...... and all free of charge, so Open Source and Community Empowering!
Its so basic it would seem that the standard
has become lost in the mists of time!
Oh - but all that work was not coded in computer language and slapped with an open source user agreement - and it aint mentioned under GNU!
It couldn't be - just as it couldn't be patented.
I fear that even if it had been so coded, some would still miss it's significance due to Terminal Myopia and the rush past the Bleeding Obvious for some personally significant Bleeding Edge experience!
Is it really going to be necessary to go dusting off research work and Theses from the 1970's/80's/90's across multiple institutions on a global scale to get some to deal with reality?
Where do those documents fit in Bugzilla - and would they even be read?
Would they actually care?
Then - some Uber Gurus have a wheel to reinvent for personal amusement - and they throw away the basics because they have no grasp of their reason, logic and Global Implications. To them it is not reality - just a self aggrandising great experiment and a personal vision for their personal desktop!
...and to them Disability Access is nothing other than a coding issue on making Orca work - and anything else more basic and fundamental is out-with their grasp - Poorly Coded and Dysfunctional Wetware is the issue!
Disability Accessibility starts at the desktop and is not an add on or optional extra!
It is a core design imperative that takes precedence over all other issues - ask the big corporate boys - they have been at it and working to avoid legal and public embarrassment for so long!
Now - you tell me where the bug is in the Gnome 3 Code - or is there a more basic and far more fundamental coding error (not written in any computer language or code) that is outside of the capacity of Bugzilla and Standard Reporting Practices?
Where is the log file so it can be studied?
It's really a Zero Day issue .... and time has run out.
Worse - it was a known issue at Day Zero and ignored which makes it far more than a coding bug! It's such a Fundamental error it is best called Mega SNAFU!
Gnome fallback and "Classic" seems to be the way that some are going in a hurried attempt
to sidestep the issue and avoid some fall out!
They do fail to address the fact that Unity still denies a person to choose Unity as an option and then make reasonable adjustment to overcome disability. They have to rely upon third party hacks - some which are not even available - and so Unity causes Disabled users to be discriminated against as soon as it's installed - by default. Whoops!
Oh how interesting It would be, or even will be, to see which has Primacy in Law - GNU clauses 15, 16 and even 17 - or other legislation On a National or even "Continental" basis!
I asked one chap - a Retired Judge - about this little catch phrase;
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
He laughed so hard, he had to open a bottle of Port!
It would seem that as Disability Accessibility and Reasonable Adjustment to that end is an "Anticipatory Duty"
and legal obligation which comes into play before anyone even installs an OS - Desktop or what ever - GNU is subordinate to some rather significant law and has a very low priority should any sitting Judge look at it!
The clause can tell the judge to interpret law the way GNU want - but I have to say, such Crass Stupidity has caused great hilarity and much drinking of Port!
That "Classic" option is there for a reason - as is "Compatibility" mode - and both avoid a number of issues including Disability Discrimination .... and legal issues in The Real World
! That's real world issues for end users - employers - institutions - governments......
After all - some with legal structures and offices and operations in the UK may be worried about such things as The Equality Act - the Equality And Human Rights Commission - European Law .... and the fact that at least One European Government had chosen to Go Open Source because Gnome 2 allowed compliance with relevant Disability Discrimination Law across Europe .... and saved money too!
"Merde" said Seattle.
It would be so embarrassing if that Coup De Ta was reversed in favour of other providers who are worried and want their Governmental Clients worth Billion$ (and increased share options) to come back!
Hmm? GNU protects against what?
Possibly some examples of Cloud Cuckoo Land for those who have no liability as a private individual - who can code as he likes when he likes. After that it's rather useless and even infantile.
Gnome 3 is a dead end - and deserves all the derision that can be heaped upon it!
It has missed so much that is basic on all levels - and there are no excuses! NONE!
It may be superbly coded and conceived - but when the end user is crippled by it there is a very big issue that impacts upon Real World Reality and not some Virtual Reality Concept and Ego trip - and a pretty desk top with no readily accessible icons.
Gnome 3 is beyond rescue - it is un-salvageable.
The only rational course of action is to return to Gnome 2, recommence rational development, and reproduce some people's idea of a Gnome 3 GUI as an optional layer over a functional and legally compliant desktop based upon Gnome 2 - so The End User can go 3 or Classic in a few mouse clicks.
Of course, some have grasped that and become ever so "Mate"y.
Problem is that Mate is just another example of reinventing the wheel - and it will probably need 3 to 5 years on consistent, well managed and rational - controversy free - development before it is accepted as a true alternative to Gnome.
If Gnome 3 was a commercial project, 2 would still be under Pro-active development and 3 would be an optional overlay and that would have happened already - but as there is no commercial imperative to control excess zeal and frank stupidity......!
Well, it would seem that the Good Ship Gnome 3 will just sail on until it hits something very hard - and even then there will be a Band Playing On to the Bitter End! ... it's so April 15th!
I have been chatting with one user who is wondering about launching a new distro based exclusively upon Gnome 3 - and calling it "Titanic Linux"!
It has backing!
They have a great basic wallpaper already! Whoops - Glug Glug Glug!
Whoever has been the Uber Guru in charge at Gnome3 needs to be got rid of - and rational practices, world views, and even End User Need/Experience returned to as the focus upon which code is built! It is after all the core reason for having a GUI!
A GUI that empowers and enables is good. One that cripples any End User is not!
There is even a clear example in Gnome 3 of why the person with oversight of an IT project should be primarily outside of the field and End User biased and not code biased.
Good Code is about Good Code. Good Product is about End User Utility and Accessibility. The Two can be Mutually Exclusive when vision is lacking in leadership and management is not able to manage reality in it's widest real world nature!
Harsh - but there we have it!
Whilst Gnome 3 and others built upon it deny disabled users the rational and long standing opportunity, as developed standard
, to decide where the primary access point on a screen is best for them - well, such projects and Desktop Indictments
will only act as examples to others of how to Get It So
Wrong - and show how to avoid the Zero Day mess that is without computer code as the core issue - and is Gnome 3!
GUI designers take notice - KDE - Gnome 3 - and then Unity!
How many real world examples do some need to get some "Wetware"
out of snooze mode and even working anywhere near capacity?
One also has to wonder when, before the end of support for 10.04, Canonical/Ubuntu will tell Gnome to Fork Off?
Whilst some at Gnome may be hiding behind a GNU and loving the supposed protection it gives them - other none private individuals do have to deal with Real world reality and legal obligation - as well as making sure that come 2013 what ever offering they have to the public - and even the public and private sectors - does not become legally embarrassing and a "Cause Célèbre"!
Gnome foundation may end up missing some funding as it gets pulled - but then again reality is not to everyone's tastes or capacities - and they can always take reassurance from that GNU.