Re: [Gimp-developer] the Gimp lcms.c plug-in
On 07/25/2012 05:25 AM, Elle Stone wrote: It always surprises me how few people are working on a project as big, important, and widely used as Gimp. I'd love to work on it, but I can't keep up with the starting point :-) ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
On Wed, 2012-07-25 at 21:53 +0530, Skand Hurkat wrote: > > very good idea. > Not just inkscape, but I believe that Emacs, Vim and other text editors > also create a backup file. AFAIK, the backup file is autosaved, and the > original is kept as is, in case the user wishes to throw away all changes. Some editors keep what in effect is the undo stack, i.e. just the operations - loading a saved file can take longer, but you don't use a gigabyte on copying a file you might not need. So I think with the GEGL graph we might be able to see this in GIMP, without having to save scads of data to disk. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml Co-author, 5th edition of Beginning XML, Wrox, 2012 ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] the Gimp lcms.c plug-in
On Wed, Jul 25, 2012 at 4:25 PM, Elle Stone wrote: > On a related note, I reported a bug back in 2010: > https://bugzilla.gnome.org/show_bug.cgi?id=620781 (I changed my > website domain, the link I gave in the bug report is no longer > available). That bug still persists in Gimp 2.8/2.9 if the sRGB to > which one is converting to, starting with a linear gamma image, is > "sRGB built-in". However, using my lcms.c plugin using lcms2.h, that > bug disappears. I need to do some more testing, but there is a more > subtle bug, also involving conversions to and from a linear gamma > color space, that also seems to no longer be a problem when using my > lcms2 plug-in. By the way, there is a recent change that you probably want to be aware of, in case the next update of LCMS v2.x is soon. https://github.com/mm2/Little-CMS/commit/8b13ad6a80ce0f2e19301083c4313988ae0f8c38 Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
On Wed, Jul 25, 2012 at 9:19 PM, Richard Gitschlag wrote: > Not when you're trying to get it running in a Windows environment > (non-native to FF) and don't necessarily have 4-5 years of experience to > compare it to. In my experience, most crashes were related not to > memory/cpu intensive tasks but simple trivial stuff like navigating its > Glyph Outline editor by mouse and click/dragging nodes and handles. Simply put, running FontForge on WIndows is godawful and should be punished by excommunication :) Speaking of Windows, gimp.org just got updated. Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
On Wed, Jul 25, 2012 at 1:06 PM, Guillermo Espertino (Gez) wrote: > On 25/07/12 07:44, wanderer wrote: >> >> Well, as an user who read the list it came to my mind the implementation >> of auto-save in Gimp. > > Keep in mind that it could not be as trivial as it sounds. Image files > processed in GIMP can be really big, and probably the penalty in performance > and diskspace of having constant backups is too much. +1 to that! I routinely work on files that are >100MB and backing them up takes times... I want it to happen when I want it. Which is why I wrote a backup script http://registry.gimp.org/node/14246 and just tap Alt+F, B when I want to snapshot a backup. -Rob A> ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
Date: Wed, 25 Jul 2012 21:13:10 +0400 From: alexandre.prokoud...@gmail.com To: gimp-developer-list@gnome.org Subject: Re: [Gimp-developer] Update and apology On Wed, Jul 25, 2012 at 8:33 PM, Richard Gitschlag wrote: FontForge crashes. A lot. So much that the program makes an autosave of your open project every 60 seconds or so. Consider yourself lucky if you open a FF project file and DON'T get a message asking whether to restore your previous session. :) It's not every day that you get a message from dawn of times so well preserved. Did someone just break into a sealed tomb with FontForge bugreport scrolls from 2003? :) FF got a lot more stable in last 4-5 years. Not when you're trying to get it running in a Windows environment (non-native to FF) and don't necessarily have 4-5 years of experience to compare it to. In my experience, most crashes were related not to memory/cpu intensive tasks but simple trivial stuff like navigating its Glyph Outline editor by mouse and click/dragging nodes and handles. -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
On Wed, Jul 25, 2012 at 8:33 PM, Richard Gitschlag wrote: > FontForge crashes. > > A lot. > > So much that the program makes an autosave of your open project every 60 > seconds or so. Consider yourself lucky if you open a FF project file and > DON'T get a message asking whether to restore your previous session. :) > It's not every day that you get a message from dawn of times so well preserved. Did someone just break into a sealed tomb with FontForge bugreport scrolls from 2003? :) FF got a lot more stable in last 4-5 years. Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
On 25/07/12 07:44, wanderer wrote: Well, as an user who read the list it came to my mind the implementation of auto-save in Gimp. I guess you already had that discussion, but I think that a good software is the one that understand that us, mere mortals human beings, make a lot of mistakes and try in some manner to reduce the range of these mistakes. Keep in mind that it could not be as trivial as it sounds. Image files processed in GIMP can be really big, and probably the penalty in performance and diskspace of having constant backups is too much. Probably it's better to wait until GIMP gains a non-destructive workflow, where storing copies of the internal GEGL tree seems more feasible than duplicating large files all the time. Gez ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
Date: Tue, 24 Jul 2012 09:33:22 -0700 From: artfoundr...@yahoo.com To: gimp-developer-list@gnome.org Subject: [Gimp-developer] Update and apology Yesterday, I wrote a letter out of frustration in regards to GIMP. Sending emails borne of frustration is like driving yourself home after having too many drinks. Now on the subject of GIMP stability in general, have you ever tried using FontForge? FontForge crashes. A lot. So much that the program makes an autosave of your open project every 60 seconds or so. Consider yourself lucky if you open a FF project file and DON'T get a message asking whether to restore your previous session. :) -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
On 25-07-2012 16:14, wanderer wrote: Well, as an user who read the list it came to my mind the implementation of auto-save in Gimp. I guess you already had that discussion, but I think that a good software is the one that understand that us, mere mortals human beings, make a lot of mistakes and try in some manner to reduce the range of these mistakes. This is an interesting point. I've recently trying out Lightworks for video editing, and I like the fact that it does not have "save" in it's workflow. Rather, it just saves every operation. I know that inkscape tries to write a backup file whenever he crashes, and it display a message to the user, whenever is possible, saying where the file is. I don't know if gimp does that, but /i think it's a very good idea. Not just inkscape, but I believe that Emacs, Vim and other text editors also create a backup file. AFAIK, the backup file is autosaved, and the original is kept as is, in case the user wishes to throw away all changes. Also, there are softwares like blender wich gives the option of saving incremental files (like file0001.tga, file0002.tga...). Mine's a strange mind; I think that implementing this option is more useful in a way that it suggests to user "hey, it's a good idea to have incremental backups" than the feature itself. It's like a suggestion of workflow. Incremental backups with .xcf files? In my workflow, each .xcf photograph ends up orders of magnitude larger than the DNG files that make up the photograph (with the many layers that get added in the workflow). Not sure if I'd like incremental backups :) Also, an autosave wich can be configured would be a good idea. It would be interesting if the number of backup files could also be set... So, if I choose to have only one backup file, every x minutes gimp writes the same file with the backup. I've used a program that does that. I always used it in one, so I don't really know the behaviour with more files... Well, these are just suggestions of a humble user :) Em 24-07-2012 15:31, s...@piments.com escreveu: On 24/07/12 18:33, Akira Tanaka wrote: Yesterday, I wrote a letter out of frustration in regards to GIMP. I feel that my actions were juvenile, immature and socially unacceptable. I haven't bothered to update the software and in a fit of misguided and dumb rage, I unleashed that attack against those who did not deserve it. I'm not a victim, I just made a foolish mistake out of anger. And for that I apologize. I meant no disrespect to any of you and I'm pretty sure I'd give GIMP another chance with its newest version. So please disregard everything that was said in "a letter of complaint." Well that seems an honest , full and sincere apology. If I'd felt I was the target I'd be satisfied. Anyone who can eat that much humble pie in one helping deserves to be excused. Though it was clearly out of order, it was so outrageous I think it caused more amusement than anything else. We don't get much comic relief on gimp-developer. You brightened my day and for that I thank you. If you can identify a serious bug, there's a good chance it will get fixed because bugs should be fixed. It's not a case of whether the reporter "deserves help" , the code base deserve help. If you can define a reproducible problem please report it. Best regards, gg. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] A letter of complaint
On 12-07-23 04:22 PM, Michael Henning wrote:
I suppose you've never used Windows ME
**shudder**
Just typing the name brings back memories.
I used to use it a long time ago. I don't understand why some people say
it's one of the worst versions of Windows. I always found ME to be at least
as reliable/stable as the previous version I was using ('98?) if not more
so. It never gave me any grief.
--
Cheers!
Kevin.
http://www.ve3syb.ca/ |"Nerds make the shiny things that distract
Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're
| powerful!"
#include | --Chris Hardwick
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] the Gimp lcms.c plug-in
>So please, just go ahead, look at the patches in bugzilla, pick the >best stuff from your patches and the bugzilla ones, and all will be >fine. OK, I'm working on it. And I promise to keep communicating actively. I'm making two Gimp from git installations, one for the existing lcms2 patches (thank you! Michael Schumacher, for pointing the two patches out to me) and one for the lcms2 code that I'm writing. On a related note, I reported a bug back in 2010: https://bugzilla.gnome.org/show_bug.cgi?id=620781 (I changed my website domain, the link I gave in the bug report is no longer available). That bug still persists in Gimp 2.8/2.9 if the sRGB to which one is converting to, starting with a linear gamma image, is "sRGB built-in". However, using my lcms.c plugin using lcms2.h, that bug disappears. I need to do some more testing, but there is a more subtle bug, also involving conversions to and from a linear gamma color space, that also seems to no longer be a problem when using my lcms2 plug-in. >We are short on >resources, and naturally active community members are harder to >forget, as opposed to patches sitting in bugzilla. It always surprises me how few people are working on a project as big, important, and widely used as Gimp. -- http://ninedegreesbelow.com Articles and tutorials on open source digital imaging and photography ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
Well, as an user who read the list it came to my mind the implementation of auto-save in Gimp. I guess you already had that discussion, but I think that a good software is the one that understand that us, mere mortals human beings, make a lot of mistakes and try in some manner to reduce the range of these mistakes. I know that inkscape tries to write a backup file whenever he crashes, and it display a message to the user, whenever is possible, saying where the file is. I don't know if gimp does that, but /i think it's a very good idea. Also, there are softwares like blender wich gives the option of saving incremental files (like file0001.tga, file0002.tga...). Mine's a strange mind; I think that implementing this option is more useful in a way that it suggests to user "hey, it's a good idea to have incremental backups" than the feature itself. It's like a suggestion of workflow. Also, an autosave wich can be configured would be a good idea. It would be interesting if the number of backup files could also be set... So, if I choose to have only one backup file, every x minutes gimp writes the same file with the backup. I've used a program that does that. I always used it in one, so I don't really know the behaviour with more files... Well, these are just suggestions of a humble user :) Em 24-07-2012 15:31, s...@piments.com escreveu: On 24/07/12 18:33, Akira Tanaka wrote: Yesterday, I wrote a letter out of frustration in regards to GIMP. I feel that my actions were juvenile, immature and socially unacceptable. I haven't bothered to update the software and in a fit of misguided and dumb rage, I unleashed that attack against those who did not deserve it. I'm not a victim, I just made a foolish mistake out of anger. And for that I apologize. I meant no disrespect to any of you and I'm pretty sure I'd give GIMP another chance with its newest version. So please disregard everything that was said in "a letter of complaint." Well that seems an honest , full and sincere apology. If I'd felt I was the target I'd be satisfied. Anyone who can eat that much humble pie in one helping deserves to be excused. Though it was clearly out of order, it was so outrageous I think it caused more amusement than anything else. We don't get much comic relief on gimp-developer. You brightened my day and for that I thank you. If you can identify a serious bug, there's a good chance it will get fixed because bugs should be fixed. It's not a case of whether the reporter "deserves help" , the code base deserve help. If you can define a reproducible problem please report it. Best regards, gg. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Gimp UI ... hesitant about compiling a list...
RMMjr gmail.com> writes: > > I caught this e-mail address on someone's signature line in a post... > Well you're certainly a verbose one... I'll be brief though: What you think are UI issues are actually code issues. The boundaries and floating layers are not there by choice exactly. there is an intention to get rid of them, but there are not many developers on this project and things simply take a long time. If you are a developer you might want to join and help. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] the Gimp lcms.c plug-in
On Tue, 2012-07-24 at 17:37 -0400, Elle Stone wrote: > Perhaps what I really should be asking is what is the process by which > an existing patch to the Gimp code is applied so that everyone can use > it? Your way of doing patches *and* actively communicating is the only way that will guarantee your patches to land. We are short on resources, and naturally active community members are harder to forget, as opposed to patches sitting in bugzilla. So please, just go ahead, look at the patches in bugzilla, pick the best stuff from your patches and the bugzilla ones, and all will be fine. > In particular, by what process does Gimp get patched to use lcms2? ( I > kinda doubt that the Gimp developers are going to let Elle Stone patch > Gimp, as the chances are very great that Elle Stone would break Gimp > in the process.) Breaking gimp at least once is part of the initiation ceremony, don't worry ;) > I don't need to patch my own copy of Gimp. It's already using lcms2. > > On 7/24/12, Michael Schumacher wrote: > > On 24.07.2012 23:16, Elle Stone wrote: > > > >> How does one apply a patch? What does "apply a patch" mean? > > > > You use the patch program to apply the changes that are contained in the > > attachments to the bug report to the GIMP code. > > > > The usage example from the Wikipedia article about patch should do: > > http://en.wikipedia.org/wiki/Patch_%28Unix%29 > > > > patch < foo.diff > > > > This could be executed in the top directory of your GIMP source tree. > > > > There are parameters to adjust for differences in the diff files > > regarding both your and the patch author's systems, see > > http://linux.die.net/man/1/patch - -p is the most commonly used > > parameter to get rid of leading folders in the paths used in the diff > > file, for example. > > > > > > -- > > HTH, > > Michael > > ___ > > gimp-developer-list mailing list > > gimp-developer-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > > > ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Update and apology
mr. Tanaka, I use GIMP since the year 2000 Maybe I can help you to identify some key points in your "crash experience" I've used GIMP for almost every artwork I've done along Photoshop - just because some things goes faster (not as computing speed) but as operation logic ( workflow if you like ...) and for me those crashes your talk about ...they are a wonder for me. For me GIMP 2.X until 2.7 was extremely stable under Windows or Linux. I remember one time - in less than 24 hours I must prepare a 5.5m x 3.5m poster for a factory expecting a visit from an international customer. The computer was prepared for web design not for prepress and large scale graphics. I can open all images from their list in Photoshop but I can't save the work because ...insufficient memory. Then for almost any layer movement Photoshop put me to wait long time when not just crashed. GIMP (2.4 if I remember well) just save my day because printing factory called me every 5 minutes. Until Photoshop CS4 for also, important operations like "liquid rescale" and "content aware fill in PS" (aka "heal selection" on GIMP) was only possible in GIMP (and some small demonstrative programs). But for prepress I was forced to use Photoshop under Windows and Linux. Regarding so many crashes something must go wrong with the hardware - GIMP use a quite modular plugin system - so many custom plugins will crash without affecting the application. Send me a separate message with your problems one by one - so we can solve things out of this mailing list. I have a lot of GIMP plugins, themes, and some good experience, probably I can help you to earn some time... Other readers of this list may help you also - if you can express very clear what you need. If you can speak clear, it's almost improbable that one or another will not throw a helping hand. BTW - please don't hate me for analogy with An American in Rome, is an italian movie from 1954, I am sure you will like this movie too ;). 2012/7/25 : > On 24/07/12 18:33, Akira Tanaka wrote: >> >> Yesterday, I wrote a letter out of frustration in regards to GIMP. I >> feel that my actions were juvenile, immature and socially unacceptable. >> I haven't bothered to update the software and in a fit of misguided and >> dumb rage, I unleashed that attack against those who did not deserve it. >> I'm not a victim, I just made a foolish mistake out of anger. And for >> that I apologize. I meant no disrespect to any of you and I'm pretty >> sure I'd give GIMP another chance with its newest version. So please >> disregard everything that was said in "a letter of complaint." > > > Well that seems an honest , full and sincere apology. If I'd felt I was the > target I'd be satisfied. Anyone who can eat that much humble pie in one > helping deserves to be excused. > > Though it was clearly out of order, it was so outrageous I think it caused > more amusement than anything else. > > We don't get much comic relief on gimp-developer. You brightened my day and > for that I thank you. > > If you can identify a serious bug, there's a good chance it will get fixed > because bugs should be fixed. It's not a case of whether the reporter > "deserves help" , the code base deserve help. > > If you can define a reproducible problem please report it. > > Best regards, > > gg. > > ___ > gimp-developer-list mailing list > gimp-developer-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gimp-developer-list -- Nemes Ioan Sorin ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
