Linked by pepa on Fri 9th Nov 2012 23:18 UTC
Permalink for comment 541777
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2006-01-01
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