[Gimp-developer] GIMP for smartphones tablets
Have you guys ever considered making a GIMP mobile app? This way iPad, iPhone, iPod Touch, Android users could enjoy quality open-source raster graphics editing. Note: Please make them Universal apps (phones tablets with the OS).___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GIMP for smartphones tablets
On Tue, Aug 28, 2012 at 5:46 AM, Thomas Hood wrote: Have you guys ever considered making a GIMP mobile app? This way iPad, iPhone, iPod Touch, Android users could enjoy quality open-source raster graphics editing. Note: Please make them Universal apps (phones tablets with the OS). http://9to5mac.com/2011/01/07/vlc-for-ios-removed-from-the-app-store/ http://www.mail-archive.com/gimp-developer@lists.xcf.berkeley.edu/msg22451.html 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] GIMP 1.8.2 for Mac (official?) Build
On Mon, 2012-08-27 at 22:02 -0600, Clayton Walker wrote: Hello, and sorry for the wait! Here's a brand new build of Gimp for osx, directly from the 2.8.2 tarball. I have included python and theme support, and it was built using jhbuild and gtk-mac-bundler. I have included no plugins, as they tend to quickly increase the size of the gimp application. Please report all bugs to the bug tracker, and have fun! https://dl.dropbox.com/u/942685/gimp-2.8.2-dmg-1.dmg If someone could just mirror that on the gimp ftp website, or upload it to sourceforge or something, that would be great. Thanks! Great! :) I have uploaded it to ftp.gimp.org and updated the download page on www.gimp.org. Thanks Clayton for the effort to make this happen! Regards, --mitch ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GIMP 1.8.2 for Mac (official?) Build
On Tue, Aug 28, 2012 at 8:02 AM, Clayton Walker wrote: Hello, and sorry for the wait! Here's a brand new build of Gimp for osx, directly from the 2.8.2 tarball. I have included python and theme support, and it was built using jhbuild and gtk-mac-bundler. Is that a native, no X11 build? I have included no plugins, as they tend to quickly increase the size of the gimp application. You mean native plugins or 3rd party? 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] GIMP 1.8.2 for Mac (official?) Build
On Tue, 2012-08-28 at 12:12 +0400, Alexandre Prokoudine wrote: On Tue, Aug 28, 2012 at 8:02 AM, Clayton Walker wrote: Hello, and sorry for the wait! Here's a brand new build of Gimp for osx, directly from the 2.8.2 tarball. I have included python and theme support, and it was built using jhbuild and gtk-mac-bundler. Is that a native, no X11 build? native I have included no plugins, as they tend to quickly increase the size of the gimp application. You mean native plugins or 3rd party? 3rd parts, all native plugins are there --mitch ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GIMP 1.8.2 for Mac (official?) Build
I should be able to make 3rd party plugin packs available for download soon. On Tue, Aug 28, 2012 at 3:42 AM, Michael Natterer mi...@gimp.org wrote: On Tue, 2012-08-28 at 12:12 +0400, Alexandre Prokoudine wrote: On Tue, Aug 28, 2012 at 8:02 AM, Clayton Walker wrote: Hello, and sorry for the wait! Here's a brand new build of Gimp for osx, directly from the 2.8.2 tarball. I have included python and theme support, and it was built using jhbuild and gtk-mac-bundler. Is that a native, no X11 build? native I have included no plugins, as they tend to quickly increase the size of the gimp application. You mean native plugins or 3rd party? 3rd parts, all native plugins are there --mitch ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list -- Please note that this signature is licensed under the General Public License. By embedding the signature, or parts of it, into your brain other than by mere aggregation, your brain becomes a combined, and therefore derived, work and thus must be licensed under the GPL too. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GIMP 1.8.2 for Mac (official?) Build
Someone asked if svg support was no longer supported. I fixed that and have included svg support in my new build, but I won't be upgrading/fixing any more import/export features until 2.8.4, as I don't want to spam the ftp website and this mailing list. Only deal-breakers will warrant new releases. https://dl.dropbox.com/u/942685/gimp-2.8.2-dmg-2.dmg NOTE: This only fixes svg support. On Tue, Aug 28, 2012 at 10:08 AM, Clayton Walker blender3dart...@gmail.comwrote: I should be able to make 3rd party plugin packs available for download soon. On Tue, Aug 28, 2012 at 3:42 AM, Michael Natterer mi...@gimp.org wrote: On Tue, 2012-08-28 at 12:12 +0400, Alexandre Prokoudine wrote: On Tue, Aug 28, 2012 at 8:02 AM, Clayton Walker wrote: Hello, and sorry for the wait! Here's a brand new build of Gimp for osx, directly from the 2.8.2 tarball. I have included python and theme support, and it was built using jhbuild and gtk-mac-bundler. Is that a native, no X11 build? native I have included no plugins, as they tend to quickly increase the size of the gimp application. You mean native plugins or 3rd party? 3rd parts, all native plugins are there --mitch ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list -- Please note that this signature is licensed under the General Public License. By embedding the signature, or parts of it, into your brain other than by mere aggregation, your brain becomes a combined, and therefore derived, work and thus must be licensed under the GPL too. -- Please note that this signature is licensed under the General Public License. By embedding the signature, or parts of it, into your brain other than by mere aggregation, your brain becomes a combined, and therefore derived, work and thus must be licensed under the GPL too. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Nightly Builds
FYI, for anyone new interested in getting this to work from scratch these are the minor adjustments I had to make to complete the compilation on Ubuntu: 1. Get latest Ubuntu with latest updates up and running (I used VirtualBox) 2. Install pre-reqs. I had to add the last 3 to get the compilation to finish on Ubuntu. The weird one was that the mingw-w64 package didn't include g++... sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev g++-mingw-w64 intltool xsltproc 3. git clone https://github.com/drawoc/windows-gimp-jhbuild 4. Follow readme During the installation I believe I had to manually sudo the bzip2 install and freetype failed the first time around (wipe and re-do fixed it with some magic). Once the build is completed, is there a good way to figure out what the actual files needed are? I can of course compare to the released Windows build of course but it would be nice to have a more 'scientific' approach and some more insight :) Thanks again to drawoc for your help! -Original Message- From: drawoc [mailto:dra...@darkrefraction.com] Sent: Wednesday, August 22, 2012 10:01 PM To: Jari Niskala Cc: gimp-developer-list@gnome.org Subject: Re: [Gimp-developer] Nightly Builds Glad to hear you've got it working. :) -- drawoc On Wed, Aug 22, 2012 at 12:49 PM, Jari Niskala jarinisk...@gmail.com wrote: Hi Drawoc, Thanks for your help in this! I finally got it working although it ended up being on Ubuntu. The weird part was that for Ubuntu, the glib-compile-resources was there in the same package... I also had to add some other mingw components etc but I'm now very happy to have a working build environment :) Thanks again for your prompt and helpful responses! Best regards, Jari Niskala Mobile: (858) 449-8952 -Original Message- From: drawoc [mailto:dra...@darkrefraction.com] Sent: Sunday, August 19, 2012 3:49 PM To: Jari Niskala Cc: gimp-developer-list@gnome.org Subject: Re: [Gimp-developer] Nightly Builds Maybe libglib2.0-bin didn't install correctly? Try reinstalling it: sudo apt-get install --reinstall libglib2.0-bin -- drawoc On Sun, Aug 19, 2012 at 4:57 PM, Jari Niskala jarinisk...@gmail.com wrote: Unfortunately I did catch that so no luck with that :) It's really weird... I couldn't find anything obvious for it online either. -Original Message- From: drawoc [mailto:dra...@darkrefraction.com] Sent: Sunday, August 19, 2012 1:33 PM To: Jari Niskala Cc: gimp-developer-list@gnome.org Subject: Re: [Gimp-developer] Nightly Builds Ah, in my last email, the command that said this: sudo apt-get install build-essential mingw-w64 git jhbuild automake autoconf libtool libgtk2.0-dev was supposed to be all on one line, but it got automatically word-wrapped at some point. As a result, it looks like you missed those last three packages, so just run this to install the missing packages as well: sudo apt-get install autoconf libtool libgtk2.0-dev -- drawoc On Sun, Aug 19, 2012 at 4:01 PM, Jari Niskala jarinisk...@gmail.com wrote: Thanks Drawoc! I got my Linux Mint Debian running but I keep running into a problem when the jhbuild is trying to configre glib...: configure: error: Could not find a glib-compile-resources in your PATH *** Error during phase configure of glib: ## Error running ./configure --prefix /home/jari/windows-gimp-jhbuild/targets/gimp-dev/ --libdir '/home/jari/windows-gimp-jhbuild/targets/gimp-dev//lib' --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --disable-docs --enable-all-warnings --disable-static --enable-debug=no AR=/usr/bin/i686-w64-mingw32-ar RANLIB=/usr/bin/i686-w64-mingw32-ranlib STRIP=/usr/bin/i686-w64-mingw32-strip AS=/usr/bin/i686-w64-mingw32-as DLLTOOL=/usr/bin/i686-w64-mingw32-dlltool OBJDUMP=/usr/bin/i686-w64-mingw32-objdump NM=/usr/bin/i686-w64-mingw32-nm WINDRES=/usr/bin/i686-w64-mingw32-windres --disable-gtk-doc --cache-file=/home/jari/windows-gimp-jhbuild/win32.cache *** [5/24] Any ideas? I can see that glib-compile-resource.c is part of glib itself but it's not on my system. I can see other glib components there just fine such as glib-compile-schemas. Thanks! -Original Message- From: drawoc [mailto:dra...@darkrefraction.com] Sent: Tuesday, August 14, 2012 5:29 PM To: Jari Niskala Cc: gimp-developer-list@gnome.org Subject: Re: [Gimp-developer] Nightly Builds I run the scripts under Debian testing regularly, so if you choose Debian or one of its derivatives you shouldn't have a hard time. If you're still fairly new to linux though, you probably want to go with something other than straight Debian. Linux Mint is my personal favorite of the more user-friendly distros (and it's debian-derived). http://www.linuxmint.com/ You might want to go with eg. the xfce version of mint as it should be faster than the cinnamon or mate based desktops. Anyway, once you
Re: [Gimp-developer] the Gimp lcms.c plug-in
On 8/27/12, Øyvind Kolås pip...@gimp.org wrote: On Mon, Aug 27, 2012 at 4:08 PM, Elle Stone l.elle.st...@gmail.com wrote: My lcms2 plug-in now does do correct ICC profile conversions, from any RGB color space, to any RGB color space, at 8-bit integer, 16-bit integer, and 32-bit floating point. However, to get it to work, I had to modify the babl/babl/util.h file. This is great news, since it means that the code works as intenended but probably with slightly different intentions. Could you clarify? which code works with which intentions? After modifying the babl/babl/util.h file, 16-bit tiffs open correctly. As you might recall, with the default util.h file, 16-bit tiffs open with a mysterious and erroneous gamma=2.2 correction having been applied. This tiff issue has nothing to do with the lcms plug-in. Data stored for higher bitdepths per pixel than 8 are assumed to be stored with a linear gamma ramp, ICC V2 matrix profiles (simplest case here) have two parts that are relevant to the present discussion: 1. They have RGB/XYZ primaries, the chromaticity coordinates that interpret if you will the chroma part of the image RGB values. 2. They have a tone response curve (TRC) that determines how fast the image RGB tonality approches maximum white, starting from minimum black, as the RGB values go from 0 to whatever maximum value is allowed by the bit-depth of the image. Also, the sRGB V2 matrix ICC profile has a 1024 point TRC that is contained in the sRGB profile TRC tags; this sRGB TRC can be exported and then imported into another ICC profile to change the other profile's TRC, to create a variant of the other profile that has the other profile's primaries, but the sRGB TRC. The *only* time the default babl code properly converts an image from one ICC profile to another is if two conditions are met: 1. The primaries are the same in the source and destination profiles. 2. The TRCs of the two profiles are either linear gamma or the sRGB TRC. So if I create a scarse prophoto variant that has a TRC equal to the sRGB TRC instead of being equal to gamma=1.8, and a second variant that has a linear gamma TRC, I can use the default babl code to convert from linear prophoto to the special prophoto variant with the sRGB TRC and back again. If I create a variant of ClayRGB that has a linear gamma TRC and a second variant that has the sRGB TRC, I can use the default babl code to convert from linear gamma ClayRGB to the special ClayRGB variant with the sRGB TRC and back again. All other ICC profile conversions are wrong if done with the default babl code, but correct if I modify the /babl/babl/util.h file. In particular, if I keep the TRC as linear gamma for the source and destination profile, but the primaries vary, the colors are wrong. And if I keep the primaries the same for the source and destination profile, but the TRCs are anything other than linear gamma and the sRGB TRC, the tonality comes out wrong. And if both the primaries and the TRC vary, then everything is wrong. Unless I modify the util.h file. Then everything is right. a higher level code where you probably could do a similar tweak without changing core babl behavior could be in ... digging through GIMP code ... gimp/app/gegl/gimp-babl.c which contains code determining the data expected to be managed, for all arbitrary profile source imagery it would be recommended to store layer data in floating point. I don't think there is any way to tweak the Gimp code to undo the effect of the util.h code that converts something in the background from a linear gamma TRC to the regular sRGB TRC and back. But perhaps if I had a better understanding of what the default babl code in babl/babl/base/util.h, and also in fast-float.c and float.c, is supposed to accomplish, it would help. Can anyone give a summary? /Øyvind K. Elle ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GIMP 1.8.2 for Mac (official?) Build
You might want to come to irc quickly, we some other fixes for you :) On Tue, 2012-08-28 at 11:27 -0600, Clayton Walker wrote: Someone asked if svg support was no longer supported. I fixed that and have included svg support in my new build, but I won't be upgrading/fixing any more import/export features until 2.8.4, as I don't want to spam the ftp website and this mailing list. Only deal-breakers will warrant new releases. https://dl.dropbox.com/u/942685/gimp-2.8.2-dmg-2.dmg NOTE: This only fixes svg support. On Tue, Aug 28, 2012 at 10:08 AM, Clayton Walker blender3dart...@gmail.comwrote: I should be able to make 3rd party plugin packs available for download soon. On Tue, Aug 28, 2012 at 3:42 AM, Michael Natterer mi...@gimp.org wrote: On Tue, 2012-08-28 at 12:12 +0400, Alexandre Prokoudine wrote: On Tue, Aug 28, 2012 at 8:02 AM, Clayton Walker wrote: Hello, and sorry for the wait! Here's a brand new build of Gimp for osx, directly from the 2.8.2 tarball. I have included python and theme support, and it was built using jhbuild and gtk-mac-bundler. Is that a native, no X11 build? native I have included no plugins, as they tend to quickly increase the size of the gimp application. You mean native plugins or 3rd party? 3rd parts, all native plugins are there --mitch ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list -- Please note that this signature is licensed under the General Public License. By embedding the signature, or parts of it, into your brain other than by mere aggregation, your brain becomes a combined, and therefore derived, work and thus must be licensed under the GPL too. ___ 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
