Re: [Gimp-developer] GIMP Developer Meeting #4 + GSoC Mentor/Admin Meeting]
- Forwarded message from Mukund Sivaraman - Date: Mon, 18 Apr 2011 07:28:06 +0530 From: Mukund Sivaraman m...@mukund.org To: LightningIsMyName lightningismyn...@gmail.com Cc: gimp-developer gimp-developer@lists.xcf.berkeley.edu Subject: Re: [Gimp-developer] GIMP Developer Meeting #4 + GSoC Mentor/Admin Meeting User-Agent: Mutt/1.5.21 (2010-09-15) Hi LightningIsMyName On Sun, Apr 17, 2011 at 11:39:05PM +0300, LightningIsMyName wrote: Hello, The next GIMP Developer Meeting (#4) was scheduled for this week on tuesday, April 19th 2011 on 20:00 UTC. For time zone conversions, see http://www.timeanddate.com/worldclock/fixedtime.html?msg=GIMP+Developer+Meeting+%234iso=20110419T20 As usual, the meeting will take place on #gimp-devel Sorry, the scheduled time is not fine for me. I had asked for this to be changed on IRC, but nothing was done for the last meeting's time too. The previous meetings have happened at around 1:30 AM localtime and 2:00 AM localtime. As there's a rather large Pacific ocean, there must certainly be a suitable time for this meeting that doesn't occur during the middle of anyone's sleeping hours. :) Mukund - End forwarded message - pgpfZzrbQVBQF.pgp Description: PGP signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] porting gimp plugins to gegl operations
Shivani, I have asked you before not to mail me directly. All GIMP GSoC discussions have to be public. I am not your mentor yet, and may not mentor at all. Please send email to the gimp-developer list and not to me. Mukund On Tue, Apr 12, 2011 at 03:51:09AM -0700, shivani maheshwari wrote: Hello, Sorry for the late reply. I was out of town on so got to read the mail today. I'll look into the code again and do the needful as soon as possible. -- Shivani Maheshwari Under Graduation( BTech.) Indian Institute of Information Technology, Allahabad (Amethi Campus) India pgp33LG1CYiyp.pgp Description: PGP signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] [m...@mukund.org: GSoC registration]
- Forwarded message from Mukund Sivaraman m...@mukund.org - Date: Thu, 7 Apr 2011 19:05:38 +0530 From: Mukund Sivaraman m...@mukund.org To: Robert Sasu sasu.rob...@gmail.com, shivani maheshwari shivani.mah...@gmail.com, sourav de souravde1...@gmail.com Cc: gimp-developer@lists.xcf.berkeley.edu Subject: GSoC registration User-Agent: Mutt/1.5.21 (2010-09-15) Hi all All students who want to participate in GSoC should have applied by April 8 according to the timeline: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/faqs#timeline Some students for the plug-in porting task have sent what has been requested, so as far as the GIMP project is concerned, they've applied. But please also check on the Google SoC website to see if Google wants you to register an account and provide your student details. Tomorrow is the last day to apply! Mukund - End forwarded message - pgpMOKhm9DEO2.pgp Description: PGP signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] [m...@mukund.org: Re: Gimp Plugin semi-flatten ported to Gegl op.]
- Forwarded message from Mukund Sivaraman m...@mukund.org -
Date: Thu, 7 Apr 2011 17:42:23 +0530
From: Mukund Sivaraman m...@mukund.org
To: shivani maheshwari shivani.mah...@gmail.com
Cc: gimp-developer gimp-developer@lists.xcf.berkeley.edu
Subject: Re: [Gimp-developer] Gimp Plugin semi-flatten ported to Gegl op.
User-Agent: Mutt/1.5.21 (2010-09-15)
On Thu, Apr 07, 2011 at 05:29:59PM +0530, Mukund Sivaraman wrote:
On Thu, Apr 07, 2011 at 04:42:02PM +0530, shivani maheshwari wrote:
+ for (i=0; in_pixels; i++)
+{
+ out_pixel[0] = (in_pixel[0] * in_pixel[3]) / 255 + (in_pixel[0] *
(255-in_pixel[3])) / 255;
+ out_pixel[1] = (in_pixel[1] * in_pixel[3]) / 255 + (in_pixel[1] *
(255-in_pixel[3])) / 255;
+ out_pixel[2] = (in_pixel[2] * in_pixel[3]) / 255 + (in_pixel[2] *
(255-in_pixel[3])) / 255;
+ out_pixel[3] = (in_pixel[3] == 0) ? 0 : inpixel[3];
+ in_pixel += 4;
+ out_pixel += 4;
+}
+ return TRUE;
Did this code work for you? Did it semi-flatten the input?
Here's a tip. Try to understand GEGL's data formats. You can find some
information here:
http://gegl.org/babl/
Try to learn the colorspaces and also the ranges of the inputs and
outputs.
Most GIMP plug-ins will have to be *rewritten* for GEGL. You can adapt
code, but simply copying code without following it will not work.
Mukund
- End forwarded message -
pgpr0KVc8cfSP.pgp
Description: PGP signature
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gegl build fails
On Tue, Mar 29, 2011 at 09:21:28PM -0600, Michael J. Hammel wrote: The commands to build it were as follows: export LD_LIBRARY_PATH=/usr/local/gimpgit/lib:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=/usr/local/gimpgit/lib/pkgconfig/: export XDG_DATA_DIRS=/usr/local/gimpgit/share/ Mukund pgpnZyIiZlnia.pgp Description: PGP signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GSoC 2011 Porting GIMP plugins to GEGL operations
Hi Sourav On Tue, Mar 29, 2011 at 12:36:04AM +0530, sourav de wrote: Hi, I am a 2nd year student of the department of Computer Science and Engineering at Indian Institute of Technology, Kharagpur ,and I am interested in the plugin for cartoonization of an image in GIMP. I gather you want to modify the cartoon plug-in in GIMP? The plug-in porting task that you have mentioned in the subject is to directly port GIMP plug-ins to GEGL ops. No modification of functionality is necessary. It is described here: http://gimp-wiki.who.ee/index.php?title=Hacking:GSoC_2011/Ideas#Porting_GIMP_plugins_to_GEGL_operations It is not a task of porting only 1 plug-in, but about 6-10 plug-ins per student. 1 plug-in is a very easy task and will not be sufficiently long for a full summer's work. To apply for this task, please present the items mentioned on the linked wiki page. However, if you wish to modify the cartoon plug-in, that sounds interesting too. It can be a different task. Can you describe what is lacking in the current approach in the GIMP plug-in? What is the algorithm that you plan to use ? You say you are doing a project on algorithmic art.. have you published anything on the methods you wish to use in this cartoon plug-in? Are you using any other published works? Note that we _may_ accomodate more tasks if they are of a high quality and we are satisfied with how the student presents it. Mukund pgpXNNaS9ZY5s.pgp Description: PGP signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Wiki spam
Ulf-D. Ehlert wrote: Currently we are getting up to 20 spam pages every day. There is an Antispam subsystem (sometimes updating its BadContent page), but obviously it doesn't work: spammers can add new pages with links to websites listet in BadContent. The latest version of MoinMoin has a new anti-spam feature called text captchas which asks the user to solve a question before accepting a form. http://moinmo.in/TextCha Try editing that page and you can see it in action. An upgrade to the latest version will help cut a lot of this spam. Kind regards, Mukund ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Luis Luis A. Florit wrote: Please excuse me, Mukund, but I will be very surprised if this has something to do with broken EXIF data. As I'm yet to see the actual original image in question, speculating about what is wrong with it is pointless. Please attach the image to the bug and we'll have a look at it and find out what is going on. There is (well was) only one place where EXIF info was discarded in GIMP, and hence I suggested what the problem be, but we may not know until you attach your image first to a bug and show it to us. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
Hi Luis Luis A. Florit wrote: Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). Ah good. So there lies your problem :-) Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
Luis A. Florit wrote: Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). Observe that version libexif 0.6.15 has a delicate security bug that was only fixed in the last version 0.6.16 (2007-06-12). Btw I use Fedora 7 (RPM based) and we have 0.6.15 in it. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ./configure doesn't recognize libexif
Hi Richard On Thu, Jun 21, 2007 at 11:21:47AM +, Richard Hirner wrote: Hi, I tried to compile the latest GIMP version from the SVN trunk. My problem: the ./configure script (called from autogen.sh) doesn't recognize libexif although the libexif-dev and libexif-gtk-dev packages are installed and the headers and libs are indeed present: You need at least libexif 0.6.15. Kind regards, Mukund ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about carol
Hi Raphael Raphaël Quinet wrote: On Thu, 21 Jun 2007 12:51:50 + (UTC), Daniel Pisano [EMAIL PROTECTED] wrote: Mukund Sivaraman muks at mukund.org writes: If there are anyone who know her personally and are nearby, please get her medical attention. Yes, please. Her condition is serious. You both raised several valid points about Carol's unacceptable behavior. However, it would have been better to avoid stating on a public mailing list that she needs medical attention (regardless of whether it is true or not). These comments should have been private. They can easily be perceived as an insult and they weaken your other arguments because you are attacking her person instead of her behavior. I was not attacking at all. It was something I suggested for her own good, as a trained professional like a psychiatrist can understand her problems better and suggest activities which can make her feel better. This is clearly my personal opinion from observation. I should not have said she's insane as I have no real idea of what her medical condition is, or if she needs treatment, and I am not a doctor. I apologize for that comment, but it was really my opinion. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about carol
Hi Louis Louis Desjardins wrote: I did not intend to offend anybody here. If I did, I apologize in advance. You do not offend. You probably wrote this email with the best intentions, but you seem unaware of many things that have happened. I cannot discuss the reasons of each and everyone talking here in their personal name as I barely show up on IRC on the gimp channel. I believe each has good reasons to express what they feel regarding Carol's behavior. At the same time, I for one feel pretty unconfortable with where this discussion is heading now that it has deviated on medical diagnostic... and still being made public. I strongly believe the advice on Carol's condition is completely out of the purpose of this list — of any list, I should say. This is private matter. A public discussion on an archived list is not the same as a kitchen discussion with whoever about whatever or whoever. I am really unconfortable now and I believe I am not alone in this situation. Firstly this `medical help' criticism has gone way overboard. I did not reveal some secret file about Carol, or something that was actually diagnosed by a doctor who confided in me. My _opinion_ was from her public behaviour towards me and others in the IRC channel and emails. This opinion is not irrational or random, and I am entitled to say it having been publicly harassed and I have proof to back it up. When I say she should seek help, I say that out of sympathy. Almost every GIMP developer is aware of her eccentric behaviour and my email was written out of frustration, having read something that very day on IRC. It pretty much concerns this list, because developers will leave unless this topic is solved (there is a limit to tolerating harassment), and this thread was started by the maintainer of GIMP. This thread _is_ about Carol's behaviour. I suggest to stop this thread and refrain from commenting further on personnal things such as the health of somebody. At the same time, I think that once the heat will be down a few degrees, the case should be discussed among the team on a private channel and preferably including Carol so she can express herself or at least understand what is going on and if exclusion is voted, at the very least the accused person knows exaclty what are the reproaches made to her, from an official point of view, with objective rules that anyone can understand and agree upon. I guess that before getting this far, an official warning should take place. If nothing changes, then a final warning and then, the consequences of being banned from the various gimp channels or monitored or whatever measures the team decides. The incremental consequences of a specific bad behavior should be publicly known. The bad behavior should be clearly identified too, and described. These rules are necessary for any kind of human community. You seem to talk of ideal conditions, which haven't existed. Who is `official' exactly? Yosh? Sven? You and me? So far there have been disagreements, and complaints have gone unanswered, and I guess this thread was started out of frustration by Sven. You talk of these official methods---do you know of our complaints so far? Carol has been asked politely several times to leave the project, and has been explained the reasons for it which she is well aware of. Nobody is prejudiced here. If she is to change today completely and turn a new leaf, she will be welcome. But that seems very unlikely, going by how she doesn't seem to care. She had received her `final warning' several times from Sven. Discussions should be public. This is a public project, people were harassed in public on IRC. IMHO, the discussion should be public so that everyone including Carol knows what progressed, and we can all say what we have to say. The gimp officials have to discuss about the facts going on the gimp channels. Nothing less. Nothing more. And take action on these facts, leaving behind any further considerations and suppositions. This is exactly what was discussed. And when you have a person speaking like a nutcase in public, it's not entirely unexpected if someone calls him/her a nutcase. It's not a secret or some private data made public. Linus called the Subversion developers stupid in his Git talk and meant it, for just getting merging wrong. I am not exactly prejudiced as I think somewhere inside she is probably a good person, but I have sure been irritated by her (and it seems that that's continuing, considering what happened yesterday morning which was out of the blue having had her on /ignore for a long time). Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
On Wed, Jun 20, 2007 at 12:52:50PM +0530, Mukund wrote: On Wed, Jun 20, 2007 at 10:06:53AM +0300, Alexander Rabtchevich wrote: Haven't found in bugs and SVN changelog. GIMP 2.3.18 (Windows) deletes exif data from images. There is a similar bug on bugzilla.gnome.org filed against the GIMP component (it may have been closed recently). Please find the bug and attach your source image (original) to it. It may be that your image's EXIF data is invalid and missing tags required in various IFDs. Raphael has put a patch into GIMP trunk recently to work around this issue and you can try that and see if the EXIF data is still deleted. If you can't find the bug, please file a new bug with the image in question and reply to this thread with the bug number. Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Luis On Wed, Jun 20, 2007 at 09:01:16PM -0300, Luis A. Florit wrote: Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 In fact, this bug in 2.3.18 is not related (only) to Bibble. Yes, it's not limited to Bibble. That's a title stated by the reporter, but the bug encompasses the class of bugs where EXIF info is not saved when the EXIF info in the source image is broken (missing required tags). Various cameras/applications can make such images with faulty EXIF info. Raphael: Btw, even if we accept broken EXIF data, the EXIF data we write back should be fixed and valid. I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. I reported this issue a week ago to this list, but got no answer. First, do a check with GIMP trunk and see if the issue has been fixed. If not, please report your image (the original source image) at the same bug too. We'll take a look at it and if it's a different bug, then we'll file another one for it. Please mark the bug as reopened too when you attach the image. Kind regards, Mukund ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] about carol
Hi Sven Neumann wrote: We will have to do something about this situation. Or even more developers, including myself, will leave the project. As a start, I ask everyone who feels harrassed by Carol to tell her that she is not welcome and to ask her to leave. Perhaps then she realizes that this is not just a personal threat from me. I'd hate to do this to any other, but this situation has gone unchecked for a long time. Having been a target of her somehow scornful and insane behavior several times, I also ask for her removal, but more than that, I also think she's genuinely insane and needs to seek medical attention (seriously). She may not be doing all of this on purpose for fun, but maybe because she has mental issues. #gimp is not your average IRC room. Similar to other rooms on GimpNet, developers get together there and there's mutual respect. Among the things I remember: - She `attacks' people in the channel, such as this one time when she was annoyed with akk and she tried to drag me into the conversation --- I had just quit my job of 5 years and when I refused to participate in her attacks and wanted to be left alone, she points out my employment situation on IRC to tick me off and made me quit the channel. - She has claimed crazy things in channel to undermine me, such as that I wanted to marry a US citizen to get a H-1B visa. - She claimed in a nonsense `apology email' that GIMP project and #gimp are `homo-erotic love fests' due to something that a GIMP developer told her (I am not going to disclose that email here for it'd hurt that person). This was irritating to read as GIMP is not an erotic love fest, at least not to its contributors. She also claimed that this GIMP developer told her that we were all trying to get sexually involved with her. All this this shows her lack of respect towards her co-contributors. - I had tried to talk sense into her, tried to explain that nobody is out to get her or ill treat her in any way. We're just trying to run a project. But nothing works and she just replies with nonsense. Reasoning with her has no effect. - She does not speak rationally. In a lot of cases, it's simply nonsense which nobody can understand or a mockery of her co-developers. - If I'm not mistaken, bolsh (Dave Neary) left the GIMP project due to inaction on Carol's behaviour. - Even today she claimed something silly, that I had sent a person this morning into the channel to ask her about my authoring a plug-in, when I had had absolutely no communication with her in the recent past whatsoever. I have her on ignore nowadays, but her message got through because I was IRC'ing from a new place. If there are anyone who know her personally and are nearby, please get her medical attention. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] GIMP jpeg-exif issue (#377917)
Hi Bill Please take a look at: http://bugzilla.gnome.org/show_bug.cgi?id=377917 From svn blame, I found that you had put in the ExifVersion check in comment #4 (revision 16371). Is there a strong reason to have this? We do want to support incomplete EXIF information (even if it's broken). Does libexif return exif_data even though there's *absolutely no EXIF info* in the file? We may need to remove this check and also the check for thumbnails (in the statement preceding this if) to handle files with broken EXIF information gracefully. I'd appreciate your comments on this. How else can we check if the exif_data has any valid EXIF data, without checking for ExifVersion? Kind regards, Mukund -- Banu -- Free software for science, media and graphics http://www.banu.com/ signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] improving bicubic interpolation
Hi Sven and gg, Sven Neumann wrote: Hi, On Mon, 2007-01-22 at 10:13 +0100, [EMAIL PROTECTED] wrote: All references to Keys' work seem to lead to papers published by IEEE and available on a per article subscription. I assume the charge for one or two articles would be fairly nominal. Would this be a good use of some of the gimp projects donations fund? That sounds like very reasonable use of the money. Please try to find out which papers would be important for your work and how much is being charged for them. I am a member of IEEE Computer Society and will be glad to get and share the full text PDF of these articles for GIMP development use. Same with ACM papers. Kind regards, Mukund -- Banu -- Free software for science, media and graphics http://www.banu.com/ signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.4 showstoppers
[EMAIL PROTECTED] wrote: Ahh, I did not see what your previous comment meant. Caught out by this damn ML reply-to setting again. I'm subscribed to several lists which operate in a more logical way: I get a msg from the list , I hit reply in my email client and it replies to the list. Since the msg came from the ml not from your address the reply-to header is counter intuitive. It actually isn't. You may want to read this: http://www.unicom.com/pw/reply-to-harmful.html Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: More interface rantings
Hi Scott Scott wrote: And directory paths. Probably a gtk issue, but why? A case in point is the gtkam application, which has been updated to use the gtk stuff. In the previous version, I would always save my digicam photos to, eg, ~/photos/2006/10. And it would remember between instances, so I'd only have to worry about changing anything when the next month rolled around, and then the next year. Now, it defaults *every stupid time* to my home directory and I have to waste numerous key/mouse strokes to get to where I want to be. The Gimp has been similar in its forgetfullness forever. Again, a tool which will remember what I want it to do will be appreciated as a wise tool. Take a look at the way Gqview does directories. Then wonder why most users use it as a front-end to get their pictures into the gimp to edit. Then ponder why the gimp couldn't do that itself You can use bookmarks in the Open Image dialog to quickly flip to directories. Not that this is exactly what you want, but it's more convenient than having to browse to a particular directory from scratch. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] colormap-remap - colormap-rearrange
Hi Sven Sorry about bug #345251; not trying to clutter up bug reports. I have asked for it to be renamed to colormap-rearrange.c from the time the menu item's label was changed to Rearrange Colormap as it's more logical for a person to find it in the source tree. Kind regards, Mukund signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] colormap-remap - colormap-rearrange
Hi Sven On Sat, 2006-09-09 at 16:51 +0200, Sven Neumann wrote: Sorry about bug #345251; not trying to clutter up bug reports. I have asked for it to be renamed to colormap-rearrange.c from the time the menu item's label was changed to Rearrange Colormap as it's more logical for a person to find it in the source tree. That only holds true for the minority of users that are using GIMP in the english locale. As long as the procedure name matches the filename, I don't see a good reason to rename the plug-in. When you put it like that in plain words, it makes a lot of sense :-) Kind regards, Mukund signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] SoC: only two weeks left - hurry!
On Mon, 2006-08-07 at 22:31 +0200, Michael Schumacher wrote: Show it! Please add your code to Bugzilla and paste your URLs on IRC and on this developer mailing list! If your work has a UI, please upload screenshots on some public server and post links. If your work does some sort of image manipulation, post before and after images of its output. If your work generates files, please upload the files and describe them. Remember that the biggest part of your work (regardless of SoC) is passing public scrutiny. People who are looking forward to trying your work may request some changes to improve it. signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Building healthy community
On Fri, 2006-07-28 at 12:34 +0200, Dave Neary wrote: Hi, http://www.oreillynet.com/conferences/blog/2006/07/oscon_how_open_source_projects.html During OSCon, Ben Collins-Sussman and Brian Fitzpatrick of Subversion fame gave a talk which was apparently very interesting on how free software projects can survive poisonous people. There's lots of good advice in there, including: * Document your community, decisions and processes * Have healthy collaboration practices * Avoid names in source code - use revision history for documenting who did what, to avoid ownership of code/modules Anyway, it seems pertinent for the GIMP developers community, and perhaps a starting point for putting in place some better practices. I want to add a note about a friendly attitude. I was an early adopter of Subversion for office work and had to deal with its developers in its unstable days. I remember how gentle and friendly they were, especially Ben Collins-Sussman. I am talking from a user's perspective, but developers were also welcomed very well. I think GIMP is average on that scale. Sometimes everyone is very friendly, sometimes not so friendly. But then the Subversion developers were paid by Collab.net to be full-time employees working on it and hence this wasn't cutting into their free time, to cause any frustrations, etc. Lots of factors are behind why people appear to be dorks. Maybe a nagging wife or husband.. maybe an unsatisfactory life.. maybe very little time... maybe some medical condition which shows up as frustration. Sometimes we're unfriendly because the person we're dealing with is rude. I've noticed though that any developer who's trying to write something for GIMP is appreciated and helped. We can definitely be more friendlier. We certainly must try and not be rude to anyone. Also respect for co-developers and contributors means a LOT. If there's no respect, forget about succeeding. Mukund signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [PATCH] About dialog shows unstable status
On Thu, 2006-07-20 at 13:23 +0100, Mukund wrote: I have made the required changes (removed newlines; moved message into a label) except I kept the descriptive text. If you think it's a bad idea still, I'll remove it. Otherwise, if you are okay with the patch (attached), I'll commit it. http://www.mukund.org/temp/about-4.png Is this patch fine? Mukund signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [PATCH] About dialog shows unstable status
Hi Sven
I have made the required changes (removed newlines; moved message into a
label) except I kept the descriptive text. If you think it's a bad idea
still, I'll remove it. Otherwise, if you are okay with the patch
(attached), I'll commit it.
http://www.mukund.org/temp/about-4.png
Mukund
Index: about.h
===
RCS file: /cvs/gnome/gimp/app/about.h,v
retrieving revision 1.4
diff -u -p -r1.4 about.h
--- about.h 1 Mar 2006 08:06:08 - 1.4
+++ about.h 20 Jul 2006 12:21:55 -
@@ -26,6 +26,10 @@
#define GIMP_NAME \
_(GNU Image Manipulation Program)
+#define GIMP_DESCRIPTION \
+ _(GNU Image Manipulation Program can be used to create new graphics \
+or edit existing ones like photographs.)
+
#define GIMP_COPYRIGHT \
_(Copyright © 1995-2006\n \
Spencer Kimball, Peter Mattis and the GIMP Development Team)
Index: dialogs/about-dialog.c
===
RCS file: /cvs/gnome/gimp/app/dialogs/about-dialog.c,v
retrieving revision 1.139
diff -u -p -r1.139 about-dialog.c
--- dialogs/about-dialog.c 20 Jun 2006 09:14:26 - 1.139
+++ dialogs/about-dialog.c 20 Jul 2006 12:21:56 -
@@ -78,6 +78,11 @@ static gbooleanabout_dialog_anim_exp
static voidabout_dialog_reshuffle (GimpAboutDialog *dialog);
static gbooleanabout_dialog_timer (gpointer data);
+#ifdef GIMP_UNSTABLE
+static voidabout_dialog_add_unstable_message (GtkWidget *vbox,
+ GimpAboutDialog *dialog);
+#endif
+
GtkWidget *
about_dialog_create (GimpContext *context)
@@ -110,7 +115,7 @@ about_dialog_create (GimpContext *contex
name, GIMP_ACRONYM,
version,GIMP_VERSION,
copyright, GIMP_COPYRIGHT,
- comments, GIMP_NAME,
+ comments, GIMP_DESCRIPTION,
license,GIMP_LICENSE,
wrap-license, TRUE,
logo, pixbuf,
@@ -148,7 +153,12 @@ about_dialog_create (GimpContext *contex
children = gtk_container_get_children (GTK_CONTAINER (container));
if (GTK_IS_VBOX (children-data))
-about_dialog_add_animation (children-data, dialog);
+{
+ about_dialog_add_animation (children-data, dialog);
+#ifdef GIMP_UNSTABLE
+ about_dialog_add_unstable_message (children-data, dialog);
+#endif
+}
else
g_warning (%s: ooops, no vbox in this container?, G_STRLOC);
@@ -585,3 +595,25 @@ about_dialog_timer (gpointer data)
/* else keep the current timeout */
return TRUE;
}
+
+#ifdef GIMP_UNSTABLE
+
+static void
+about_dialog_add_unstable_message (GtkWidget *vbox,
+ GimpAboutDialog *dialog)
+{
+gchar *text;
+GtkWidget *label;
+
+text = g_strdup_printf (span style=\italic\%s/span,
+_(This is an unstable development release.));
+label = gtk_label_new (NULL);
+gtk_label_set_markup (GTK_LABEL (label), text);
+gtk_box_pack_start (GTK_BOX (vbox), label, FALSE, FALSE, 0);
+gtk_box_reorder_child (GTK_BOX (vbox), label, 2);
+gtk_widget_show (label);
+g_free (text);
+}
+
+#endif
+
signature.asc
Description: This is a digitally signed message part
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [PATCH] About dialog shows unstable status
Hi Sven On Wed, 2006-07-19 at 08:41 +0200, Sven Neumann wrote: Please do not use newlines do adjust spacing. Especially not in translatable strings. The spacing in the about dialog is set to what the HIG suggests and should be fine without such hacks. If you really think it needs to be changed, please file a bug-report against GTK+. In hindsight, I agree and I will remove the newlines. Mukund signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [PATCH] About dialog shows unstable status
Hi Sven On Wed, 2006-07-19 at 08:50 +0200, Sven Neumann wrote: With further input from Alan Horkan (idea to add descriptive comment) I think that the description should stay GNU Image Manipulation Program as it is now. The new text is IMO too long and I really like the fact that the current About dialog prominently expands the GIMP acronym. This doesn't really work any longer with the proposed changes. IMHO, I prefer Alan Horkan's comment about the descriptive text. I think this is what the field is for too, to describe what the application does tersely. But if you think it's unnecessary, I'll remove it out. I suggest that we keep the dialog as is for stable releases. For unstable releases, it would be nice to have a small disclaimer like you proposed. Please implement this by adding another label to the vbox. Yes it was too stupid of me to append the text to the comment field as it killed the semantic meaning of the field. I'll add another label to the dialog. Mukund signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] [PATCH] About dialog shows unstable status
Patch is attached for a simple thing. Also adds some spacing to make the text appear nicer. If you approve, I'll commit it. Screenshot: http://www.mukund.org/temp/about-2.png Index: app/about.h === RCS file: /cvs/gnome/gimp/app/about.h,v retrieving revision 1.4 diff -u -p -r1.4 about.h --- app/about.h 1 Mar 2006 08:06:08 - 1.4 +++ app/about.h 18 Jul 2006 18:57:07 - @@ -27,11 +27,13 @@ _(GNU Image Manipulation Program) #define GIMP_COPYRIGHT \ - _(Copyright © 1995-2006\n \ -Spencer Kimball, Peter Mattis and the GIMP Development Team) + _(Copyright © 1995-2006\n \ +Spencer Kimball, Peter Mattis\n \ +and the GIMP Development Team) #define GIMP_LICENSE \ - _(GIMP is free software; you can redistribute it and/or modify it\ + _(\n \ +GIMP is free software; you can redistribute it and/or modify it\ under the terms of the GNU General Public License as published by \ the Free Software Foundation; either version 2 of the License, or \ (at your option) any later version.\ @@ -43,7 +45,8 @@ \n\n \ You should have received a copy of the GNU General Public License \ along with GIMP; if not, write to the Free Software Foundation,\ -Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.) +Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. \ +\n\n ) #endif /* __ABOUT_H__ */ Index: app/dialogs/about-dialog.c === RCS file: /cvs/gnome/gimp/app/dialogs/about-dialog.c,v retrieving revision 1.139 diff -u -p -r1.139 about-dialog.c --- app/dialogs/about-dialog.c 20 Jun 2006 09:14:26 - 1.139 +++ app/dialogs/about-dialog.c 18 Jul 2006 18:57:07 - @@ -93,6 +93,12 @@ about_dialog_create (GimpContext *contex GdkPixbuf *pixbuf; GList *children; +#ifdef GIMP_UNSTABLE + gchar *comment = g_strconcat (GIMP_NAME, \n\n, +_(This is an unstable development release.), +\n, NULL); +#endif + if (gimp_pdb_lookup_procedure (context-gimp-pdb, PDB_URL_LOAD)) gtk_about_dialog_set_url_hook (about_dialog_load_url, g_object_ref (context), @@ -110,7 +116,11 @@ about_dialog_create (GimpContext *contex name, GIMP_ACRONYM, version,GIMP_VERSION, copyright, GIMP_COPYRIGHT, +#ifdef GIMP_UNSTABLE + comments, comment, +#else comments, GIMP_NAME, +#endif license,GIMP_LICENSE, wrap-license, TRUE, logo, pixbuf, @@ -124,6 +134,10 @@ about_dialog_create (GimpContext *contex */ translator-credits, _(translator-credits), NULL); + +#ifdef GUM_UNSTABLE + g_free (comment); +#endif if (pixbuf) g_object_unref (pixbuf); signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [PATCH] About dialog shows unstable status
On Tue, 2006-07-18 at 19:58 +0100, Mukund wrote: Patch is attached for a simple thing. Also adds some spacing to make the text appear nicer. If you approve, I'll commit it. Ugh.. that's GIMP_UNSTABLE.. not GUM_UNSTABLE in the patch. Corrected patch is attached. Mukund Index: app/about.h === RCS file: /cvs/gnome/gimp/app/about.h,v retrieving revision 1.4 diff -u -p -r1.4 about.h --- app/about.h 1 Mar 2006 08:06:08 - 1.4 +++ app/about.h 18 Jul 2006 18:57:07 - @@ -27,11 +27,13 @@ _(GNU Image Manipulation Program) #define GIMP_COPYRIGHT \ - _(Copyright © 1995-2006\n \ -Spencer Kimball, Peter Mattis and the GIMP Development Team) + _(Copyright © 1995-2006\n \ +Spencer Kimball, Peter Mattis\n \ +and the GIMP Development Team) #define GIMP_LICENSE \ - _(GIMP is free software; you can redistribute it and/or modify it\ + _(\n \ +GIMP is free software; you can redistribute it and/or modify it\ under the terms of the GNU General Public License as published by \ the Free Software Foundation; either version 2 of the License, or \ (at your option) any later version.\ @@ -43,7 +45,8 @@ \n\n \ You should have received a copy of the GNU General Public License \ along with GIMP; if not, write to the Free Software Foundation,\ -Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.) +Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. \ +\n\n ) #endif /* __ABOUT_H__ */ Index: app/dialogs/about-dialog.c === RCS file: /cvs/gnome/gimp/app/dialogs/about-dialog.c,v retrieving revision 1.139 diff -u -p -r1.139 about-dialog.c --- app/dialogs/about-dialog.c 20 Jun 2006 09:14:26 - 1.139 +++ app/dialogs/about-dialog.c 18 Jul 2006 18:57:07 - @@ -93,6 +93,12 @@ about_dialog_create (GimpContext *contex GdkPixbuf *pixbuf; GList *children; +#ifdef GIMP_UNSTABLE + gchar *comment = g_strconcat (GIMP_NAME, \n\n, +_(This is an unstable development release.), +\n, NULL); +#endif + if (gimp_pdb_lookup_procedure (context-gimp-pdb, PDB_URL_LOAD)) gtk_about_dialog_set_url_hook (about_dialog_load_url, g_object_ref (context), @@ -110,7 +116,11 @@ about_dialog_create (GimpContext *contex name, GIMP_ACRONYM, version,GIMP_VERSION, copyright, GIMP_COPYRIGHT, +#ifdef GIMP_UNSTABLE + comments, comment, +#else comments, GIMP_NAME, +#endif license,GIMP_LICENSE, wrap-license, TRUE, logo, pixbuf, @@ -124,6 +134,10 @@ about_dialog_create (GimpContext *contex */ translator-credits, _(translator-credits), NULL); + +#ifdef GIMP_UNSTABLE + g_free (comment); +#endif if (pixbuf) g_object_unref (pixbuf); signature.asc Description: This is a digitally signed message part ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Portable XCF
On Fri, Aug 15, 2003 at 07:45:28AM -0500, Kevin Myers wrote: | BTW, Microsoft Windows registry is already basically an extensible file | system within a file. A high end business product that I use called also | SAS has something similar. I would guess there are others out there as | well. You brought a strange thought to mind. Subversion (http://subversion.tigris.org/) implements a versioned FS using a Sleepycat's Berkeley DB database. It has a full library implementation which any application could use. Imagine that images could be revisioned. Subversion also uses a hybrid delta algorithm for binary diffs. Mukund ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Portable XCF
On Fri, Aug 15, 2003 at 03:02:46PM +0200, Tino Schwarze wrote: | Subversion (http://subversion.tigris.org/) implements a versioned FS | using a Sleepycat's Berkeley DB database. It has a full library | implementation which any application could use. | | Well, using a database as container might be a good idea. I'm not quite | familiar with Berkeley DB but it might be useful as a backend. Subversion provides its own client library for accessing the virtual file system. You won't have to work with the DB directly. It also provides an abstracted recover facility in one of its utilities (in case of stale locks). | Imagine that images could be revisioned. Subversion also uses a hybrid | delta algorithm for binary diffs. | | Worst case: I make my black image white. That's the point where a binary | diff will only waste processing power. I said hybrid delta algorithm for binary diffs. I didn't say straightforward A - B diffing. Even if your images are black and white, they are most likely stored in a compressed format (if a Subversion based GIMP file format was ever invented), and if such compressed files are revisioned, no generic algorithm is going to give you a good difference. The whole Subversion thing was a far fetched *idea*. An alternative, which is most definitely going to be blown off as there are more reasonable ways of implementing the GIMP file format which are not far fetched. Mukund ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: PS vs. PDF
On Thu, Aug 14, 2003 at 01:34:01PM -0400, Leonard Rosenthol wrote: | | Implementing a full PDF parser is definitely much harder than a full | PostScript parser. PDF more or less encompasses PostScript. | | You are quite misinformed... | | PDF is a static file format of structured objects referenced | by a single catalog (cross reference table). It's pretty easy to | write a PDF parser - a couple of days at most, which is why there are | so many of them. (the hard part is getting all the object management | correct for later modification). It has NO variables, loops, | conditionals, etc. | | Postscript is a full fledged programming language with all | that at entails (stack managements, variables, loops, functions, | conditionals, turing completeness, etc.). Person! I said it more or less encompasses PostScript. I do agree that the interpreter is much simpler in case of the PDF due to the absence of procedures, variables, conditionals, etc. But PDF has a lot of other features which add complexity to it over PostScript. You yourself have listed features such as JPEG2000, 16-bit images and JBIG. PDF also supports more types of fonts, supports hyperlinks, annotations, bookmarks, thumbnails, scripting -- there you go, encryption and signatures, plug-ins and more. | PostScript is much more widely supported than PDF. | | Only as far as direct/native printing goes - that's true. | | On the application side, PDF has wider support due to the | ease of implementation. See above. PDF has become popular on screen displays (and even for printing as a result), but I think it has more to do with Adobe pushing the PDF format with a free viewer, and due to it's document capabilities. | It is just as extensible as PDF as far as imaging goes. | | To an extent - there are things that PDF does by default that | PS can't do (eg. 16bit images, JPEG2000, JBIG2), and there are areas | of PDF that provide extensibility that PS does not. We were talking about extensibility, not about features that come bundled. There are areas of PDF that provide extensibility, but none of them directly apply to the GIMP or processing of imaging information. | Sure, at some point the printer is just putting bits on a | page - but only the home-level inkjets are ONLY raster-based. | Professional office and prepress printers use a page description | language (usually either PCL or PS) to keep traffic down and then | rasterize on the device. | | Most implement RIPping on the device itself... | | | More or less, most people are able to print PostScript on their printers | on most major operating systems. | | Not out of the box! They would need to install Ghostscript | (and associated drivers, which might also require something like | GIMP-print). To print PostScript, one doesn't need GIMP-print. My OS (Red Hat Linux) came with Ghostscript installed out of the box. I assume Mac OS X can also handle PostScript out of the box as it has a unix toolchain. IIRC it uses CUPS as its print system. I am not sure about Windows as I haven't worked with it in a long time. The point of my statements was to say that despite them being PCL or raster-based printers, they can still print PostScript. They can sure print PDF as well in the same way. The point Joao was trying to make was that one can print PostScript on a printer way easier than one might print a custom GIMP file format as they don't need to find a copy of GIMP to print it, and that gives weightage to going with a PostScript file format. Mukund ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Portable XFC
On Wed, Aug 20, 2003 at 07:45:33PM -0400, Leonard Rosenthol wrote: | | Because Postscript is dead. It hasn't been updated in over 6 | years, and Adobe themselves are slowly moving towards PDF-based | solutions, including printing. PostScript is far from dead. You would be banishing the entire publishing industry if you say PostScript is dead :-) Are you sure it hasn't been updated for so long? Take a look at the PostScript 3 reference manual. | Also, Postscript is a programming language. You would need | to implement a full parser and interpreter for it. NOT a fun thing. | | You'd be better off heading down the PDF route...All the | benefits of PS, but a LOT easier to implement and MUCH more | extensible and supported. Implementing a full PDF parser is definitely much harder than a full PostScript parser. PDF more or less encompasses PostScript. PostScript is much more widely supported than PDF. It is just as extensible as PDF as far as imaging goes. | The major one, of course, is that the file would be essentialy | auto renderable - no need of GIMP, neither of any other program, | to get it printed. | | Assuming a PS printer... | | But most users either have PCL or raster-based printers... Most printers are raster based at the core, except for certain plotters (which are very interesting to watch BTW). Some printing solutions implement the RIP in software on the host computer (such as Ghostscript or Adobe's PressReady -- not sure if the latter has been deprecated by something else). Others implement it on the printer itself, such as a few printers in the HP LaserJet family. More or less, most people are able to print PostScript on their printers on most major operating systems. | Since PSD and TIFF are used by ADOBE, ADOBE also has a program that | makes use of postscript subsets.. I just do not remember which file | type it is. | | Versions of Adobe Illustrator = 8 used a subset of EPS | (Encapsulated Postscript) as its native file format. As of version | 9, it now uses PDF as the file format. | | | It can have color profiling support - it is on the specifications. | It has support for multiple compression standards... (ok, maybe you | have to encode the decompressor algorithm inside the file as well if | you want something too different) | | PS doesn't support plug-in filters... As compared to PDF? In the context of the original poster's comment, what did you have in mind for using plug-in filters? How is the PDF plug-in support useful in any way with image representation? The original poster was talking about color profiles. Mukund ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Portable XFC
On Wed, Aug 13, 2003 at 08:32:00PM -0300, Joao S. O. Bueno wrote: | But on this new thread were proprietary formats batle along with mutant | ideas, here I go: | Why not settle for a Postscript subset? PostScript is a proprietary format controlled by Adobe. Adobe has several patents on various aspects of the PostScript format any implementation would be affected by. | The major one, of course, is that the file would be essentialy auto | renderable - no need of GIMP, neither of any other program, to get it | printed. This is a good idea, but it would also mean GIMP would have to read back a PostScript file. PostScript is a huge standard outside the scope of an application such as the GIMP. Developers would have to put in kludges and special comments which'll help them represent structures which cannot be natively represented using PostScript. Isn't this just as expensive as implementing a new specification? What's more easier? A Have a native file format designed for the GIMP. Those who want to use it with PostScript aware applications export the native format using a plug-in. If XML is used for the underlying data representation, any XML parser can be used to parse information, especially information such as the author of an image, size and colour depth of the image, etc. B Use a subset PostScript as the native file format. Design and implement representation of unrepresentable structures in PostScript comments. Implement a PostScript parser (which is as good as a stack based interpreter). | Since PSD and TIFF are used by ADOBE, ADOBE also has a program that | makes use of postscript subsets.. I just do not remember which file type | it is. | | It can have color profiling support - it is on the specifications. It | has support for multiple compression standards... (ok, maybe you have to | encode the decompressor algorithm inside the file as well if you want | something too different) Support for multiple compression algorithms can be implemented in an XML based format. One can also have data in other image formats such as TIFF, PNG or even the same GIMP native format itself embedded as CDATA, or the file format may be an archive of associated images, etc. The features implemented depend on how far developers want to take the new file format. The developers themselves are capable of doing what they want :-) Mukund ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
