How do I get KDE to work with this?
by
Green+Light
·
· Score: 3, Interesting
From the linked site:
New in X11 v0.2:
Support for Gnome, KDE hints etc.
I was using the first edition of this, and could not get KDE to compile (using fink).
Before I waste 5 more hours of my (precious) time, does anyone know if KDE will now compile with this new edition?
-- "Send an Instant Karma to me" - Yes
fink and apple's x11
by
brarrr
·
· Score: 3, Interesting
What do I need to know about having fink work with apple's x11. I have fink installed on my new ibook, but wanted to wait to see if i should install xfree86 or apple's x11 implementation.
what settings do i set, where, and how. what are the differences between that and xfree86?
-- to email me: take my/. handle and append.net preceded by charter.
What a crock... [Re:Why the rev change?]
by
Xcapee
·
· Score: 4, Interesting
Was this a troll or lame attempt at humour?
Firstly the X11 thing is beta.
Secondly safari is a beta.
Thirdly, your last link is not even Apple sw.
Given your attitude, I'd say you are too dumb or too careless to be able to figure that out.
Q: How much free software have you released without need for revision?
-- Oh shoot! Sig block again.
Re:Thank you Apple...
by
spitzak
·
· Score: 2, Interesting
The timeout before the focus change was the solution I first thought of and seems like the obvious one. However after thinking about it awhile (but not really having any system to test it on) I think the idea of waiting for a keystroke to change the menubar may be much better. A system that does not rely on a timeout would be much cleaner and predictable.
The other problem is something common to Linux and Windows, which is a confusion between being on top and having the focus. Unfortunately sometimes these are entangled quite badly at low levels in the system (X does not have this problem but new X window managers do). I can think of no other reason why Carbon has to be on top than the fact that the carbon interface to raise and give focus are the same and thus there is no way to tell the program otherwise. The double-buffered Quartz could easily emulate any graphic effects such as reading back from the screen so there is no technical reason why Carbon cannot act like Cocoa, it is certainly a limitation of the Carbon API.
Your problem with terminals is exactly what I have been yelling about here for months: CLICK SHOULD NOT RAISE WINDOWS!!!! This has been an endless frustration as it makes overlapping windows useless. And every time I say it some moron will say "but if some raise and some don't it will be inconsistent and confuse the user". That is bull and paranoid thinking like that is going to keep alternative GUI's from ever being better than Windows.
Slashdot Mirror
"Send an Instant Karma to me" - Yes
What do I need to know about having fink work with apple's x11. I have fink installed on my new ibook, but wanted to wait to see if i should install xfree86 or apple's x11 implementation.
what settings do i set, where, and how. what are the differences between that and xfree86?
to email me: take my
Was this a troll or lame attempt at humour?
Given your attitude, I'd say you are too dumb or too careless to be able to figure that out.
Q: How much free software have you released without need for revision?
Oh shoot! Sig block again.
The other problem is something common to Linux and Windows, which is a confusion between being on top and having the focus. Unfortunately sometimes these are entangled quite badly at low levels in the system (X does not have this problem but new X window managers do). I can think of no other reason why Carbon has to be on top than the fact that the carbon interface to raise and give focus are the same and thus there is no way to tell the program otherwise. The double-buffered Quartz could easily emulate any graphic effects such as reading back from the screen so there is no technical reason why Carbon cannot act like Cocoa, it is certainly a limitation of the Carbon API.
Your problem with terminals is exactly what I have been yelling about here for months: CLICK SHOULD NOT RAISE WINDOWS!!!! This has been an endless frustration as it makes overlapping windows useless. And every time I say it some moron will say "but if some raise and some don't it will be inconsistent and confuse the user". That is bull and paranoid thinking like that is going to keep alternative GUI's from ever being better than Windows.