Linked by pepa on Fri 9th Nov 2012 23:18 UTC
Gnome "I'm writing to inform you that the release team discussed Drop or Fix Fallback Mode yesterday. We've come to the conclusion that we can't maintain fallback mode in reasonable quality, and are better off dropping it." Gnome-fallback has been my refuge, as I find both Unity and Gnome 3's shell unusable. Yes, we have been warned this would happen. I thought the cost of maintaining gnome-panel would be so low that it might never need to happen. But as it appears, it is deemed necessary. As for me, I'm bound for something Qt, as I am very angry at Gnome for abandoning its 'classic' users.
Permalink for comment 541777
To read all comments associated with this story, please click here.
RE[5]: Goodbye Gnome
by OSGuy on Sat 10th Nov 2012 07:44 UTC in reply to "RE[4]: Goodbye Gnome"
Member since:

Well you see, Timothy should not have to do this but unfortunately he does because there is no coherence between toolkits. The foundation of every toolkit is different! There should be like a central protocol where all developers can turn to and follow.

If what you said is true, it means that the functionality I specified is hard-coded to handle various different messages from different toolkits but this is not Timothy's fault and he should be praised for this because he tries to at least cover, lower the extent of the mess created by other developers!

With Windows, based on my own experience, regardless if the program looks like Office XP (super flat buttons), Office 95 (3D), Office 97 (flat) or is using the Ribbon UI, they all follow the same rules.

- Every window has a Window Procedure
- Every window receive the same messages: WM_ACTIVATE, WM_LBUTTONDBLCLK, WM_KEYDOWN ... you name it because they all derive from the same object.

This is why everything works with Windows because there is one central foundation to everything that's running and they are all related to particular objects following the same rules.

From what I have experienced, X.ORG does not have these rules and that's why everything is broken and nothing is compatible with each and even toolkits themselves are not compatible with each other with different versions. It's a joke but this can be fixed. Put everything in the past and start-over, create a protocol or if starting over is bad then take one toolkit and make it official and then everyone can use the same toolkit and improve it.

Edited 2012-11-10 07:59 UTC

Reply Parent Score: 1