[Gimp-developer] Website updates for 2.2 release
Hello everyone, So time has come to start thinking about the information provided on the website before the 2.2 release is out. The first thing that is needed is some information on how to update from 2.0 to 2.2 and how to have 2.0 and 2.2(-preX) installed side-by-side. This is a great time for everyone that wants to help with the website to come forward and help. If you are interested then join the gimp-web list and help to start discussions and even help with the information on the website. As all may understand what the main reason is for the updates is to keep up-to-date with the application itself and so we need to start thinking about making 2.0 information into 2.2. At the moment I do not have a list of TODOs but I am sure with this mail that we all can start discussing the different places that needs updating and what would be good to add to the site. Right now we just need to start thinking about the information that needs updating and not adding new sections etc. So please come with ideas and help us to get a even better website then it was before. Regards, -- Niklas Mattisson ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] directory organisation [was Re: [Gimp-user] Installing plug-ins (fwd)]
One thing I have always admired about the gimp is the logical organisation of its files on disk. Unlike most other programs the gimp developers had the foresight to create a sensible directory structure /usr/share/gimp /usr/share/gimp/2.0 /usr/share/gimp/2.2 whereas most applications are less sensibly organised and create files like /usr/share/appname /usr/share/appname2 /usr/share/appname3 The message below from the user list reminded me and I was wondering Would it be possible to continue this elegent and logical organistion sense to the same for files in the user home directory and in future have something like this? ~/.gimp/2.2 ~/.gimp/3.0 (I'll file a bug report and try and make a patch if this idea is deemed acceptable) Sincerely Alan Horkan -- Forwarded message -- Date: Tue, 26 Oct 2004 15:14:22 +0200 From: Sven Neumann <[EMAIL PROTECTED]> To: Carol Spears <[EMAIL PROTECTED]> Cc: GIMPUser <[EMAIL PROTECTED]> Subject: Re: [Gimp-user] Installing plug-ins Hi, Carol Spears <[EMAIL PROTECTED]> writes: > actually, i was wrong. the cvs version of gimp is now installing > things into ~/.gimp-2.0/ i guess until the plug-ins catch up with > the version numbers. GIMP 2.2 will be using the ~/.gimp-2.2 directory. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] open thumbnail and raw files
Hi, Joseph Heled <[EMAIL PROTECTED]> writes: > The gimp Open Image dialog contains preview thumbnail. To generate > them, gimp calls the plugin to generate them. Now, for raw digital > camera files (.nef, .crw ...) this is a very expensive operation - and > obviously one would love to use the prepared/pre-stored thumbnail > which exists in the file. > > From what I could see, there is no way I (the plugin author) can > detect if the call is for a thumbnail or not. > > Can someone tell me if I am right or wrong? > > If wrong - how do I do it? > If right, is there a chance this can be changed? You are right. You could suggest an API and we could consider to add it for GIMP 2.4. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer