GAP is useful is you do not want to paint each and every frame of an animation yourself. You can create path animations (a layer is move along a path), and do transforms at the same time.
The disadvantage: GAP is maintained by one author and totally tailored to his needs. Some parts of it seem to be illogical to other people. In order to change this, it needs more contributors. This doesn't neccessarily imply coding - building it, using it, documenting it as equally important.
This is something I wondered about during the past months, too.
Are ways to guarantee identification, authentication and authorization of a signal's sender even implemented in satellites, or does everyone rely on the fact that no one except the owners does (did) have the equipment to transmit to them?
Will we soon see global transmissions of messages like "This is a message to all American infidels. You will be punished for your decadent ways on the first day of Radaman."?
Re:Will anyone gain anything from this? Not Linux
on
The End is Nigh for XP
·
· Score: 2, Interesting
net stop wuauserv
This does stop the Automatic Updates service and thus gets rid of the dialog. Then it's your responsibility to remember that your system does require a restart.
In XP Pro, you can disable this dialog via a group policy, try googling for the exact value.
Re:Distribution on Windows
on
Why Use GTK+?
·
· Score: 1
I for one are quite happy with the look of GTK+ apps on Windows (I rely more on consistency per application than per platform, though), and I also run GTK+ without the MS theme engine on my own systems.
Some differences might be caused by the fact that a GTK+-based GUI is likely to be based on the GNOME HIG.
Re:Distribution on Windows
on
Why Use GTK+?
·
· Score: 1
Size isn't something that bothers many users nowadays. In the past, some have been bothered by the fact that GIMP and GTK+ installers are separate packages. This division is somewhat natural - GTK+ can and is used by other programs as well. Windows' lack of a package management system bites, though, so the current GIMP 2.3 installers come with the ability to detect the possible lack of GTK+ (this was already present in previous versions, in fact) and to download it directly from Sourceforge if needed.
Currently, an important reason for not integrating the GTK+ into the GIMP installer is emerging:
Seems like more current version of GTK+ (>= 2.8.0, as far as I can tell) don't work with Win98 anymore. So, if it was bundled, users on this platform would suddenly not be able to use GIMP anymore. With individual packages, they can pick the 2.6 which works, while users of Win2k or XP can choose the more advanced 2.8.
I always found GTK+ to be much faster on Win32 than on other platforms. For the look, there is a theme engine (MSEngine afaik, formerly known as gtk-wimp).
The feel is probably the only part where noticeable differences can still be found, in particular with the file chooser. Not the fact that there is no file entry, but e.g. the (non-)handling of UNC paths (got some fixes recently) and problems with.lnk files ("symlinks" on Win32).
Please note that Cinepaint is the continuation of GIMP's HOLLYWOOD branch, which was branched off in the GIMP 1.0 times - so some users might recognize its interface as somewhat familiar.
In steps 5 and 6, you should have been told about Xnest and Deweirdyfier. And I haven't yet seen a user with a comment like "I use Deweirdifyier, and it has the following things I'd like to see improved", so your assumption might be wrong.
Your remarks to the limited time... may I quote from your last paragraph? "I don't have the time."
Your ranting about the scripting interfaces... well, they are an example for features that went in by the "someone needed it and made it happen" principle. Note that except two of the interfaces - Scheme and Python - these aren't maintained in the GIMP source tree. BTW, afaik there are at least 6 interfaces, though one is going to replace the current Scheme one and two are no longer maintained. The plug-in and extension mechanisms make this possible, and you surely don't want to forbid anyone creating plug-ins, do you?
Aout the patches - if you'd change the UI with one large patch, you would do something wrong. GIMP is modular, so this can be changed one by one - which would be important, otherwise you could seriously delay the development of other features. Smaller patches are more easily reviewed, too.
My fucking eyes are open, and I see people who don't like the current interface and people who do like it. As people rather complain about things they don't like, and don't care to write about things they like (mentioned in another comment in this thread), I tend to weigh those opinions with different scales.
However, any changes to the UI have to consider the people who like the current interface. Comments concerning this are found in the bug tracking system at bugzilla.gnome.org, and anyone who is seriously interested in changing anything should read the relevant bug reports there and use the mailing list archives - and show that he has done so in any discussions he takes part in.
The problem with suggestions of changing this is usually that the one who suggests it declares that the current interface sucks and demands it to be changed "now and forever".
Coming to a mailing list or irc channel of a project with this attitude doesn't make you many friends. At least, you should listen to the regulars and accept why the UI is as it is, what tools are there to changed the behaviour (Xnest and Deweirdyfier were already mentioned).
And about the ignoring - the developer's time is limited. And it is unlikely that the main developers will create a seperate UI for a signle one platform. Here's the chance for new developers (and that's the group the "Fix it yourself"s are directed at) to implement new ways for an UI. Of course, changes have to be reasonable - the 12345kB "Hey, I changed the whole UI" patch will be rejected, as will any big changes that should be done on the GTK+ level (and much UI stuff probably should be done or at least prepared there). Again, listen to the regulars.
OpenSource Software is, at least partly, made by the people who create it for the people who create it. If you want it to be made (more) for you, consider becoming part of the people who create it - "create" isn't limited to "coding".
For some software, there are multiple distributions on Windows, or merely multiple distributors (check all those Ebay auctions seeling the "MS Office replacements" etc...).
What happens if one of these includes spyware? Will the whole program be delisted, or will the offending ditros be identified individually?
Well, there are some situations where this doesn't work - when selectiong a directory for patterns, brushes etc, or loading a gluas script, or...
GTK+ 2.6.0 comes with type-ahead search turned on, so in future releases of GIMP that are based on this version of it, the missing file entry will be a non-issue.
Slashdot Mirror
I'm shocked to read that NASA does use obsolete technology to illustrate science. They should be using CFLs in their examples.
GAP is useful is you do not want to paint each and every frame of an animation yourself. You can create path animations (a layer is move along a path), and do transforms at the same time.
The disadvantage: GAP is maintained by one author and totally tailored to his needs. Some parts of it seem to be illogical to other people. In order to change this, it needs more contributors. This doesn't neccessarily imply coding - building it, using it, documenting it as equally important.
This is something I wondered about during the past months, too.
Are ways to guarantee identification, authentication and authorization of a signal's sender even implemented in satellites, or does everyone rely on the fact that no one except the owners does (did) have the equipment to transmit to them?
Will we soon see global transmissions of messages like "This is a message to all American infidels. You will be punished for your decadent ways on the first day of Radaman."?
net stop wuauserv
This does stop the Automatic Updates service and thus gets rid of the dialog. Then it's your responsibility to remember that your system does require a restart.
In XP Pro, you can disable this dialog via a group policy, try googling for the exact value.
I for one are quite happy with the look of GTK+ apps on Windows (I rely more on consistency per application than per platform, though), and I also run GTK+ without the MS theme engine on my own systems.
Some differences might be caused by the fact that a GTK+-based GUI is likely to be based on the GNOME HIG.
Size isn't something that bothers many users nowadays. In the past, some have been bothered by the fact that GIMP and GTK+ installers are separate packages. This division is somewhat natural - GTK+ can and is used by other programs as well. Windows' lack of a package management system bites, though, so the current GIMP 2.3 installers come with the ability to detect the possible lack of GTK+ (this was already present in previous versions, in fact) and to download it directly from Sourceforge if needed.
Currently, an important reason for not integrating the GTK+ into the GIMP installer is emerging:
Seems like more current version of GTK+ (>= 2.8.0, as far as I can tell) don't work with Win98 anymore. So, if it was bundled, users on this platform would suddenly not be able to use GIMP anymore. With individual packages, they can pick the 2.6 which works, while users of Win2k or XP can choose the more advanced 2.8.
Which are the operations that violate this principle?
Maybe they discovered that Open Source is more than Linux and that narrow-mindedness isn't limited to the Microsoft World?
One by one, Microsoft Windows is taken away from Microsoft this way, and that's a good thing.
There shouldn't be a problem with distributing the official build free of charge - if the license for the source is completely GPL, that is.
I always found GTK+ to be much faster on Win32 than on other platforms. For the look, there is a theme engine (MSEngine afaik, formerly known as gtk-wimp).
.lnk files ("symlinks" on Win32).
The feel is probably the only part where noticeable differences can still be found, in particular with the file chooser. Not the fact that there is no file entry, but e.g. the (non-)handling of UNC paths (got some fixes recently) and problems with
Please note that Cinepaint is the continuation of GIMP's HOLLYWOOD branch, which was branched off in the GIMP 1.0 times - so some users might recognize its interface as somewhat familiar.
In steps 5 and 6, you should have been told about Xnest and Deweirdyfier. And I haven't yet seen a user with a comment like "I use Deweirdifyier, and it has the following things I'd like to see improved", so your assumption might be wrong.
Your remarks to the limited time... may I quote from your last paragraph? "I don't have the time."
Your ranting about the scripting interfaces... well, they are an example for features that went in by the "someone needed it and made it happen" principle. Note that except two of the interfaces - Scheme and Python - these aren't maintained in the GIMP source tree. BTW, afaik there are at least 6 interfaces, though one is going to replace the current Scheme one and two are no longer maintained. The plug-in and extension mechanisms make this possible, and you surely don't want to forbid anyone creating plug-ins, do you?
Aout the patches - if you'd change the UI with one large patch, you would do something wrong. GIMP is modular, so this can be changed one by one - which would be important, otherwise you could seriously delay the development of other features. Smaller patches are more easily reviewed, too.
My fucking eyes are open, and I see people who don't like the current interface and people who do like it. As people rather complain about things they don't like, and don't care to write about things they like (mentioned in another comment in this thread), I tend to weigh those opinions with different scales.
However, any changes to the UI have to consider the people who like the current interface. Comments concerning this are found in the bug tracking system at bugzilla.gnome.org, and anyone who is seriously interested in changing anything should read the relevant bug reports there and use the mailing list archives - and show that he has done so in any discussions he takes part in.
The problem with suggestions of changing this is usually that the one who suggests it declares that the current interface sucks and demands it to be changed "now and forever".
Coming to a mailing list or irc channel of a project with this attitude doesn't make you many friends. At least, you should listen to the regulars and accept why the UI is as it is, what tools are there to changed the behaviour (Xnest and Deweirdyfier were already mentioned).
And about the ignoring - the developer's time is limited. And it is unlikely that the main developers will create a seperate UI for a signle one platform. Here's the chance for new developers (and that's the group the "Fix it yourself"s are directed at) to implement new ways for an UI. Of course, changes have to be reasonable - the 12345kB "Hey, I changed the whole UI" patch will be rejected, as will any big changes that should be done on the GTK+ level (and much UI stuff probably should be done or at least prepared there). Again, listen to the regulars.
OpenSource Software is, at least partly, made by the people who create it for the people who create it. If you want it to be made (more) for you, consider becoming part of the people who create it - "create" isn't limited to "coding".
For some software, there are multiple distributions on Windows, or merely multiple distributors (check all those Ebay auctions seeling the "MS Office replacements" etc...).
What happens if one of these includes spyware? Will the whole program be delisted, or will the offending ditros be identified individually?
The previous splash was heavily criticized as being "for/from an vector app" rather than an image manipulation program.
1) Help the GTK+ maintainers to make it independent of X11
2) Get GIMP from another source than MacGIMP.com
So life forms you don't know (or do you dare to declare Wilber and Wilma to be members of any existing species) are automatically animals for you?
http://sourceforge.net/projects/gimp-win
WARNING! The Windows torrent is for GIMP 2.2-pre2, which is not GIMP 2.2.0.
"Brightness and Contrast" is a tool - and you can select the visible tools now (File->Dialogs->Tools).
Actually, it involves a font - watch the layers dialog when starting to move the selection.
Well, there are some situations where this doesn't work - when selectiong a directory for patterns, brushes etc, or loading a gluas script, or...
GTK+ 2.6.0 comes with type-ahead search turned on, so in future releases of GIMP that are based on this version of it, the missing file entry will be a non-issue.
Did you try it with a recent GTK+ installer (currently GTK+ 2.4.14)?
An advice for Gentoo users:
Learn about USE flags and how to use them. Will become useful when trying to figure out why some things are missing from your GIMP.