Re: [Gimp-developer] [GIMP-developer] Discontinuation of mailing lists and moving to Discourse
Hello, On Fri, 21 Oct 2022 11:25:05 -0500 Pat David via gimp-developer-list wrote: > It's worth noting that in general, you can use a Discourse forum _entirely_ > in mailing-list mode if you want to. That is, you'll still see emails > coming in from the system and can reply to them in your mail client of > choice. > On the backend, this translates into emails from you becoming forum posts > on discourse, and new posts showing up as new messages in your inbox. > > We've got a bunch of users at pixls using it in mailing-list mode (myself > included for a while initially). > > The caveat, of course, is that you'll still need to register for an account > on the forum in the first place (to provide your email address and set up > any settings you want initially). > Another caveat is that the forum administrators need to enable this as an > option - particularly for mailing *into* the forum to start a new topic (I > have this turned off be default on pixls but will enable it shortly for > y'all). [snip] Is it true that topics get auto-locked after few weeks? That doesn't seem pretty smart in terms of software development or user support at all, if it's true. The same topic is discussed here and there, it's interesting (and a bit scary) to see feedback coming from discourse users - currently I'm following the midnight commander ML as well, hosted at gnome.org for historical reasons but definitely independent nowadays. Regards, -- wwp https://useplaintext.email/ pgpOjab4tQpsz.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Looking for gexiv2 maintainer
Hi, On Sun, 12 Sep 2021 08:24:00 +0300 Shlomi Fish wrote: > Hi Jens, > > On Sun, 29 Aug 2021 02:30:07 +0200 > Jens Georg wrote: > > > Hello, > > > > I am going to give up gexiv2 maintainership, for multiple reasons. > > > > One of them is that I have too many projects, the other one is I don't > > want to work with Exiv2 upstream anymore. > > > > I will do a final 0.14 release for GNOME 41 and than I'll stop caring. > > Sorry about that, but I have to let that go, for my onw personal > > sanity. > > > > I can try to volunteer some time, but note that I have some disabilities: > https://www.shlomifish.org/meta/FAQ/which_disabilities_do_you_have.xhtml . My > gnome acct is https://gitlab.gnome.org/shlomif . Having Shlomi Fish taking over the maintenanceship and further moves of gexiv2 seems a good thing to me! My 2 cents, -- wwp https://useplaintext.email/ pgp3L64kCSjeH.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp "make install" fails with undefined references to fresh-built gegl
Hello Deft, On Tue, 16 Jun 2020 18:37:09 -0700 "Deft Developer" wrote: > I built gimp 2.10.18 on CentOS 7 last year on another host, but on a new > host with gimp 2.10.20, I'm stuck with undefined reference errors for GEGL. > I'm not a c++ developer, so this is all a foreign language to me :( > > CentOS 7 libraries are all very old, so I built them, including latest GEGL > (0.4_24) and configured it with -prefix=/opt/gimp2.10 > > I deleted all gegl files before rebuilding, and now when I look in the lib64 > dir I see the new libs: > > ls -1 /opt/gimp-2.10/lib64/libgegl-* > /opt/gimp-2.10/lib64/libgegl-0.4.so > /opt/gimp-2.10/lib64/libgegl-0.4.so.0 > /opt/gimp-2.10/lib64/libgegl-0.4.so.0.424.1 > /opt/gimp-2.10/lib64/libgegl-npd-0.4.so > /opt/gimp-2.10/lib64/libgegl-sc-0.4.so > > ls -1 /opt/gimp-2.10/lib64/pkgconfig/gegl-* > /opt/gimp-2.10/lib64/pkgconfig/gegl-0.4.pc > /opt/gimp-2.10/lib64/pkgconfig/gegl-sc-0.4.pc > > I set LD_LIBRARY_PATH and PKG_CONFIG_PATH to include my fresh libraries: > > LD_LIBRARY_PATH=/opt/gimp-2.10/lib64:/opt/gimp-2.10/lib:/usr/local/lib64:/us > r/local/lib:/usr/lib > > PKG_CONFIG_PATH=/opt/gimp-2.10/lib64/pkgconfig:/opt/gimp-2.10/share/pkgconfi > g:/opt/gimp-2.10/lib/pkgconfig/pkgconfig:/usr/local/share/pkgconfig:/usr/loc > al/lib/pkgconfig > > But when I try to build gimp, ld fails. The errors start with: > > make[3]: Entering directory > '/usr/exports/projects/3rd_party/gimp-world/gimp/app' > > CCLD gimp-2.10 > > display/libappdisplay.a(gimpdisplay.o): In function > `gimp_display_update_bounding_box': > > gimpdisplay.c:(.text+0x130c): undefined reference to > `gegl_rectangle_subtract' > > ... > > gimp-gegl-utils.c:(.text+0xc7e): undefined reference to > `gegl_rectangle_subtract' > > collect2: error: ld returned 1 exit status > > make[3]: *** [Makefile:1010: gimp-2.10] Error 1 > > ... > > > > Is this a gegl mis-configuration or a gimp one? > > How should I fix? I build Gimp 2.8.x and 2.10.x on CentOS 7 (with the almost complete set of dependencies and dependencies of dependencies and the cross-dependency hell) too, and didn't face this situation. Did you build the 2.10.20 sources against the old gegl, then build the new gegl and rebuild gimp without doing a `make clean`? Regards, -- wwp https://useplaintext.email/ pgp5cmJb_ZP2z.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] [ANNOUNCE] GIMP 2.10.20, babl 0.1.78, GEGL 0.4.24
Hello Øyvind, On Fri, 12 Jun 2020 19:21:28 +0200 Øyvind Kolås wrote: > On Fri, Jun 12, 2020 at 9:47 AM wwp wrote: > > Is it normal if all files in babl and gegl sources archives are from > > epoch origin (Jan 1 1970)? > > > > Not sure if it's related, but ninja-build fails when I attempt to build > > babl or gegl here (CentOS 7, ninja 1.7.2): > > ninja: error: manifest 'build.ninja' still dirty after 100 tries > > > > A recursive `touch` in the sources tree did solve it. > > Not sure what is going on, maybe something is odd on your system - I > haven't heard > of such an issue before, and the tarballs themselves do seem fine: > > $ tar tvf babl-0.1.78.tar.xz | tail -n3 ; tar tvf gegl-0.4.24.tar.xz | tail > -n3 > -rw-r--r-- pippin/pippin950 2020-06-07 19:38 > babl-0.1.78/tools/introspect.c > -rw-r--r-- pippin/pippin518 2020-06-07 19:38 babl-0.1.78/tools/meson.build > -rw-r--r-- pippin/pippin 5941 2020-06-07 19:38 > babl-0.1.78/tools/trc-validator.c > -rw-r--r-- pippin/pippin 14034 2020-06-07 21:11 > gegl-0.4.24/tools/operation_reference.c > -rw-r--r-- pippin/pippin 24479 2020-06-07 21:11 > gegl-0.4.24/tools/operations_html.c > -rwxr-xr-x pippin/pippin2701 2020-06-07 21:11 > gegl-0.4.24/tools/xml_insert.sh Well.. you're right, it seems that unpacking the archives using `mc` goes with wrong file dates (using a plain `tar cJf` is fine). This is the first time I encounter this issue, I'll see w/ the `mc` guys, maybe something is specific with those babl/gegl archives, maybe it's a bug on `mc`'s side or whatever. The ninja error seems quite common when file date is "abnormal", anyway I could workaround it. Thanks! Regards, -- wwp https://useplaintext.email/ pgpiKlD10M5iO.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] [ANNOUNCE] GIMP 2.10.20, babl 0.1.78, GEGL 0.4.24
Hello, On Thu, 11 Jun 2020 16:51:26 +0300 Alexandre Prokoudine via gimp-developer-list wrote: > Hello, > > We've just released GIMP 2.10.20 with usability improvements, new > features, and bug fixes. Just like always, the release is accompanied > by new releases of babl and GEGL libraries. > > Here's release notes with screenshots and whatnot :) > > https://www.gimp.org/news/2020/06/11/gimp-2-10-20-released/ > > For a full list of changes, please see the respective NEWS files. > > https://gitlab.gnome.org/GNOME/gimp/-/blob/master/NEWS > https://gitlab.gnome.org/GNOME/babl/-/blob/master/NEWS > https://gitlab.gnome.org/GNOME/gegl/-/blob/master/docs/NEWS.txt Is it normal if all files in babl and gegl sources archives are from epoch origin (Jan 1 1970)? Not sure if it's related, but ninja-build fails when I attempt to build babl or gegl here (CentOS 7, ninja 1.7.2): ninja: error: manifest 'build.ninja' still dirty after 100 tries A recursive `touch` in the sources tree did solve it. Regards, -- wwp https://useplaintext.email/ pgpgcnKVYQedF.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Questions about the split view feature
Hello, the split view in Gimp 2.10 is an awesome feature! Here are my questions: - I couldn't find a way to have the split view turned on by default, in any place. Is that possible? - The split view handle is only visible when the guides are visible. You probably see me coming, because, when the guides are unvisible, turn on the split view and.. and nothing :-). Shouldn't turning the split view on, make the guides visibles? Or just the split view guide (make it a non-discardable guide)? Regards, -- wwp pgpjxniWnKf2O.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Usability request, step value on the slider widgets
Hello there, I'm a very-happy user of Gimp 2.10.x now, but noticed there's an itchy point in my production process, it's about usability, more precisely it concerns the granularity of the new sliders widgets used, for instance, in the Hue-Saturation dialog, to move the Hue, Lightness, Saturation dialogs (and everywhere else). If mastering those widgets was not trivial at once, compared to the usual ones - the sensitivity is vertically split in two, both halves behaving differently, they are better than the former ones, it took me time to make my "hand" to it. The usability issue with them, is that there is no more +10/-10 granularity when you use the mouse to click on them, you cannot make the value jump by 10 left or right by other means than reaching the widget using TAB key several times (if you directly click it to put the focus, you'll modify the value - arg!) then pressing page up/down. Clicking with left or right button produces the same behaviour, whereas clicking with right button could have been used to make the value +10/-10 instead of the default behaviour (make the value to the exact position clicked) - or using modifier keys. Same, I though another step value could have been used w/ the arrows to the right, but it's +1/-1, whatever you left or right click, with or without modifiers keys. Here too, a shift click. To summarize, if it's possible to use page up/page down to use a +10/10 value step, it would help to use an alternate click method to get the same: in the widget band and on the right-side arrows. Any thought? Regards, -- wwp pgp8sIXALRflZ.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] note to packagers: partially desynchronising babl, GEGL and GIMP releases cycles
Hello Øyvind, On Mon, 22 Oct 2018 15:13:12 +0200 Øyvind Kolås wrote: > Packagers for linux distributions should update the recipes for babl > and GEGL, and new releases of GIMP 2.10.6 for flatpak/snap/OSX/windows > with the new babl and GEGL is desirable. > > Before in the 2.10 releases we have synchronized the releases of babl, > GEGL and GIMP. This synchronization has been a by-product of work on > finishing the GIMP release have resulted in additional commits to > GEGL; and thus coordinating the releases have been neccessary also to > have a properly building GIMP. As the 2.10 series stabilizes and > releases become less frequent we can expect having babl and GEGL > releases also in-between future stable GIMP releases. > > babl-0.1.58 and GEGL-0.4.10 have already been released this month > > Building the previous release of GIMP-2.10 with the new babl will fix > regressions the 2.10 series of GIMP has had over 2.8 in workflows > involving first transforming or deforming a layer. These operations > now maintain the color of fully transparent pixels, thus making > anti-erase mode of the paint tools and the alpha channel mode of the > curves tool. > > GEGL has an important display fix for OSX, where severe display > glitches on some zoom levels now are gone. > > These changes come In addition to performance improvements, in > particular babl is now doing (most) reference computations in 32bit > floating point rather than 64bit floating point speeding up initial > and some runtime pixel format conversions, for more complete release > note for babl-0.1.58 and GEGL-0.4.10 including internal refactoring > and new features, see their respective NEWS files. Thanks for this detailed notification, good to know. Regards, -- wwp pgpVcH9N4USAJ.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] how to build json-glib in a prefix when building gimp from git in a prefix?
Hello Ken, On Sun, 30 Sep 2018 02:33:34 +0100 Ken Moffat via gimp-developer-list wrote: > On Sun, Sep 30, 2018 at 12:00:40AM +0100, Ken Moffat via gimp-developer-list > wrote: > > On Sat, Sep 29, 2018 at 06:21:36PM -0400, Elle Stone wrote: > > > > > > I don't know what version json-glib from git is on. I cloned it as > > > follows: > > > git clone https://gitlab.gnome.org/GNOME/json-glib But I'd be happy to > > > download a specific tarball, if anyone knows what version of json-glib is > > > currently required by GIMP. > > > > Are you sure you need json-glib ? > > I just cloned https://gitlab.gnome.org/GNOME/gimp.git a few minutes > ago. I cani't run ./autogen.sh (don't have gtk-doc, and no intention > of installing that source of pain), but grepping for json-glib only > finds: > > ken@origin /scratch/ken/git/gimp $find -type f | xargs grep json-glib > ./build/windows/jhbuild/gimp.moduleset:package="json-glib"/> > ./build/windows/jhbuild/misclibs.moduleset: autogen-sh="configure"> > ./build/windows/jhbuild/misclibs.moduleset: > module="json-glib/1.2/json-glib-1.2.2.tar.xz" > ./build/docker/gimpbuilder-base/Dockerfile:RUN apt-get install > $APT_GET_OPTIONS intltool libglib2.0-dev libjson-c-dev libjson-glib-dev > libgexiv2-dev libcairo2-dev libpango1.0-dev libjpeg62-turbo-dev > libsuitesparse-dev libspiro-dev libopenexr-dev libwebp-dev > > which suggests that only docker and windows need it. And grepping > for JSON in capitals finds some perl modules in a git hook, and > JSON_C_LIBS references in the Makefile.am files under app/ - json-c > (0.12.1) is again referenced in windows and docker files. Json-glib *is* needed to build gimp 2.10. I build gimp 2.8/2.10 on CentOS 6 and 7 boxes, where no package is available (for the latest 2.8 and 2.10 at all), and I build quite all the necessary deps (it's a lot and the cross-deps are a nightmare), json-glib is required at some step. From what I see in my build script, gegl 0.3/0.4 need it. Regards, -- wwp pgpqctCZ_Vflu.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Please migrate to GitHub/CMake
Hello, On Sun, 7 May 2017 16:33:49 +0300 Shlomi Fish <shlo...@shlomifish.org> wrote: > Dear Alexandre, > [snip] > As a side note regarding IRC - old does not necessarily imply it is bad (see > http://www.shlomifish.org/humour/fortunes/show.cgi?id=two-kinds-of-fools ) and > one can normally find some unified clients to communicate on more than one > service. Agreed on that. The whole Claws Mail team is on IRC daily, communicating about dev topics as well as personal ones, we're a team, most of us are friends. It's sync and async ways of communicating, and we have a channel archive. It's fast and lightweight, public and private, can be done from a phone even, what would we want more or different? Another thing to re-invent? ;-). IRC is probably (w/ email) one of the oldest communication ways I se and still happy w/ it, it does the work. Regards, > Sun, 7 May 2017 16:08:24 +0300 Alexandre Prokoudine > <alexandre.prokoud...@gmail.com> wrote: > > > On Sun, May 7, 2017 at 3:54 PM, gregory grey wrote: > > > > >>> Now, a person says "I'd like to suggest" and your reply is basically > > >>> "f*** off". > > >> > > >> It's an interesting way to interpret a simple 'no'. > > >> > > > > > > Turning tables much? You should interpret the number of developers on > > > the projects into reasons of it being so. > > > > Irrelevant. > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list -- wwp pgpCRJ_4hVwsh.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Point-and-click tool to create guides?
On Mon, 9 May 2016 21:30:48 +0100 C R <caj...@gmail.com> wrote: > What would be nice is a manual entry box for moving the measure tool > markers around (in the Tool Options for measure). This way you could type > in the exact value(s) you want, and use ctrl-click and alt-click to make > your markers how you like with better precision than the mouse pointer > allows. Right! Even ore because clicking the spot line (layer boundary, one-pixel wide line) is a bit difficult - but maybe it's just me. Regards, > On Mon, May 9, 2016 at 9:23 PM, wwp <subscr...@free.fr> wrote: > > > Hello C, > > > > > > On Mon, 9 May 2016 21:02:21 +0100 C R <caj...@gmail.com> wrote: > > > > > This is also sub-function of the measure tool. > > > To create a horizontal guide, place a marker on the spot, and ctrl-click > > it > > > To create a vertical guide, place a marker on the spot and alt-click it > > > > Nice too, thanks for the tip! :-) > > > > > > Regards, > > > > > On Mon, May 9, 2016 at 8:54 PM, Alexandre Prokoudine < > > > alexandre.prokoud...@gmail.com> wrote: > > > > > > > On Mon, May 9, 2016 at 10:47 PM, wwp wrote: > > > > > Hello there, > > > > > > > > > > > > > > > I wonder if the idea of a point-and-click tool to create guides could > > > > > be a good one? > > > > > > > > > > The idea there is to directly create guides with a minimum number of > > > > > clicks in order to speed up a production process. It is based upon my > > > > > (long, subjective and perfectible) experience w/ the Gimp 2.x. > > > > > > > > > > The way of doing it could be, for instance: in one click you pick the > > > > > create-guide tool from the side dock, then you click on the image: > > > > > it creates a horizontal or vertical guide at this click's x or y - > > > > > horizontal or vertical axis could be determined using ctrl or shift > > > > > modifier. Clicking in the margin (outside the layer boundary) could > > be > > > > > even more intuitive, up/down margin to create vertical guides, > > > > > left/right to create horizontal ones, still for instance. While > > moving > > > > > the mouse pointer with this tool, a "live" guide shadow could be > > > > > displayed, in order to provide a visual clue about the guide location > > > > > that you validate when you click to create it. > > > > > > > > > > Any thought? > > > > > > > > Just to make sure I get it right... > > > > > > > > Instead of > > > > > > > > 1. Hovering your mouse pointer over the ruler. > > > > 2. Clicking, dragging, and releasing the mouse button to create a new > > > > guide. > > > > > > > > ...you want > > > > > > > > 1. Hover your mouse pointer over the toolbox above the > > > > 'point-and-click tool' and click it. > > > > 2. Go to the location where you want a guide and use a modifier to > > > > create either vertical or horizontal (or both) guides. > > > > > > > > Unless I'm terribly mistaken, that's about the same amount of step in > > > > comparison to something that has been around for years :) You you get > > > > guide position preview too. > > > > > > > > Hmmm? :) > > > > > > > > Alex > > > > ___ > > > > gimp-developer-list mailing list > > > > List address:gimp-developer-list@gnome.org > > > > List membership: > > > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > > > List archives: https://mail.gnome.org/archives/gimp-developer-list > > > > > > > ___ > > > gimp-developer-list mailing list > > > List address:gimp-developer-list@gnome.org > > > List membership: > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > > List archives: https://mail.gnome.org/archives/gimp-developer-list > > > > -- > > wwp > > > > ___ > > gimp-developer-list mailing list > > List address:gimp-developer-list@gnome.org > > List membership: > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > List archives: https://mail.gnome.org/archives/gimp-developer-list -- wwp pgpFqX1UldKo3.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Point-and-click tool to create guides?
Hello Alexandre, On Mon, 9 May 2016 22:54:12 +0300 Alexandre Prokoudine <alexandre.prokoud...@gmail.com> wrote: > On Mon, May 9, 2016 at 10:47 PM, wwp wrote: > > Hello there, > > > > > > I wonder if the idea of a point-and-click tool to create guides could > > be a good one? > > > > The idea there is to directly create guides with a minimum number of > > clicks in order to speed up a production process. It is based upon my > > (long, subjective and perfectible) experience w/ the Gimp 2.x. > > > > The way of doing it could be, for instance: in one click you pick the > > create-guide tool from the side dock, then you click on the image: > > it creates a horizontal or vertical guide at this click's x or y - > > horizontal or vertical axis could be determined using ctrl or shift > > modifier. Clicking in the margin (outside the layer boundary) could be > > even more intuitive, up/down margin to create vertical guides, > > left/right to create horizontal ones, still for instance. While moving > > the mouse pointer with this tool, a "live" guide shadow could be > > displayed, in order to provide a visual clue about the guide location > > that you validate when you click to create it. > > > > Any thought? > > Just to make sure I get it right... > > Instead of > > 1. Hovering your mouse pointer over the ruler. > 2. Clicking, dragging, and releasing the mouse button to create a new guide. > > ...you want > > 1. Hover your mouse pointer over the toolbox above the > 'point-and-click tool' and click it. > 2. Go to the location where you want a guide and use a modifier to > create either vertical or horizontal (or both) guides. > > Unless I'm terribly mistaken, that's about the same amount of step in > comparison to something that has been around for years :) You you get > guide position preview too. > > Hmmm? :) Hah. Dragging from the rulers does exactly what I need, the feature already exists. Thanks!! Regards, -- wwp pgpWoR9GevvmV.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Point-and-click tool to create guides?
Hello there, I wonder if the idea of a point-and-click tool to create guides could be a good one? The idea there is to directly create guides with a minimum number of clicks in order to speed up a production process. It is based upon my (long, subjective and perfectible) experience w/ the Gimp 2.x. The way of doing it could be, for instance: in one click you pick the create-guide tool from the side dock, then you click on the image: it creates a horizontal or vertical guide at this click's x or y - horizontal or vertical axis could be determined using ctrl or shift modifier. Clicking in the margin (outside the layer boundary) could be even more intuitive, up/down margin to create vertical guides, left/right to create horizontal ones, still for instance. While moving the mouse pointer with this tool, a "live" guide shadow could be displayed, in order to provide a visual clue about the guide location that you validate when you click to create it. Any thought? Regards, -- wwp pgppyp74SH4Db.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] GIMP 2.9 XCF files and digiKam, gnome file browsers, etc
Hello Elle, On Sun, 3 Jan 2016 17:53:42 -0500 Elle Stone <ellest...@ninedegreesbelow.com> wrote: > Does anyone know of *any* image viewer that can display a thumbnail for GIMP > 2.9 XCF files? XnViewMP does. Regards, -- wwp pgpmcxeLLe_uD.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Export instead save directly
Hello Pavel, On Mon, 29 Feb 2016 22:21:49 +0100 pa...@pamsoft.cz wrote: > 2. Do you know some photo/image viewer which can display xcf files? I am not > aware of any. Maybe there is some, but it is not important at the moment. The > important message is, that poeple (I appologise to Alex for speaking on > behalf of other peaple than I am) usually don't want to store they images as > xcf. I bet most often they want to load their JPEG from their camera, make > some edits, color enhancemnts, etc. and SAVE it back as JPEG. That's all. [snip] XnView (MP version at least) does show xcf :-). Regards, -- wwp pgptvZTMo5O2k.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Export instead save directly
Hello, On Mon, 29 Feb 2016 19:31:00 + "A. da Mek" <a.da_m...@ufoni.cz> wrote: > > I still think that there should be a file->import as it's really hard to > tell people JPEG and PNG are not native to GIMP when it opens them just fine. > > > Yes, I had the same thought; the current system is asymmetric. If it is > insisted that non-xcf files cannot be saved and are exported instead, so they > shall be also only imported instead of opened. But when I can open a file, > then I expect that I am able also to save it. That's probably the real point. > OTOH, as the application can detect which format is being opened, and choose > automatically between opening of the native format and importing of other > formats, so maybe the best solution could be simply change the label from > "open" to "open or import". "open" is generic enough. "import" (if it exists besides "open") usually implies that you convert from a format that is not the format used internally or not the intended format for the application. "export" has the same meaning (but other direction). "save" is generic too. You can also think about other generic terms, like "load" and "store". Regards, -- wwp pgp03NoDZM3yl.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Export instead save directly
Hello, On Mon, 29 Feb 2016 13:15:49 + C R <caj...@gmail.com> wrote: > Also, the old way of forcing a user to bypass a warning message every time > he/she wants to save to the loaded format is (workflow-wise) much worse > than just learning the "Export" hotkey imho. Also, it's clearly not a > "flaw"; it's not broken, it's working as intended. > If there were a vote, I'd vote to keep it the new way (and I process a very > very high volume of product photos with GIMP). I reckon people are more > likely to complain about a change in UI conventions than praise it... so > here's one praising it. How many theoretical user votes is that worth? ;) That's it! I'm a long-time user of Gimp (this is not an excuse for being right when arguing :-P), and even if I got hurt twice or thrice with the Save as vs Export change, I quickly decided to think about the good reasons for this change, accepted them (and changed the hotkey to export with Ctrl S - hah, I quite never save as .xcf when I process photos, I only use the .xcf storing when I work on graphical constructions). To bring my 2 cents WRT the exchange between Alexandre and A. da Mek, I think that it's very different/difficult to get feedback from users when you don't sell a product more or less directly and distribute it a passive way (downloads on a website for instance). Alexandre is right (and I well know this, being part of commercial and open source projects for more than 15 years), generally the only guys you hear are the ones who make more noise than the silent ones; and the noisy guys are most of the time the angry ones, specifically the ones with a expansive character and an egocentric/narrow way of thinking. A pain in the *ss to deal w/ user support sometimes, a bigger pain when users come from Windows userland (or other kind of dumb users). I saw the Save as vs Export thing discussed in many places but it has been well explained and every time it made sense to people who were asking why, it's just difficult for some guys to understand that the file format in GIMP is xcf and that jpg/tif/etc. are exports, exactly like in *office, where odt is the file format and PDF an export for printing/exanging. The other very important (to my eyes) point when dealing w/ usability is something that may shut the mouth of angry birds: "people" (including me) were complaining about the multiple-window GUI scheme in Gimp 2.6, and for years. Gimp developers finally added a single-window GUI scheme. Isn't that quite a compromise and acceptation from them to (optionally) comply with "standards" and user requests when they make sense? Regards, > On Mon, Feb 29, 2016 at 12:27 PM, Alexandre Prokoudine < > alexandre.prokoud...@gmail.com> wrote: > > > On Mon, Feb 29, 2016 at 3:20 PM, A. da Mek wrote: > > >>> How can we know how many of them there is, if they simply downgrade to > > >>> 2.6 > > >>> and do not bother to discuss it somewhere? > > >> > > >> > > >> One of the first things I learned when I was in the marketing and PR > > >> business is that unhappy customers do complain. A lot. > > > > > > > > > A producer of a commercial product gets the complaints from the customers > > > who paid for that product and are nor satisfied with it. He does not > > know if > > > there are any customers who were aware of the flaws of his product > > already > > > before they bought it, and so they simply decided to buy another product. > > > > > > > This is simply not how it really works. > > > > Alex > > ___ > > gimp-developer-list mailing list > > List address:gimp-developer-list@gnome.org > > List membership: > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > List archives: https://mail.gnome.org/archives/gimp-developer-list > > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list -- wwp pgp1gwsR3IEu9.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Export to JPEG dialog: setting default subsampling
Hello, On Sat, 16 Jan 2016 19:53:52 +0100 wwp <subscr...@free.fr> wrote: > On Sat, 16 Jan 2016 17:23:04 +0100 wwp <subscr...@free.fr> wrote: > > > (using Gimp 2.8.14 in Linux) > > > > Once, I've set the default JPEG export options to use the 4:4:4 > > subsampling value: I've set the export to JPEG dialog options to what I > > wanted then clicked the "save defaults" button. > > > > When I export images to JPEG, I notice that the factory value is > > proposed (4:4:2 horizontal) in the dialog, instead of the default value > > I've set, other settings do respect my wishes. Is this behaviour > > expected? > > > > FYI, the 'use quality settings from original image' checkbox is unset > > here, and clicking the "load defaults" does set the expected 4:4:4 value. > > Hmm it seems to be: https://bugzilla.gnome.org/show_bug.cgi?id=747054, > sorry for the noise! In addition to my own noise, I presume there is no other option to set the default subsampling but editing the sources? Regards, -- wwp pgpz1gfIX3d93.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Export to JPEG dialog: setting default subsampling
On Sat, 16 Jan 2016 17:23:04 +0100 wwp <subscr...@free.fr> wrote: > (using Gimp 2.8.14 in Linux) > > Once, I've set the default JPEG export options to use the 4:4:4 > subsampling value: I've set the export to JPEG dialog options to what I > wanted then clicked the "save defaults" button. > > When I export images to JPEG, I notice that the factory value is > proposed (4:4:2 horizontal) in the dialog, instead of the default value > I've set, other settings do respect my wishes. Is this behaviour > expected? > > FYI, the 'use quality settings from original image' checkbox is unset > here, and clicking the "load defaults" does set the expected 4:4:4 value. Hmm it seems to be: https://bugzilla.gnome.org/show_bug.cgi?id=747054, sorry for the noise! Regards, -- wwp pgpjdgJkACTSw.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] ANNOUNCE: GIMP 2.8.12 released
Hello Michael, On Tue, 26 Aug 2014 00:10:15 +0200 Michael Natterer mi...@gimp.org wrote: Hi, GIMP 2.8.12 has been released. This is a bugfix release in the stable 2.8 series, no new features were added. For a complete list of changes since 2.8.10 please see the Changes section below. Also see the release notes of the 2.8 series at http://www.gimp.org/release-notes/gimp-2.8.html Happy GIMPing, --Mitch Download GIMP 2.8.12 is available from: http://downloads.gimp.org/pub/gimp/v2.8/ [snip] Cool! But isn't it http://download.gimp.org/pub/gimp/v2.8/ (s/downloads/download) ? Regards, -- wwp pgp3x24Oj2SOm.pgp Description: OpenPGP digital signature ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] ANNOUNCE: GIMP 2.8.12 released
Hello,
On Tue, 26 Aug 2014 09:02:55 +0200 Michael Natterer mi...@gimp.org wrote:
On Tue, 2014-08-26 at 08:39 +0200, wwp wrote:
Hello Michael,
On Tue, 26 Aug 2014 00:10:15 +0200 Michael Natterer mi...@gimp.org wrote:
GIMP 2.8.12 is available from:
http://downloads.gimp.org/pub/gimp/v2.8/
[snip]
Cool!
But isn't it http://download.gimp.org/pub/gimp/v2.8/ (s/downloads/download)
?
Argh, of course :)
It's indeed http://download.gimp.org/pub/gimp/v2.8/
Sorry for the typo!
Strangely, the 2.8.12's configure fails with my python 2.6 (CentOS6,
which is conform to the requirement: Python = 2.5.0), whereas 2.8.10
finds it as expected.
See:
[snip]
checking for a Python 2 interpreter with version = 2.5.0... none
configure: error:
*** Could not find Python 2 (2.5.0 or newer).
*** Please install it, or skip building the python scripting extension by
*** passing --disable-python to configure (but then you will not be able
*** to use scripts for GIMP that are written in Python).
whereas with 2.8.10:
checking for a Python interpreter with version = 2.5.0... python
checking for python... /usr/bin/python
checking for python version... 2.6
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.6/site-packages
checking for python extension module directory...
${exec_prefix}/lib64/python2.6/site-packages
checking for headers required to compile python extensions... found
checking for PYGTK... yes
checking for pygtk-codegen-2.0... /opt/gimp-2.8/bin/pygtk-codegen-2.0
checking for pygtk defs... /opt/gimp-2.8/share/pygtk/2.0/defs
Note that both python and python2.6 are on PATH.
Setting PYTHON env. var. doesn't help, but I usually doesn't set it.
The following python line causes a wrong check when python version is 2.x:
sys.exit(sys.version_info.major != 2 or sys.hexversion minverhex)
It ends up with a wrong logic, see:
[snip]
+ test set = set
+ :
+ enableval=yes
+ test xyes '!=' xno
+ enable_python=yes
+ test -n ''
+ printf '%s\n' 'configure:22496: checking for a Python 2 interpreter with
version = 2.5.0'
+ printf %s 'checking for a Python 2 interpreter with version = 2.5.0... '
checking for a Python 2 interpreter with version = 2.5.0... + false
+ for am_cv_pathless_PYTHON in python python2 python2.7 python2.6 python2.5
python2.4 python2.3 python2.2 python2.1 python2.0 none
+ test python = none
+ prog='import sys
# split strings by '\''.'\'' and convert to numeric. Append some zeros
# because we need at least 4 digits for the hex conversion.
# map returns an iterator in Python 3.0 and a list in 2.x
minver = list(map(int, '\''2.5.0'\''.split('\''.'\''))) + [0, 0, 0]
minverhex = 0
# xrange is not present in Python 3.0 and range returns an iterator
for i in list(range(0, 4)): minverhex = (minverhex 8) + minver[i]
sys.exit(sys.version_info.major != 2 or sys.hexversion minverhex)'
+ echo 'configure:22513: python -c import' sys '#' split strings by ''\''.'\'''
and convert to numeric. Append some zeros '#' because we need at least 4 digits
for the hex conversion. '#' map returns an iterator in Python 3.0 and a list in
2.x minver = 'list(map(int,' ''\''2.5.0'\''.split('\''.'\'')))' + '[0,' 0, '0]'
minverhex = 0 '#' xrange is not present in Python 3.0 and range returns an
iterator for i in 'list(range(0,' '4)):' minverhex = '(minverhex' '' '8)' +
'minver[i]' 'sys.exit(sys.version_info.major' '!=' 2 or sys.hexversion ''
'minverhex)'
+ ac_status=1
+ echo 'configure:22516: $? = 1'
+ exit 1
+ for am_cv_pathless_PYTHON in python python2 python2.7 python2.6 python2.5
python2.4 python2.3 python2.2 python2.1 python2.0 none
+ test python2 = none
+ prog='import sys
# split strings by '\''.'\'' and convert to numeric. Append some zeros
# because we need at least 4 digits for the hex conversion.
# map returns an iterator in Python 3.0 and a list in 2.x
minver = list(map(int, '\''2.5.0'\''.split('\''.'\''))) + [0, 0, 0]
minverhex = 0
# xrange is not present in Python 3.0 and range returns an iterator
for i in list(range(0, 4)): minverhex = (minverhex 8) + minver[i]
sys.exit(sys.version_info.major != 2 or sys.hexversion minverhex)'
+ echo 'configure:22513: python2 -c import' sys '#' split strings by
''\''.'\''' and convert to numeric. Append some zeros '#' because we need at
least 4 digits for the hex conversion. '#' map returns an iterator in Python
3.0 and a list in 2.x minver = 'list(map(int,'
''\''2.5.0'\''.split('\''.'\'')))' + '[0,' 0, '0]' minverhex = 0 '#' xrange is
not present in Python 3.0 and range returns an iterator for i in
'list(range(0,' '4)):' minverhex = '(minverhex' '' '8)' + 'minver[i]'
'sys.exit(sys.version_info.major' '!=' 2 or sys.hexversion '' 'minverhex)'
+ ac_status=1
+ echo 'configure:22516: $? = 1'
+ exit 1
+ for am_cv_pathless_PYTHON in python python2 python2.7 python2.6 python2.5
python2.4 python2.3 python2.2 python2.1 python2.0 none
+ test python2.7 = none
+ prog='import sys
# split strings
[Gimp-developer] Lines in Text area are vertically reversed
Hello there, occasionnaly, I notice a strange behaviour in a text area: If I paste in: AAA BBB CCC They will display in vertical reverse order (CCC first). Moreover, when I move the cursor in the edit zone (whatever it's directly in the editor widget or the text area itself, the cursor up/down keys behave as down/up. If this is somewhat consistent with the reverse display order but totally unexpected for a European type style (left to right, top to bottom). Is that something I twisted or missed? Or a bug? Gimp 4.8.4, compiled from the source, GNU/Linux 64bit. (I also noticed a crash when pasting text in the text area, but I'll report this on the bug tracker) Regards, -- wwp signature.asc Description: PGP signature ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Translate the Windows installer packages of GIMP 2.8.x
Hello Michael, On Sat, 13 Oct 2012 23:09:47 +0200 Michael Schumacher schum...@gmx.de wrote: Hi, some of you might have noticed that the Windows installers for GIMP 2.8.x, available from http://gimp-win.sourceforge.net, offer a few more language options than previous releases - Deutsch, English, Italiano and Slovenski. [snip] I'd like to contribute by providing the FR(ench) one, if no-one is already working on it. Is there a deadline for an incoming release, BTW? Regards, -- wwp signature.asc Description: PGP signature ___ 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
Hello Akira, On Mon, 23 Jul 2012 10:15:41 -0700 (PDT) Akira Tanaka artfoundr...@yahoo.com wrote: To all the developers of GIMP software... In the five years that I've used your program for my own creative purposes, I've dealt with some of the good aspects of GIMP and the negative aspects of it as well. The variety in brushes was good and the option to create animated GIFs with ease is a nice addition as well. However, there have been many negative aspects that have given me so much grief with this program. I've dealt with the instability of tablet devices being added on to my computer when I use GIMP. The times that GIMP has crashed and so many irretrievable hours of work lost only fueled my rage against this program. But after accessing an already usable file only to get an error message that doesn't make any sense, that was it. That was the straw that broke the camel's back. After five years of putting up with this mediocre excuse for a software, it's time for me to hold my hands high and say enough is enough. I feel like I've been put through something and this is the breaking point. A software that crashes on you and then has the audacity to refuse a direct order makes for a truly negative experience. This is it. I've had it. I will never use GIMP software again for as long as I live. I know you have some sort of bureaucracy set up to review letters from anonymous users. There is a chance you will reject this letter but if that's the case, I'm willing to give you these parting words. GIMP is, without a doubt, the most unreliable, poorly programmed, pathetic excuse for a software program ever conceived by a human being. That is all. If you took the time to read this, you have my thanks. If you just carelessly rejected this without even looking into the letter, you can all go fuck yourselves. Maybe you could: - have reported way sooner your crash experiences, (making more detailed reports, getting support and probably getting fixes as well!), - have complained sooner about the Gimp in a general manner (5 years? woooh!), - adapted (and improved) your work habits (save your work, save frequently if you know that the software is unstable), - changed for another piece of software earlier. You surely faced issues while using the Gimp. You could have done a better work yourself, for your own sake and by contributing to the Gimp community way before going nuts like this and sending a complaint that now almost lose credibility. Regards, -- wwp signature.asc Description: PGP signature ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] gimp 2.8 prohibitively slow
Hello Michael, Aaron, On Thu, 19 Jul 2012 06:34:29 + (UTC) Michael Grosberg grosberg.mich...@gmail.com wrote: Aaron Paden aaronbpaden at gmail.com writes: So I mostly use MyPaint, but I'd like to be able to do some things in gimp, too. But gimp is way too slow on this computer. Especially trying to open large images like MyPaint encourages, I'll have to run to another tty to try and kill the process so I can continue to use my computer. I've got an old Pentium 4 with only about half a gig of RAM. A bit behind the times, but especially on Linux it's generally fast enough to get the job done. Is there anything I can do to help improve performance? I don't have much experience. I doubt I could write anything any faster. But maybe I can do something to help identify bottlenecks? Anything I can do to help, I'm game. You know, when you have a system that's probably 12 years old, it's good form to start by saying that you have one instead of complaining that an application developed in 2012 is prohibitively slow. For example, you could use the subject line running Gimp on an old PC. Just saying. That's right, even though when attempting to process image/data files that are, say, modern. The OP didn't mention precisely how big they are (trying to open large images like MyPaint encourages), but I presume they are way bigger than image sizes that were conventional in the times P4 + 512Go RAM were common. How big are they, Aaron? Regards, -- wwp signature.asc Description: PGP signature ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] RFE: single window mode: always show tab
Hello there, I'm plugging in here a discussion started on the bug tracker, see https://bugzilla.gnome.org/show_bug.cgi?id=667168 Martin, I understand your point about making the default behaviour the right one without an option. Let me explain what's wrong to the current way tabs are managed, IMHO. See the current two situations with tabs in Gimp 2.7: 1) you have only one image opened. No tab is shown. 2) you have two or more images opened, several tabs are shown. I'm not asking why no tab is shown in situation 1), this is pretty obvious. Switching from situation 1) to 2) inserts what we can call a tab bar (tab widgets) and stretches down the image view to a narrower size. What the user sees is a clunky, chaning UI layer, widgets are inserted (might flicker a bit) and the global working area is rearranged - possible without respect to the visual arrangements made by the user. Now switching from situation 2) to 1): same notes as above. Plus: if you were closing another tab but the current one, the current view will be resized (stretched up), what you now see is not what you were seeing before closing that other tab. This is even more sensible when the image fills the window. IMO all this is not friendly, I dislike flickering and self-rearranging stuff, and most of all: it makes me feel that the visual working area is *unstable* and not respecting my view settings. I know other applications (firefox, galeon) who made that behaviour optional, allowing to always see a tab even if only one tab is opened. I hope I've explained more clearly.. :-). Regards, --- Comment #1 from Martin Nordholts ense...@gmail.com 2012-01-04 05:26:47 UTC --- Hi and thanks for the feedback! Adding an option for this would be way more annoying than the current behavior. GIMP should simply do the right thing by default. GIMP should work for the user, not vice versa (which would be the case if an option was needed so that a human could tell GIMP how to behave sanely). Exactly what problem is it that you see? That's a discussion for the gimp-developer mailing list though, not a bug tracker. -- wwp signature.asc Description: PGP signature ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
