I expect this has been debated to death elsewhere, but:
'I personally consider anything a "derived work" that needs special hooks in the kernel to function with Linux (ie it is _not_ acceptable to make a small piece of GPL-code as a hook for the larger piece), as that obviously implies that the bigger module needs "help" from the main kernel.'
Doesn't that precicely describe Nvidia's graphics driver? A GPL'd stub that wraps a huge proprietry blob of code?
This has been fixed for some time. Keyboard shortcuts work even when palette windows have the focus. The fact that they steal the focus at all is now merely cosmetic--if the colour of the windows' title bars didn't change then I wouldn't be able to tell the difference.
The last few versions of the Gimp have really improved.
No longer does every palette count as a separate window in the Alt-Tab list/window list.
Clicking on a palette no longer steals the focus from the document window*. This used to drive me insane.
The visibility of palettes can be toggled by pressing Tab.
Raising a document window now even raises the palettes along with it!
The one thing I find missing is a way to maximise the amount of space a document window takes up, without making it so large that parts of it are obscured by the palettes.
As much as I hate MDI, I have to admit that being able to maximise a subwindow, having previously docked the palettes into the main window is very handy. Likewise, on the Mac OS, the window manager knows to avoid overlaying a window on palettes or the dock when hitting 'the green button'.
So, all I want is for the Gimp to borrow this behaviour from the Mac OS. Have it avoid my palettes when maximising windows. The 'correct' place to implement this is probably even in Metacity. I don't really care who gets it fixed, but once it is, I will no longer have cause to complain about the Gimp's UI.
$ whatis Xnest Xnest (1x) - a nested X server $ help export export: export [-nf] [name[=value]...] or export -p
NAMEs are marked for automatic export to the environment of
subsequently executed commands. If the -f option is given,
the NAMEs refer to functions. If no NAMEs are given, or if `-p'
is given, a list of all names that are exported in this shell is
printed. An argument of `-n' says to remove the export property
from subsequent NAMEs. An argument of `--' disables further option
processing. $ whatis metacity metacity (1) - minimal GTK2 Window Manager $ whatis gimp gimp (1) - an image manipulation and paint program.
Xnest is from XFree86/Xorg. It creates a new X display as a client of another X display.
The DISPLAY environment variable tells an X client which display to connect to. Here,:1 indicates the nested X display created in the previous command.
metacity is the default window manager for the Gnome desktop. I chose it because I assume it is what most Gimp users use.
I expect it didn't work on your Mac OS X machine because you don't have XFree86/Xorg. Being on a Mac OS machine, you don't really need MDI since the Mac's window management scheme makes it easy to raise all the windows of an application at once, and to hide all the windows from another application. IIRC it's under "$Application -> Hide others".
I think his point was that, even though you detest rebooting into Windows to play your game, you still bought the game.
Their thinking is that the number of people who run Linux and who want to play a non-free game like WoW and who are not prepared to dual-boot to do so, multiplied by the typical revenue from a subscriber over the course of his subscription is less than the cost of developing and maintaining a Linux port of the game.
So why should Blizzard spend $lots on developing a Linux client when most of the potential market for the port already pay for the Windows port, and boot into Windows/run it via Wine?
I think the idea is to standardise what is already common practice. The LSB people could have sat down and codified everything according to How It Should Be -- but no one would have used it.
But if they used Jabber, then all the messy stuff--the gateways to other IM networks--run on Google's Jabber servers. If Microsoft started blocking them then as soon as the hackers at Google worked out how to bypass the block, the MSN transport could be brought back up.
From a user's poing of view, contacts on other networks would be no different from Jabber contacts: abc@talk.google.com, fred_bloggs223%hotmail.com@msn.talk.google.com, 1324354@icq.talk.google.com, etc.
Wow, I knew that the Flash settings UI was badly designed, confusing and annoying to use. I didn't know that it set up tracking with partner sites as well.
Besides, what steps does Flash take to ensure that any old web site can't just reset these permissions, or except itself to the 'no local storage' policy you set?
After all, Apple is switching to Intel... ;)
Assuming you have a list of machines...
while read machine
do
ssh $machine apt-get install program
done
Doesn't that precicely describe Nvidia's graphics driver? A GPL'd stub that wraps a huge proprietry blob of code?
Strangely that one doesn't work. Perhaps '1' has some other function in a palette window.
Why so rude? I wish Slashdot didn't allow anonymous posts. Then I could killfile people like you.
This has been fixed for some time. Keyboard shortcuts work even when palette windows have the focus. The fact that they steal the focus at all is now merely cosmetic--if the colour of the windows' title bars didn't change then I wouldn't be able to tell the difference.
Pressing tab here hides all palettes (Gimp 2.2.8).
http://fuckinggoogleit.com/search?q=xnest+export+d isplay
The last few versions of the Gimp have really improved.
No longer does every palette count as a separate window in the Alt-Tab list/window list.
Clicking on a palette no longer steals the focus from the document window*. This used to drive me insane.
The visibility of palettes can be toggled by pressing Tab.
Raising a document window now even raises the palettes along with it!
The one thing I find missing is a way to maximise the amount of space a document window takes up, without making it so large that parts of it are obscured by the palettes.
As much as I hate MDI, I have to admit that being able to maximise a subwindow, having previously docked the palettes into the main window is very handy. Likewise, on the Mac OS, the window manager knows to avoid overlaying a window on palettes or the dock when hitting 'the green button'.
So, all I want is for the Gimp to borrow this behaviour from the Mac OS. Have it avoid my palettes when maximising windows. The 'correct' place to implement this is probably even in Metacity. I don't really care who gets it fixed, but once it is, I will no longer have cause to complain about the Gimp's UI.
Actually, if we are going to be pedantic pricks, then the package to install is 'xnest'. There is no 'Xnest' package.
Arcane XML or registry syntax? Have you even heard of gconf-editor?
It seems that the easiest way to solve that bug would be to prevent windows from opening that don't have a menu bar/address bar/button bar/status bar.
So don't do it. When you bring X11 to the front, all the Gimp windows come with it...
$ whatis Xnest ...] or export -p
:1 indicates the nested X display created in the previous command.
Xnest (1x) - a nested X server
$ help export
export: export [-nf] [name[=value]
NAMEs are marked for automatic export to the environment of
subsequently executed commands. If the -f option is given,
the NAMEs refer to functions. If no NAMEs are given, or if `-p'
is given, a list of all names that are exported in this shell is
printed. An argument of `-n' says to remove the export property
from subsequent NAMEs. An argument of `--' disables further option
processing.
$ whatis metacity
metacity (1) - minimal GTK2 Window Manager
$ whatis gimp
gimp (1) - an image manipulation and paint program.
Xnest is from XFree86/Xorg. It creates a new X display as a client of another X display.
The DISPLAY environment variable tells an X client which display to connect to. Here,
metacity is the default window manager for the Gnome desktop. I chose it because I assume it is what most Gimp users use.
I expect it didn't work on your Mac OS X machine because you don't have XFree86/Xorg. Being on a Mac OS machine, you don't really need MDI since the Mac's window management scheme makes it easy to raise all the windows of an application at once, and to hide all the windows from another application. IIRC it's under "$Application -> Hide others".
HTH HAND
xnest -- :1
export DISPLAY=:0
metacity &
gimp
There you go.
Nah, it's just Darwin at work... ex post facto.
I think his point was that, even though you detest rebooting into Windows to play your game, you still bought the game.
Their thinking is that the number of people who run Linux and who want to play a non-free game like WoW and who are not prepared to dual-boot to do so, multiplied by the typical revenue from a subscriber over the course of his subscription is less than the cost of developing and maintaining a Linux port of the game.
So why should Blizzard spend $lots on developing a Linux client when most of the potential market for the port already pay for the Windows port, and boot into Windows/run it via Wine?
Don't make me laugh. The virtual desktop power toy is shit.
It's in Microsoft's best interests to make PDFs difficult to use. They would rather you used their competing Metro technology, which will 'just work'.
I think the idea is to standardise what is already common practice. The LSB people could have sat down and codified everything according to How It Should Be -- but no one would have used it.
From Virtual Entity of Relevant Acronyms (Version 1.9, June 2002) [vera]:
MUX
MUltipleXer
Oops, I just realised that "legact" == "legacy". Never mind. :)
So they aren't supporting TLS? :(
But if they used Jabber, then all the messy stuff--the gateways to other IM networks--run on Google's Jabber servers. If Microsoft started blocking them then as soon as the hackers at Google worked out how to bypass the block, the MSN transport could be brought back up.
From a user's poing of view, contacts on other networks would be no different from Jabber contacts: abc@talk.google.com, fred_bloggs223%hotmail.com@msn.talk.google.com, 1324354@icq.talk.google.com, etc.
Wow, I knew that the Flash settings UI was badly designed, confusing and annoying to use. I didn't know that it set up tracking with partner sites as well.
Besides, what steps does Flash take to ensure that any old web site can't just reset these permissions, or except itself to the 'no local storage' policy you set?
Don't bother visiting Macromedia's site at all:
find / -name libflashplayer.so -o -name libflashplayer.xpt -exec rm {} \;
If you really can't live without it, try this instead:
chmod --recursive 500 ~/.macromedia
Making idiot PHBs of marketing companies burn their money investigating this new technology seems like a good idea to me.