Re: [Gimp-developer] gimp-developer-list Digest, Vol 54, Issue 22

[mailrea...@juno.com]

Thank you!

-- Original Message --
From: gimp-developer-list-requ...@gnome.org
To: gimp-developer-list@gnome.org
Subject: gimp-developer-list Digest, Vol 54, Issue 22
Date: Mon, 28 Mar 2016 12:00:01 +

Send gimp-developer-list mailing list submissions to
 gimp-developer-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
 https://mail.gnome.org/mailman/listinfo/gimp-developer-list
or, via email, send a message with subject or body 'help' to
 gimp-developer-list-requ...@gnome.org

You can reach the person managing the list at
 gimp-developer-list-ow...@gnome.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gimp-developer-list digest..."


Today's Topics:

   1. Re:  re. suggestions (mailrea...@juno.com)
   2. Re:  re. suggestions (C R)


--

Message: 1
Date: Sun, 27 Mar 2016 20:19:43 GMT
From: "mailrea...@juno.com" 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] re. suggestions
Message-ID: <20160327.131943.2561...@webmail03.vgs.untd.com>
Content-Type: text/plain; charset=ISO-8859-1


Subject: re. suggestions
Date: Sun, 27 Mar 2016 19:32:44 GMT

To C.R.:  I think your proposed change to the download page (adding"93 MB" just 
above the download button for GIMP for Windows) is easy, simple, and clear.  I 
recommend it highly!
To Alex:  What do I suggest you do about it?  I thought that the features of 
the latest version of Photoshop could be listed and tried, and any features 
that anyone likes in any other programs, as well as original ideas, and that 
GIMP could be presented so that even the relatively inexperienced (like me!) 
could easily and quickly understand that those useful features are available, 
what they are, and how to find and conveniently use them.  I wasn't specific 
because I certainly don't know everything about either well-known program!  
I've found a 653-page GIMP user manual, which took forever to download on this 
borrowed old Mac laptop.  I was in too much of a hurry to read more than about 
a page of it.  I couldn't find a link that would allow me to copy and save the 
manual file so I might be able to look at it later, after I have to return the 
laptop and when I can't get an Internet connection. (Since the laptop got wet 
(before I borrowed it), the screen and image files appear 
 in very startling and frequently changing colors!  This makes it even more of 
a challenge to get good results from image editing very quickly.)

Places You'll See
38 Stunning Photos of Norwegian's Biggest, Baddest Cruise Ship
http://thirdpartyoffers.juno.com/TGL3131/56f8409e22280409d48f4st02vuc


--

Message: 2
Date: Sun, 27 Mar 2016 23:26:14 +0100
From: C R 
To: "mailrea...@juno.com" 
Cc: gimp-developer 
Subject: Re: [Gimp-developer] re. suggestions
Message-ID:
 
Content-Type: text/plain; charset=UTF-8

>
> To C.R.:  I think your proposed change to the download page (adding"93 MB"
> just above the download button for GIMP for Windows) is easy, simple, and
> clear.  I recommend it highly!
>

We used to list the file size on the download buttons. Apparently the
feature didn't get added to the new web layout (which is much better than
our old one in almost every way possible) I'm sure it's just an oversight.


To Alex:  What do I suggest you do about it?  I thought that the features
> of the latest version of Photoshop could be listed and tried, and any
> features that anyone likes in any other programs, as well as original
> ideas, and that GIMP could be presented so that even the relatively
> inexperienced (like me!) could easily and quickly understand that those
> useful features are available, what they are, and how to find and
> conveniently use them.


Where on the Adobe website does it list the features of Photoshop compared
to GIMP?
GIMP is not made to be competition with Photoshop, and conversely,
Photoshop is not made to be in competition with GIMP. They are both highly
sophisticated image editors, but they are different programs. They are
simply built for similar purposes.This is why you will not see a
feature-comparison done on either website.

Since you are new to both programs, I recommend GIMP. The time you would
spend learning Photoshop is about the same as the time it takes to learn
GIMP.

For your effort, get these advantages:
1. You get a software application that will dutifully serve your
photo-editing needs, for free, for both professional and hobbyist uses
without limitation.
2. You get free updates, and will never have to pay any money for GIMP.
3. You will never be bothered by license keys that run out, or other
software imposed DRM protection that gets in the way of your work.
4. You will be able to work on any Desktop OS you choose, be it Linux, Mac,
or Windows, giving you the freedom to choose your working environment and

Re: [Gimp-developer] gimp-developer-list Digest, Vol 52, Issue 20

[John]

Thanks Michael, that's got to be it.

On 01/18/2016 08:00 PM, gimp-developer-list-requ...@gnome.org wrote:

Send gimp-developer-list mailing list submissions to
gimp-developer-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
or, via email, send a message with subject or body 'help' to
gimp-developer-list-requ...@gnome.org

You can reach the person managing the list at
gimp-developer-list-ow...@gnome.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gimp-developer-list digest..."


Today's Topics:

1.  gimp 2.9 build on linux, now jpeg, tiff,etc are unknown
   file types (John)
2. Re:  gimp 2.9 build on linux, now jpeg, tiff, etc are unknown
   file types (Michael Schumacher)


--

Message: 1
Date: Mon, 18 Jan 2016 18:57:30 +0800
From: John 
To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] gimp 2.9 build on linux, now jpeg, tiff,  etc
are unknown file types
Message-ID: <569cc51a.20...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed

I've been using gimp 2.9.2 and 2.9.3, building from a git clone without
issues, using a subdirectory of my home for the install location.

I've now moved the install location to /usr/local, and the autogen, make
and make install steps complete without errors.   Note:  I now use sudo
make install in order to add files to /usr/local, before I simply
invoked make install to send files to my home/gimp subdirectory.

However the new build of gimp does not recognize common image types such
as jpeg, tiff, etc.  During the autogen step, I get output:
/
/

 /checking for TIFFReadScanline in -ltiff... yes/
 /checking tiffio.h usability... yes/
 /checking tiffio.h presence... yes/
 /checking for tiffio.h... yes/
 /checking for jpeg_destroy_decompress in -ljpeg... yes/
 /checking for jpeglib.h... yes/
 /checking for jpeg_save_markers in -ljpeg... yes

 ...

 config.status: creating plug-ins/file-jpeg/Makefile
 config.status: creating plug-ins/file-psd/Makefile
 config.status: creating plug-ins/file-sgi/Makefile
 config.status: creating plug-ins/file-tiff/Makefile

 /

which looks hopeful, but at the end there's no mention of jpg or tiff
file support (just JPEG2000),

 /Building GIMP with prefix=/usr/local, datarootdir=${prefix}/share//
 //Desktop files install into ${datarootdir}//
 //
 //Extra Binaries://
 //  gimp-console:yes//
 //
 //Optional Features://
 //  Language selection:  yes//
 //
 //Optional Plug-Ins://
 //  Ascii Art:   no (AA library not found)//
 //  Ghostscript: no (Ghostscript library not found)//
 //  Help Browser:no (WebKit not found)//
 //  JPEG 2000:   yes//
 //  MNG: yes//
 //  OpenEXR: yes//
 //  PDF (import):Using PostScript plug-in (libpoppler-glib
 not found)//
 //  PDF (export):yes//
 //  Print:   yes//
 //  Python 2:yes//
 //  Script-Fu:   yes//
 //  SVG: yes//
 //  TWAIN (MacOS X): no//
 //  TWAIN (Win32):   no//
 //  Webpage: no (WebKit not found)//
 //  WMF: no (libwmf not found)//
 //  X11 Mouse Cursor:yes//
 //  XPM: yes/

Shared libraries for tiff and jpeg exist on my system (as I said, gimp
2.9 worked when the install target was my home directory).

 /ldconfig -p | grep tiff/
 /libtiffxx.so.5 (libc6,x86-64) =>
 /usr/lib/x86_64-linux-gnu/libtiffxx.so.5/
 /libtiffxx.so (libc6,x86-64) =>
 /usr/lib/x86_64-linux-gnu/libtiffxx.so/
 /libtiff.so.5 (libc6,x86-64) =>
 /usr/lib/x86_64-linux-gnu/libtiff.so.5/
 /libtiff.so.5 (libc6) => /usr/lib/i386-linux-gnu/libtiff.so.5/
 /libtiff.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libtiff.so/


There must be a simple explanation, I just can't think of it!




--

Message: 2
Date: Mon, 18 Jan 2016 12:05:01 +0100
From: Michael Schumacher 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] gimp 2.9 build on linux, now jpeg, tiff,
etc are unknown file types
Message-ID: <569cc6dd.3080...@gmx.de>
Content-Type: text/plain; charset=windows-1252

Am 18.01.2016 um 11:57 schrieb John:


There must be a simple explanation, I just can't think of it!

Check where you are pointing GIMP to find its plug-ins. This is in the
preferences.




___
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

Re: [Gimp-developer] gimp-developer-list

[Elle Stone]

On 01/11/2016 12:07 PM, Alexandre Prokoudine wrote:

11 янв. 2016 г. 20:00 пользователь "Elle Stone" написал:


Well, maybe, but I just did git pull, and recompiled, with the following

errors:

Did you rerun autogen.sh?


No. But I just did rerun autogen.sh, with the same result.

Elle

___
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-developer-list

[Alexandre Prokoudine]

11 янв. 2016 г. 20:00 пользователь "Elle Stone" написал:

> Well, maybe, but I just did git pull, and recompiled, with the following
errors:

Did you rerun autogen.sh?

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

Re: [Gimp-developer] gimp-developer-list

[Elle Stone]

On 01/11/2016 10:10 AM, Alexandre Prokoudine wrote:

On Mon, Jan 11, 2016 at 6:10 PM, Elle Stone wrote:

On 01/11/2016 08:23 AM, Americo Gobbo wrote:


Hi all,
I am trying compile the last git master, today... but I find these errors
com gimp compile:

$: ~/devel/gimp-2.9$ make -j4
make  all-recursive
`/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
ln -s ../../icons/Symbolic/12/gimp-default-colors.png
12/gimp-default-colors.png
ln: failed to create symbolic link ‘12/gimp-default-colors.png’: File
exists
make[3]: *** [12/gimp-default-colors.png] Error 1
make[3]: Leaving directory
`/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jag/devel/gimp-2.9/icons'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jag/devel/gimp-2.9'
make: *** [all] Error 2



I encountered similar errors.


Benoit has already fixed this in master.


Well, maybe, but I just did git pull, and recompiled, with the following 
errors:


/usr/bin/install: cannot stat ‘./12/gimp-default-colors.png’: No such 
file or directory

Makefile:1086: recipe for target 'install-icons12DATA' failed
make[3]: *** [install-icons12DATA] Error 1
make[3]: Leaving directory 
'/home/elle/code/gimpdefault/build/gimp/icons/Symbolic-Inverted'

Makefile:1408: recipe for target 'install-am' failed
make[2]: *** [install-am] Error 2
make[2]: Leaving directory 
'/home/elle/code/gimpdefault/build/gimp/icons/Symbolic-Inverted'

Makefile:547: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/elle/code/gimpdefault/build/gimp/icons'
Makefile:718: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1

Elle


___
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-developer-list

[Alexandre Prokoudine]

On Mon, Jan 11, 2016 at 6:10 PM, Elle Stone wrote:
> On 01/11/2016 08:23 AM, Americo Gobbo wrote:
>>
>> Hi all,
>> I am trying compile the last git master, today... but I find these errors
>> com gimp compile:
>>
>> $: ~/devel/gimp-2.9$ make -j4
>> make  all-recursive
>> `/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
>> ln -s ../../icons/Symbolic/12/gimp-default-colors.png
>> 12/gimp-default-colors.png
>> ln: failed to create symbolic link ‘12/gimp-default-colors.png’: File
>> exists
>> make[3]: *** [12/gimp-default-colors.png] Error 1
>> make[3]: Leaving directory
>> `/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/home/jag/devel/gimp-2.9/icons'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/jag/devel/gimp-2.9'
>> make: *** [all] Error 2
>
>
> I encountered similar errors.

Benoit has already fixed this in master.

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

Re: [Gimp-developer] gimp-developer-list

[Elle Stone]

On 01/11/2016 08:23 AM, Americo Gobbo wrote:

Hi all,
I am trying compile the last git master, today... but I find these errors
com gimp compile:

$: ~/devel/gimp-2.9$ make -j4
make  all-recursive
`/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
ln -s ../../icons/Symbolic/12/gimp-default-colors.png
12/gimp-default-colors.png
ln: failed to create symbolic link ‘12/gimp-default-colors.png’: File exists
make[3]: *** [12/gimp-default-colors.png] Error 1
make[3]: Leaving directory
`/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jag/devel/gimp-2.9/icons'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jag/devel/gimp-2.9'
make: *** [all] Error 2


I encountered similar errors.


___
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] gimp-developer-list

[Americo Gobbo]

Hi all,
I am trying compile the last git master, today... but I find these errors
com gimp compile:

$: ~/devel/gimp-2.9$ make -j4
make  all-recursive
make[1]: Entering directory `/home/jag/devel/gimp-2.9'
Making all in m4macros
make[2]: Entering directory `/home/jag/devel/gimp-2.9/m4macros'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/jag/devel/gimp-2.9/m4macros'
Making all in cursors
make[2]: Entering directory `/home/jag/devel/gimp-2.9/cursors'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/jag/devel/gimp-2.9/cursors'
Making all in icons
make[2]: Entering directory `/home/jag/devel/gimp-2.9/icons'
Making all in Color
make[3]: Entering directory `/home/jag/devel/gimp-2.9/icons/Color'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/jag/devel/gimp-2.9/icons/Color'
Making all in Symbolic
make[3]: Entering directory `/home/jag/devel/gimp-2.9/icons/Symbolic'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/jag/devel/gimp-2.9/icons/Symbolic'
Making all in Symbolic-Inverted
make[3]: Entering directory
`/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
ln -s ../../icons/Symbolic/12/gimp-default-colors.png
12/gimp-default-colors.png
ln: failed to create symbolic link ‘12/gimp-default-colors.png’: File exists
make[3]: *** [12/gimp-default-colors.png] Error 1
make[3]: Leaving directory
`/home/jag/devel/gimp-2.9/icons/Symbolic-Inverted'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/jag/devel/gimp-2.9/icons'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jag/devel/gimp-2.9'
make: *** [all] Error 2
$:~/devel/gimp-2.9$ git pull -r
Current branch master is up to date.


___
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

Re: [Gimp-developer] gimp-developer-list Digest, Vol 26, Issue 23

[Thomas W]

Hi Marc, Michael

> New option to the fuzzy select tool:  stop matching pixels at pixels
which are
> already selected, or something similar.

Great idea. +1.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 26, Issue 10

[Thomas W]

Hi DeVont, thanks for your suggestions & interest in contribution.

I'm not really a GIMP developer and am definitely not familiar with the
codebase, but I'm deeply familiar with software engineering/ re-engineering
& I'll just give you a few comments on first principles.

> 1. gimp/libgimpmath/gimpmathtypes.h (file in
> question:gimp/libgimpmath/gimpmatrix.h(c))
>
> This file declares math structures that gimp uses like vectors and
> matrices. The GimpMatrix structure come in 2X2, 3X3 and even 4X4 versions.
> Each matrix is a 2Dimensional gdouble array with the appropriate amount of
> elements to span the NXN matrix.I believe this data structure is used for
> computation during image editing. There are functions handling
> comparisons, identities, transformations, rotations, translations and
> various other matrix operations.
>
> Possible changes: I believe the declaration of 3 special kinds of gimp
> matrices can be generalized to a struct (or class) that holds and defines
> an NXN matrix.

Generalizing these structures, would almost certainly make them slower.
While in peripheral areas that might be fine, I do not think GIMP users
wish to lose performance on matrix-based image transformations.

Neither am I aware that there could ever be a need for matrices larger than
4x4.

So, I probably recommend against pursuing #1.


> 2. gimp/app/core/gimpcontainer.h
> This class contains a data structure that is used to store different
things about the
> various objects in gimp. It works hand and hand with the GimpObject class.
> This class uses what I believe to be some form of tree or heap structure.
The
> class refers to add, remove, reorder, and getChild functions that are
defined
> across the class. The gimp.h code uses the GimpContainer class pointers
for everything
> from fonts, to documents, to displays. As this data structure is used with
> GimpObject (which controls a large amount of functionality in gimp) and is
> heavily referenced in the gimp.h file, optimizing this class could go a
long way in
> optimizing the code.

This area is probably more productive for investigation. You will need to
take some measurements/ benchmarks, to verify whether your changes are
delivering an actual performance improvement -- and by how much.

If you document the number of calls into this data structure/site, measure
performance beforehand, trial various changes, measure & document
performance from each version, write the results up formally and submit
code (if any) you will have completed your assignment fully.

I am not assuming that you will be able to improve performance, this may be
quite possible but even measuring & investigating thoroughly and coming to
the well-supported conclusion that you can't, would be a very competent
completion of your assignment.

> If we decrease the amount of time to ?reorder? the tree, then we decrease
the amount of time
> several other objects take to be initialized and added to the tree.

Well, it sounds quite plausible!  But only the measurements can tell.


> 3. gimp/libgimpmath/gimpvector.h(c)
> The GimpVector data structure keeps track of axis orientations and
lengths.
> I believe this is used in the various drawing tools. I also believe the
> automated shapes functions may use it for drawing polygons. The vector
data
> structure is a structure that holds four gdouble variables that are
> separately declared (gdouble x, y, z, w for the 4axis vector for example).
> There are three versions of the gimp vector: 2axis, 3axis, and 4axis. A
potential change to
> GimpVector could be altering the way that it is stored like we plan to
> change the GimpMatrix. This means making a streamlined generalized vector
that can be of
> dimension N.

I didn't like the GimpMatrix idea, due to reduced efficiency of
very-heavily used code. I expect the GimpVector may also be quite heavily
used -- perhaps less so than GimpMatrix, but I would have to be convinced
it was not performance-critical.

"Unrolled loops" -- and thus separate size-specific implementations, as per
the existing code -- are the best design choice for performance-critical
code.

Implementing a variable-length vector/list will, I expect, be vastly slower
than using a fixed-size struct or array. Structs and arrays are much more
efficient to allocate & de-reference.. Perhaps comparing such codes on a
testbed might give you a better idea/assessment of the potential relative
performance?

IN CONCLUSION:

It's great that your group is interested & willing to challenge yourself,
by taking a look at some serious large-scale software.

I think #2 (GimpContainer/ the heap) sounds like the most plausible area
for investigation & optimization. Make sure you measure & benchmark in a
reliable way (warm-up first, # of iterations, etc) -- you may need to write
some scripts or support code to enable this.

Be sure to write up all your initial measurements, different approaches,
results & conclusions.

Good luck!

Re: [Gimp-developer] gimp-developer-list Digest, Vol 26, Issue 7

[Thomas W]

Hi people, I agree with Akkana.

"Export..." and "Export to" have poor User Interface- clarity. They don't
mentally distinguish very well, as I reported on the GIMP bugtracker it's
easy & common to select the wrong one since the process to distinguish them
involves too much mental negation.

> For one thing, I'm still confused about the difference between Export...
and Export to
> -- they seem to do the same thing even though one has a ... and the other
doesn't, they
> have different shortcuts, and one of them isn't always available.

Part of the problem is how the menu-items are labelled (especially when no
file is selected, this is confusing), part of the problem may be how the
menu-items are ordered.

Cognitively it really doesn't seem to be good design.

> And I can never remember in any given session which images can use
> Overwrite versus which ones need an Export... or Export to, so I no
> longer trust any save/export shortcut to be the right one, and
> almost always end up going to the menus instead.

My position (and I'm pretty sure I'm objective here) is that even looking
at the menu, things are less than 100% obvious.
--

On another note, having some working shortcuts in the "Close" dialog to
Discard is great. Perhaps even better would be, to enable these to work
*without* needing a Ctrl-modifier key..


Regards
Thomas
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 22

[Thomas W]

Hi Jehan, Chris, Marc, list members,

Thanks for your feedback. I do feel "autocomplete" is either too intrusive
or feels awkward for a "Save File" dialog, because of the degree to which
it interferes with the UI/ or prompts the user with existing filenames.

> in the cases you do want to overwrite, it is better to have the user
write it down
> or select it by mouse, so that we prevent too fast "enter-enter-damn
> it was the wrong name!" consequences).

I've re-examined the Windows "Save As" file chooser and find it has an
autocomplete -- but I've never noticed it as intrusive. It may be because
the "Filename Input" is below the list pane & thus less visually obtrusive,
and the Windows autocomplete doesn't capture/block any of my key bindings.
(Enter or Alt-S).

> Anyway if possible, I'd say there should be intermediate autocompletion
> types. Like "autocomplete folders, but not file names" (so we still help
users
> to choose a folder,

I examined the GIMP "Save As" chooser more closely.

I found that Autocomplete blocks Alt-S always, and captures/blocks 'Enter'
if your mouse pointer is over/ has entered the autocomplete field. The net
effect of these is very disruptive to my normal expectation of how a UI
should work (press Alt-S once).

It is occasionally possible for Alt-S to actually *work* to save the file
from the dialog, but only in the occasional case where autocomplete hasn't
popped up or has been dismissed already. Most of the time, you press it
once, again, it still doesn't work & then have to mentally context-switch
for a different key. Not good for work rhythm.

By comparison, the Windows autocomplete is down the bottom of the dialog --
below the filename input & away from the file list/ navigation pane -- and
captures/blocks neither Alt-S nor Enter, even if you have moused over it.
Several autocompletions are offered in an unobtrusive way & don't seem to
be a problem.

So perhaps it is not the logical concept of "autocompletion on Save" which
is invalid, perhaps it is rather the UI design & visual layout, and
especially the blocking of keybindings which cause it to be a problem.

> Here's how to reproduce it on Linux:
> Note a mysterious box in the lower right collecting your keystrokes
>
> Version: GIMP 2.8.4 as shipped by Ubuntu.

Thanks for your report, Chris.


Regards
Tom
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Jehan Pagès]

Hi,

On Mon, Sep 16, 2013 at 3:53 PM, Christopher Curtis  wrote:
> On Sun, Sep 15, 2013 at 11:21 PM, Jehan Pagès 
> wrote:
>>
>> well I have the "mysterious box collecting [my] keystroke" (also using
>> GIMP 2.8.4 as shipped by Mint, hence Ubuntu). It just looks to me like
>> a feature for being able to select a file without having the text
>> field active. And it does not block Enter for saving (which was the
>> original bug reported in the email as I understand it).
>> So I don't see any bug there.
>
>
> Well, I haven't been following the thread closely but I don't know what you
> expect it to mean that something would "block Enter".
>

Well... that's part of the message I am answering to, and
consequently, the one you answer to as well.
It says it blocks enter, and I say it does not at least on my machine.

> When in this mode, if you type and hit enter, the box goes away and nothing
> appears to happen. It isn't clear that the box is even there because it's
> not in the visual field. It appears that nothing happens, including enter.
> After hitting enter and trying to type again, the box reappears. Unless you
> pay close attention what is happening this is both very non-obvious and
> frustrating.
>
> I don't understand the bug's comment because I've never tried to use Alt-S
> or Alt-E in that dialog. I suspect the bug report is simply poorly phrased
> out of frustration, which I can completely relate to.

Yes for these other shortcuts, I am not even sure that these are
supposed to work from the start. Maybe these are common shortcut in
save dialogs in Windows program? I can't say.

> How is this popup search even useful when there's already search built in to
> the file name input? I would agree the popup should be removed/disabled.
> Arrow up/down work in it but Page up/down doesn't. Arrow up/down,
> left/right, and Page up/down all work (mostly) reasonably when used from the
> file name input. Worst of all, if you select a file from the multiple choice
> file name input and then arrow up/down, you're in the file chooser portion
> and typing uses the popup search instead of the file name search you just
> came from.
>
> Personally, I hit this frequently and think this behavior is an
> extraordinarily frustrating usability disaster.

Yes probably the file selection dialog can be improved. Do you know if
this also happens in GTK+3 programs? If so, a feature request with
relevant counter propositions of how to improve this for GTK+3 may be
worth it (if not already existing, that's possible and should be
searched first).

Because this is not a GIMP thing and there is not so much we can do
about it (of course we could make a custom widget, but well, the whole
point of separating GTK+ from GIMP was to share common widgets).

Jehan

> Chris
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Christopher Curtis]

On Sun, Sep 15, 2013 at 11:21 PM, Jehan Pagès wrote:

> well I have the "mysterious box collecting [my] keystroke" (also using
> GIMP 2.8.4 as shipped by Mint, hence Ubuntu). It just looks to me like
> a feature for being able to select a file without having the text
> field active. And it does not block Enter for saving (which was the
> original bug reported in the email as I understand it).
> So I don't see any bug there.
>

Well, I haven't been following the thread closely but I don't know what you
expect it to mean that something would "block Enter".

When in this mode, if you type and hit enter, the box goes away and nothing
appears to happen. It isn't clear that the box is even there because it's
not in the visual field. It appears that nothing happens, including enter.
After hitting enter and trying to type again, the box reappears. Unless you
pay close attention what is happening this is both very non-obvious and
frustrating.

I don't understand the bug's comment because I've never tried to use Alt-S
or Alt-E in that dialog. I suspect the bug report is simply poorly phrased
out of frustration, which I can completely relate to.

How is this popup search even useful when there's already search built in
to the file name input? I would agree the popup should be removed/disabled.
Arrow up/down work in it but Page up/down doesn't. Arrow up/down,
left/right, and Page up/down all work (mostly) reasonably when used from
the file name input. Worst of all, if you select a file from the multiple
choice file name input and then arrow up/down, you're in the file chooser
portion and typing uses the popup search instead of the file name search
you just came from.

Personally, I hit this frequently and think this behavior is an
extraordinarily frustrating usability disaster.

Chris
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Jehan Pagès]

Hi,

On Mon, Sep 16, 2013 at 2:57 PM, Christopher Curtis  wrote:
> On Sun, Sep 15, 2013 at 10:38 PM, Jehan Pagès 
> wrote:
>>
>> > I don't appear to have the problem on linux.  Perhaps it is a problem
>> > related to windows.
>>
>> I don't think I have this problem either on Linux. I may test on my
>> Windows VM some day later.
>
>
> Here's how to reproduce it on Linux:
>
> Go to File->Open (or File->Export, etc.)
> Navigate to any directory using the folders on the left.
> Double click to select any folder that looks like a good place to open/save.
> Type something.
> Note the filename, while highlighted, never changes
> Note a mysterious box in the lower right collecting your keystrokes
>
> Version: GIMP 2.8.4 as shipped by Ubuntu.


well I have the "mysterious box collecting [my] keystroke" (also using
GIMP 2.8.4 as shipped by Mint, hence Ubuntu). It just looks to me like
a feature for being able to select a file without having the text
field active. And it does not block Enter for saving (which was the
original bug reported in the email as I understand it).
So I don't see any bug there.

But I still agree that this is probably not the best behavior for the
"save" dialog, and maybe even the "export" one. But for "open", it
looks acceptable (though certainly there is a better way, of course.
Just saying I see no obvious usability problem or bug here, as
reported in the email).

Jehan


> Regards,
> Chris
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Christopher Curtis]

On Sun, Sep 15, 2013 at 10:38 PM, Jehan Pagès wrote:

> > I don't appear to have the problem on linux.  Perhaps it is a problem
> > related to windows.
>
> I don't think I have this problem either on Linux. I may test on my
> Windows VM some day later.


Here's how to reproduce it on Linux:

Go to File->Open (or File->Export, etc.)
Navigate to any directory using the folders on the left.
Double click to select any folder that looks like a good place to open/save.
Type something.
Note the filename, while highlighted, never changes
Note a mysterious box in the lower right collecting your keystrokes

Version: GIMP 2.8.4 as shipped by Ubuntu.

Regards,
Chris
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Jehan Pagès]

Hi,

On Mon, Sep 16, 2013 at 11:07 AM, Paka  wrote:
> * Thomas W  [09-15-13 18:51]:
>> Hi Marc, list members,
>>
>> Yes, I encounter awkwardness with the Save dialog & autocomplete
>> triggering. You will also note that 'autocomplete' triggering blocks Enter
>> from actually saving..  it also blocks Alt-S (or whatever Windows shortcut)
>> from working.
>>
>> I'm not a big fan of autocomplete for "Save" -- if I wanted a similar name
>> to an existing file, I'd expect to select the existing file in the list &
>> change the name in the edit field. Since "autocomplete" here interferes
>> strongly with the expected/standard UI, I'd consider the best usability to
>> remove it entirely.

For the usability problem about "should we autocomplete the save
dialog?", I find your saying interesting. Indeed in a
"non-destructive" point of view, I don't think autocomplete is such a
great idea for the save dialog, because in most cases, you don't want
to overwrite an existing file, but create a new name (and in the cases
you do want to overwrite, it is better to have the user write it down
or select it by mouse, so that we prevent too fast "enter-enter-damn
it was the wrong name!" consequences).
Does it make sense to others?

Unfortunately I think we may not have a say in it. I had a fast look
at GTK file chooser dialog API and did not see a function to disable
autocompletion. I may have to check further in GTK code. I don't think
we can add new features in gtk2, but maybe this can be added to gtk3
(then use when we get out GIMP 3, but it means it won't be available
for a bit of course). Anyway if possible, I'd say there should be
intermediate autocompletion types. Like "autocomplete folders, but not
file names" (so we still help users to choose a folder, but don't
direct them to existing file name for saving).
I'd say this is an interesting feature request. Does anyone agree?

>> https://bugzilla.gnome.org/show_bug.cgi?id=698481
>>
>> Failing that, "autocomplete" should be reworked so as not to block the
>> dialog's main keybindings. (Perhaps this would be useful for the 'Open'
>> dialog.)
>>
>> Marc, you'd be welcome to add you comment in Bugzilla & hopefully "vote"
>> usability issues a little higher priority. Other people notice this issue?
>>
>
> I don't appear to have the problem on linux.  Perhaps it is a problem
> related to windows.

I don't think I have this problem either on Linux. I may test on my
Windows VM some day later.

Jehan
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Paka]

* Thomas W  [09-15-13 18:51]:
> Hi Marc, list members,
> 
> Yes, I encounter awkwardness with the Save dialog & autocomplete
> triggering. You will also note that 'autocomplete' triggering blocks Enter
> from actually saving..  it also blocks Alt-S (or whatever Windows shortcut)
> from working.
> 
> I'm not a big fan of autocomplete for "Save" -- if I wanted a similar name
> to an existing file, I'd expect to select the existing file in the list &
> change the name in the edit field. Since "autocomplete" here interferes
> strongly with the expected/standard UI, I'd consider the best usability to
> remove it entirely.
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=698481
> 
> Failing that, "autocomplete" should be reworked so as not to block the
> dialog's main keybindings. (Perhaps this would be useful for the 'Open'
> dialog.)
> 
> Marc, you'd be welcome to add you comment in Bugzilla & hopefully "vote"
> usability issues a little higher priority. Other people notice this issue?
> 
> Thanks,
> Tom
> 
> 
> > once in a while, when I want to save a file, and get into the safe
> dialog, when I start typing, the text appears
> > right below in a search box instead of in the filename box. I do not know
> how to reproduce this yet, but it
> > happens ever so often and it is a bit annoying.
> 
> 
> 
> 
> 
> 
> On Mon, Sep 16, 2013 at 12:00 AM, 
> wrote:
> 
> > Send gimp-developer-list mailing list submissions to
> > gimp-developer-list@gnome.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > or, via email, send a message with subject or body 'help' to
> > gimp-developer-list-requ...@gnome.org
> >
> > You can reach the person managing the list at
> > gimp-developer-list-ow...@gnome.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of gimp-developer-list digest..."
> >
> >
> > Today's Topics:
> >
> >1. Re:  refactor palette loading code (Warren Turkal)
> >2. Re:  refactor palette loading code (Warren Turkal)
> >3.  Dialog Safe text entered appears in searchboxinstead
> >   filenamebox annoying (Marc Kroeks (zonnet.nl))
> >4. Re:  refactor palette loading code (Jehan Pag?s)
> >
> >
> > --
> >
> > Message: 1
> > Date: Sun, 15 Sep 2013 01:17:46 -0700
> > From: Warren Turkal 
> > To: Michael Henning 
> > Cc: Graphical Geniuses 
> > Subject: Re: [Gimp-developer] refactor palette loading code
> > Message-ID:
> >  > h_rgfeq0gyxq8tbeyq2ilefztd...@mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Sorry for taking so long to respond. I don't have a lot of time during
> > normal work days to work on this. :)
> >
> > On Tue, Sep 10, 2013 at 6:10 PM, Michael Henning
> > wrote:
> >
> > > I made a few minor nitpicks on your commit on github. If you would fix
> > > those points, I'll commit your code to master.
> > >
> >
> > Thanks. I think I addressed all your comments. However, I just added a
> > rewind at the end of gimp_palette_load_detect format instead of doing what
> > your comment suggested. PTAL and see if you approve. Here's the
> > link.
> > I have also attached a patch to this mail.
> >
> > As a side note for the future, the fastest way to get a patch reviewed
> > > is normally if you post it to a pastebin and bother people on irc.
> > >
> >
> > I am not in a huge hurry, and I haven't had much luck catching folks on IRC
> > when I am on. Is there really any benefit of using pastebin over pushing my
> > branch out so that it can be looked at and fetched? The pastebin method
> > seems like it'd be pretty inconvenient for bigger patches, and it doesn't
> > have any kind of commenting on the patch. Also, which pastebin do you
> > prefer?
> >
> > I will say that I was surprised there wasn't more interest in using git to
> > pass around these patches. I would have expected you folks to acquire the
> > patch from my repository (e.g. fetch my branch from my repo and look at the
> > branch directly). I was somewhat surprised by the request for a patch file.
> >
> > With regard to git, I don't see any merges in the history for the project.
> > Does this project not do git merges?
> >
> >   -- drawoc
> > >
> > > P.S. I don't see the patch on that last email. Are you sure you attached
> > > it?
> > >
> >
> > It appears to be attached on my end. Does the ML block attachments?
> >
> > FWIW, I also attached the new diff to this email. It indeed does appear to
> > be attached at this point.
> >
> > wt
> >
> >
> > --
> >
> > Message: 2
> > Date: Sun, 15 Sep 2013 01:32:27 -0700
> > From: Warren Turkal 
> > To: Jehan Pag?s 
> > Cc: Graphical Geniuses 
> > Subject: Re: [Gimp-developer] refactor palette loading code
> > Message-ID:
> > <
> > cab_jbhhsx4

Re: [Gimp-developer] gimp-developer-list Digest, Vol 24, Issue 20

[Thomas W]

Hi Marc, list members,

Yes, I encounter awkwardness with the Save dialog & autocomplete
triggering. You will also note that 'autocomplete' triggering blocks Enter
from actually saving..  it also blocks Alt-S (or whatever Windows shortcut)
from working.

I'm not a big fan of autocomplete for "Save" -- if I wanted a similar name
to an existing file, I'd expect to select the existing file in the list &
change the name in the edit field. Since "autocomplete" here interferes
strongly with the expected/standard UI, I'd consider the best usability to
remove it entirely.

https://bugzilla.gnome.org/show_bug.cgi?id=698481

Failing that, "autocomplete" should be reworked so as not to block the
dialog's main keybindings. (Perhaps this would be useful for the 'Open'
dialog.)

Marc, you'd be welcome to add you comment in Bugzilla & hopefully "vote"
usability issues a little higher priority. Other people notice this issue?

Thanks,
Tom


> once in a while, when I want to save a file, and get into the safe
dialog, when I start typing, the text appears
> right below in a search box instead of in the filename box. I do not know
how to reproduce this yet, but it
> happens ever so often and it is a bit annoying.






On Mon, Sep 16, 2013 at 12:00 AM, wrote:

> Send gimp-developer-list mailing list submissions to
> gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
> gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
> gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>1. Re:  refactor palette loading code (Warren Turkal)
>2. Re:  refactor palette loading code (Warren Turkal)
>3.  Dialog Safe text entered appears in searchboxinstead
>   filenamebox annoying (Marc Kroeks (zonnet.nl))
>4. Re:  refactor palette loading code (Jehan Pag?s)
>
>
> --
>
> Message: 1
> Date: Sun, 15 Sep 2013 01:17:46 -0700
> From: Warren Turkal 
> To: Michael Henning 
> Cc: Graphical Geniuses 
> Subject: Re: [Gimp-developer] refactor palette loading code
> Message-ID:
>  h_rgfeq0gyxq8tbeyq2ilefztd...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Sorry for taking so long to respond. I don't have a lot of time during
> normal work days to work on this. :)
>
> On Tue, Sep 10, 2013 at 6:10 PM, Michael Henning
> wrote:
>
> > I made a few minor nitpicks on your commit on github. If you would fix
> > those points, I'll commit your code to master.
> >
>
> Thanks. I think I addressed all your comments. However, I just added a
> rewind at the end of gimp_palette_load_detect format instead of doing what
> your comment suggested. PTAL and see if you approve. Here's the
> link.
> I have also attached a patch to this mail.
>
> As a side note for the future, the fastest way to get a patch reviewed
> > is normally if you post it to a pastebin and bother people on irc.
> >
>
> I am not in a huge hurry, and I haven't had much luck catching folks on IRC
> when I am on. Is there really any benefit of using pastebin over pushing my
> branch out so that it can be looked at and fetched? The pastebin method
> seems like it'd be pretty inconvenient for bigger patches, and it doesn't
> have any kind of commenting on the patch. Also, which pastebin do you
> prefer?
>
> I will say that I was surprised there wasn't more interest in using git to
> pass around these patches. I would have expected you folks to acquire the
> patch from my repository (e.g. fetch my branch from my repo and look at the
> branch directly). I was somewhat surprised by the request for a patch file.
>
> With regard to git, I don't see any merges in the history for the project.
> Does this project not do git merges?
>
>   -- drawoc
> >
> > P.S. I don't see the patch on that last email. Are you sure you attached
> > it?
> >
>
> It appears to be attached on my end. Does the ML block attachments?
>
> FWIW, I also attached the new diff to this email. It indeed does appear to
> be attached at this point.
>
> wt
>
>
> --
>
> Message: 2
> Date: Sun, 15 Sep 2013 01:32:27 -0700
> From: Warren Turkal 
> To: Jehan Pag?s 
> Cc: Graphical Geniuses 
> Subject: Re: [Gimp-developer] refactor palette loading code
> Message-ID:
> <
> cab_jbhhsx4bfw4k-8u8prp4-s7xcn4xjsqbhy80yfs8uvuh...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Sep 10, 2013 at 6:54 PM, Jehan Pag?s  >wrote:
>
> > On Wed, Sep 11, 2013 at 1:10 PM, Michael Henning
> >  wrote:
> >  > As a side note for the future, the fastest way to get a patch reviewe

Re: [Gimp-developer] gimp-developer-list Digest, Vol 22, Issue 5

[Maggio Mago]

Hey! Thank you Sven,

Effectively i forgot the parameter --enable-gtk-doc-app (I now have the
documentation of the app API)

Unfortunately I still meet concerns. I do not have the images shown. for
example in :
http://developer.gimp.org/api/2.0/libgimpwidgets/libgimpwidgets-GimpStock.html#GIMP-STOCK-LAYERS:CAPSmy
stocks icon are not shown. I
made a copy and paste of the images to fix the problem but if you know a
better solution I'm interested because I did not see any option abouts.

Thank you again for your kindness,



2013/7/7 

> Send gimp-developer-list mailing list submissions to
> gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
> gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
> gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>1.  Generate the API documentation (Maggio Mago)
>2. Re:  Generate the API documentation (scl)
>
>
> --
>
> Message: 1
> Date: Sun, 7 Jul 2013 10:44:39 +0200
> From: Maggio Mago 
> To: gimp-developer-list@gnome.org
> Subject: [Gimp-developer] Generate the API documentation
> Message-ID:
>  268...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello,
>
> I have cloned Gimp-2.8.7 from git then ./configure
> --prefix=/home/user/local --enable-gtk-doc and make install
>
> I can find my documentation in /home/user/local/share/gtk-doc/html/
> For example, I successful generated
> http://developer.gimp.org/api/2.0/libgimpbase/index.html and more :
> $]ls /home/user/local/share/gtk-doc/html
> libgimp  libgimpbase  libgimpcolor  libgimpconfig  libgimpmath
> libgimpmodule  libgimpthumb  libgimpwidgets
>
> However, i do not found the API documentation like this page :
> http://developer.gimp.org/api/2.0/app/app-hierarchy-part.html
>
> Someone could help me ?
>
> PS: I use gtkdoc 1.18
>
>
> --
>
> Message: 2
> Date: Sun, 07 Jul 2013 13:05:48 +0200
> From: scl 
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Generate the API documentation
> Message-ID: <51d94b8c.1050...@gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> it seems, you forgot the parameter  --enable-gtk-doc-app.
>
> You find a detailed description in our developer wiki*.
> Note: the API documentation on developer.gimp.org is
> for GIMP 2.6 and thus outdated. Currently the best way to get
> an up-to-date API docu is to create it yourself.
> I have already considered autogenerating and publishing
> the API docu automatically from the continuous builds,
> but yet haven't found a hoster.
>
> Kind regards,
>
> Sven
>
>
> *developer wiki: http://wiki.gimp.org/index.php/Hacking:API_documentation
>
>
> --
>
> Subject: Digest Footer
>
> ___
> gimp-developer-list mailing list
> gimp-developer-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
>
>
> --
>
> End of gimp-developer-list Digest, Vol 22, Issue 5
> **
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 18, Issue 7

[Kim Malar]

what are legacy plugins???

On Thu, Mar 7, 2013 at 5:30 PM, wrote:

> Send gimp-developer-list mailing list submissions to
> gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
> gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
> gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>1. Re:  Improving pygimp documentation (Sean Munkel)
>2. Re:  GIMP - flesh out a way of allowing lazy  rendering?
>   (Jon Nordby)
>3. Re:  Improving pygimp documentation (Joao S. O. Bueno)
>4.   Improving pygimp documentation (Sean Munkel)
>
>
> --
>
> Message: 1
> Date: Wed, 6 Mar 2013 17:19:33 -0500
> From: Sean Munkel 
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Improving pygimp documentation
> Message-ID:
> <
> cakyagk3gjcdmfmhe++vy81+nx1e83r_nmkp38e7gmnatv86...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> The problem with that is that help() would not display the__doc__ for
> the instance of PDBFunction, but will instead generate a generic
> overview of the class itself. As far as I can tell this is because
> help() doesn't recognize PDBFunction instances as functions (or
> routines as they're called in inspect). I had actually tried your
> approach initially and it did not work coming from the C side or from
> the Python side. This is why I created a custom help(). To get help()
> to display the __doc__ of an object it has to be a C builtin or a
> python function.
>
> This brings me to a messier idea that I had to get around this. One
> way to get around this issue of __doc__ not being display is to
> actually create a regular python function for each procedure. Instead
> of using gimp.PDB you would have to wrap it in a class that will use
> its methods but hook into __getattr__. Inside of __getattr__ it would
> create a function that would then be able to have a __doc__ that would
> be displayed by help.
>
> https://gist.github.com/smunkel/5103533
>
>
> On Mon, Mar 4, 2013 at 6:46 AM, Joao S. O. Bueno 
> wrote:
> > Your approach could lead to a a patch to dynamically provide the __doc__
> > attributes of PDB items - taht would be ok. For the builtin items,
> > such as Layer, Image and such, as the code is today,
> > the documentation would have to be hard-coded in the C files, however.
> >
> >   js
> >  -><-
>
>
> --
>
> Message: 2
> Date: Thu, 7 Mar 2013 00:41:17 +0100
> From: Jon Nordby 
> To: "Joao S. O. Bueno" 
> Cc: gimp-developer 
> Subject: Re: [Gimp-developer] GIMP - flesh out a way of allowing lazy
> rendering?
> Message-ID:
>  z...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 4 March 2013 15:24, Joao S. O. Bueno  wrote:
> > Hi all --
> >
> > While GIMP 2.9 is thriving with lots of possibilities, one thing remain
> as fact:
> > it is dead slow.
> >
> > I most likely missed some of the efforts being done to try to
> > compensate for that -
> > like avoiding unnecessary pixel format conversions in some operations -
> and
> > the possibility of having GEGL to run with open-CL acceleration.
> >
> > I think it is not an exaggeration to add that even with this, the
> > current rendering model
> > is dead slow.
> >
> > To the point of being unfeasible to work on a 1024x768 image in modern
> > hardware -
> > one simply can't paint.
> Other raster application, including GIMP 2.8, are doing OK performance
> wise with a rendering mode that is very similar to GIMP uses now, so I
> don?t we necessarily need to do drastic changes there in order to fix
> the performance.
>
> I think a useful GSoC project would be to define and implement some
> meaningful benchmarks for GIMP. If successful, that would give
> insights into what the causes of the current performance problems are.
> I believe that is needed for coming up with a good solution for
> current, and future performance issues.
>
> --
> Jon Nordby - www.jonnor.com
>
>
> --
>
> Message: 3
> Date: Thu, 7 Mar 2013 00:13:40 -0300
> From: "Joao S. O. Bueno" 
> To: Sean Munkel 
> Cc: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Improving pygimp documentation
> Message-ID:
> <
> cah0mxtq55qhtr4jewuafbewap50uxcvwujxssbta5rlqn+4...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 6 March 2013 19:19, Sean Munkel  wrote:
> > The problem with that is that help() would not display the__doc__ for
> > the instance of PDBFunction, but will instead generate a generic
> > overview of the class itself. As far as I can tell this is because
> > help() doe

Re: [Gimp-developer] gimp-developer-list Digest, Vol 12, Issue 31

[Gino D]

>
> That is the new (GIMP 2.8) default behaviour that irritates Gino. IMHO
> would be great to let the user choose its preference, use one general
> size default for all the tools or default to the tool default size. An
> option in the preference or in the tool options should be created on
> purpouse.
>
> bye
>
> --
> Marco Ciampa
>

I did not mean to give the impression of being irritated about this
new feature, although I have to admit it leaves me a bit puzzled. More
than anything, I was interested in being informed whether it was a bug
or not, before going and submitting in vain that issue at the Bugzila
GNOME site. However, through your clarification, now I know for sure
that it is not a matter of a bug. For the rest, I agree with you about
the convenience obtained by equipping the GIMP with that option you
perfectly described. Unfortunately, I myself am not yet so skilled to
operate on the source code, but maybe some developer (who thinks it is
worth it) might.

Thanks and regards.

-- 
Gino D
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 9, Issue 25

[Mathew Oakes]

I'd like to just chime in with support for the new save export setup. 

It is a lot clearer than how photoshop morphs the save and save as dialogues 
with 'as a copy' as well as arbitarily hiding other options.

I'm astonished at the ire many are expressing over modifying their behaviour 
slightly. Perhaps they should just stick with 2.6

If there is a break with convention in the interface, it might be 'save as' may 
have been a less radical choice.

When there are adjustment layers and higher bit depth editing. This arrangement 
will be even more valuable
-- 
Sent from my phone, excuse my brevity.

gimp-developer-list-requ...@gnome.org wrote:

Send gimp-developer-list mailing list submissions to
gimp-developer-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
or, via email, send a message with subject or body 'help' to
gimp-developer-list-requ...@gnome.org

You can reach the person managing the list at
gimp-developer-list-ow...@gnome.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gimp-developer-list digest..."


Today's Topics:

1. Re: present xcf as what it is, a gimp project file format (Paka)
2. Re: present xcf as what it is,   a gimp project file format
(Jon Nordby)
3. Re: present xcf as what it is, a gimp project file format (gg)
4. Re: present xcf as what it is, a gimp project file format (gg)
5. Re: present xcf as what it is, a gimp project file format
(Marco Ciampa)
6. Re: present xcf as what it is, a gimp project file format
(Marco Ciampa)
7. Re: present xcf as what it is,   a gimp project file format
(Christopher Curtis)


_


Message: 1
Date: Sat, 16 Jun 2012 13:46:12 -0400
From: Paka 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <20120616174612.gb30...@wahoo.no-ip.org>
Content-Type: text/plain; charset=us-ascii

* Nicolas Robidoux  [06-16-12 12:55]:
> > - to really Save the contents of the file has to match what is
> > on the screen (save, quit, restart, open file: no change--undo
> > history excepted). this is not just a good idea, this is the law.
> > breaking the law: usability blooper.
> 
> Indeed, if "Save is lossless" is a law, "Save" has to be to XCF, and
> something else has to be used to "save" to any other format.

Maybe "export to"

> Nonetheless, I can't help but think that few people would buy a gun
> that makes it hard to shoot yourself in the foot.
> 
> No matter how sensical the feature.
> 
> Because most of us like to shoot first and ask questions later.

Perhaps YOU are not the "target audience".

-- 
(paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
http://en.opensuse.org openSUSE Community Member
Registered Linux User #207535 @ http://linuxcounter.net


_


Message: 2
Date: Sat, 16 Jun 2012 19:58:02 +0200
From: Jon Nordby 
To: Nicolas Robidoux 
Cc: gimp-developer mailing list 
Subject: Re: [Gimp-developer] present xcf as what it is,a gimp
project file format
Message-ID:

Content-Type: text/plain; charset=UTF-8

On 16 June 2012 18:54, Nicolas Robidoux  wrote:
>> - to really Save the contents of the file has to match what is
>> on the screen (save, quit, restart, open file: no change--undo
>> history excepted). this is not just a good idea, this is the law.
>> breaking the law: usability blooper.
>
> Indeed, if "Save is lossless" is a law, "Save" has to be to XCF, and
> something else has to be used to "save" to any other format.
>
> Nonetheless, I can't help but think that few people would buy a gun
> that makes it hard to shoot yourself in the foot.
>
> No matter how sensical the feature.
Most guns I know have the very sensible feature of a safety switch. It
does make it harder to accidentally shoot oneself in the foot, but I
have not heard very many people complain about it.

Most guns also have a shield in front of the trigger, and require a
substantial force to actually trigger. The ease of shooting oneself in
the foot is severely hampered by this, but again I do not see many
complain about it.

> Because most of us like to shoot first and ask questions later.
I think that "better safe than sorry" is a more sensible approach. One
can in general not revive dead peop^Wdocuments.


-- 
Jon Nordby - www.jonnor.com


_


Message: 3
Date: Sat, 16 Jun 2012 20:16:40 +0200
From: gg 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <4fdccd88.4070...@catking.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 06/16/12 19:58, Jon Nordby wrote:
> One
> can in general not revive dead pe

Re: [Gimp-developer] gimp-developer-list Digest, Vol 8, Issue 12

[legion1978]

  
  
Ok guys. I figured if i just posted "gimp" and "rename" in the same
sentence, you would've just disregard it. So, as gg wisely put it, I
made the message look "spammy". It occurred to me it would be more
likely clicked. :) Not so far fetched.

Heres the thing: I believe its not just a matter of *name change*,
but an image revamp. 
I read some old threads from 2007 and 2009 and a guy said at the end
of one something like "if you can either point out other reasons
than the one has been already discused (and ruled on) and make a
solid arguement about this particular topic, *maybe* it can raise
some interest". This regarding same ol' bitchin 'bout the negative
context the gimp word has in some scenarios, which is besides my
point (in my post).
So, without any pretensions,  I refer u all to the post i made
http://tinyurl.com/8857jxn
For those of u who had read it, thank you for your time. It means a
lot.  And for all the others "thanx, but no thanx" type of guys, i
can only say "never close a door to a future, without fully knowing
what it can offer".

Thank you.



gimp-developer-list-requ...@gnome.org escribió:

  Send gimp-developer-list mailing list submissions to
	gimp-developer-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.gnome.org/mailman/listinfo/gimp-developer-list
or, via email, send a message with subject or body 'help' to
	gimp-developer-list-requ...@gnome.org

You can reach the person managing the list at
	gimp-developer-list-ow...@gnome.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gimp-developer-list digest..."


Today's Topics:

   1. Re:  yes, its that time of the year.. (Eric Grivel)
   2. Re:  [Gimp-user] Translation updates for GIMP 2.8 (?yvind Kol?s)
   3. Re:  XP SP3 requirement? (Jernej Simon?i?)
   4.  Differences between Gimp Windows and Gimp Linux (Anke Lange)
   5. Re:  Differences between Gimp Windows and Gimp Linux
  (mikehenn...@eclipse.net)
   6. Re:  yes, its that time of the year.. (Michael Grosberg)
   7. Re:  Official 2.8 Windows installer? (michael grosberg)
   8. Re:  yes, its that time of the year.. (Michael Schumacher)
   9. Re:  [Gimp-user] Translation updates for GIMP 2.8
  (Cristian Secar?)


--

Message: 1
Date: Sun, 06 May 2012 11:48:51 -0400
From: Eric Grivel 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] yes, its that time of the year..
Message-ID: <4fa69d63.10...@lumenssolutions.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Well, I deleted the message without reading, and I'm not planning to 
click the link until it is accompanied with some relevant information on 
why it would be relevant for me. Because unlike gg I'm not quite that 
bored...

Eric

On 05/06/2012 10:14 AM, gg wrote:

  
On 06/05/12 15:15, legion1978 wrote:


  Please read it before you ditch it.
http://tinyurl.com/8857jxn


Thank you.


-- 
*Roony Alvarez*
/Director Creativo/
The Shibumi Group




As a publicist, you sure know how to make your emails look like SPAM.

I clicked on the tinyURL link FULLY expecting it to be spam ( because 
I'm bored and was curious a to what browser trick it might be using. )

I was rather phased when it turned out to be something to do with GIMP.

I suppose if you're trying to trick people into reading something you 
imagine they don't want to read, you have to be a bit devious.

/gg



___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list


  
  

--

Message: 2
Date: Sun, 6 May 2012 18:19:23 +0200
From: ?yvind Kol?s 
To: Cristian Secar? 
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] [Gimp-user] Translation updates for GIMP
	2.8
Message-ID:
	
Content-Type: text/plain; charset=UTF-8

On Sun, May 6, 2012 at 3:45 PM, Cristian Secar?  wrote:

  
I checked with the official source code release for 2.8 and it seems
that things have been screwed up somewhere. The script-fu .po files for
languages ar, el, eo, ko, ro and te reports 61 total strings, the same
as the current online version which now has been truncated down to 61
strings for *all* languages.

  
  
It sounds like translators are pushing translations based on master into 2.8.
The reduction in translatable string count is probably related to a
local trimming/cleaning commit that I have locally that has not been
pushed yet - but the removal of string has been prematurely pushed.

/?




-- 
  Roony Alvarez
  Director Creativo
  The Shibumi Group
  3126793266
  


___
gimp-developer-list mail

Re: [Gimp-developer] gimp-developer-list Digest, Vol 7, Issue 6

[un.autrerevenu]

BONJOUR , et MERCI le problème pour moi est L'ANGLAIS .Gerard
leseniorprovencal .



2012/4/4 

> Send gimp-developer-list mailing list submissions to
>gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
>gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
>gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>   1. Re:  Get currently active image in python (Jon Decker)
>   2.  Plugin registration question (Jon Decker)
>   3.  Python plugin debugging and workflow (Jon Decker)
>   4. Re:  bug with Overlay (Paul Geraskin)
>   5. Re:  Python plugin debugging and workflow (Joao S. O. Bueno)
>   6. Re:  Python plugin debugging and workflow (Ragnar Brynj?lfsson)
>
>
> --
>
> Message: 1
> Date: Tue, 3 Apr 2012 05:50:23 -0400
> From: Jon Decker 
> To: "Joao S. O. Bueno" 
> Cc: gimp-developer 
> Subject: Re: [Gimp-developer] Get currently active image in python
> Message-ID:
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Ok thanks for the information.  I think I'll file a feature request as well
> - I think this would be a great addition to the API
>
> On Mon, Apr 2, 2012 at 10:06 AM, Joao S. O. Bueno  >wrote:
>
> > On 23 March 2012 15:06, Chris Mohler  wrote:
> > > On Fri, Mar 23, 2012 at 12:51 PM, Jon Decker 
> > wrote:
> > >> Thanks for the reply.  I do realize that the current image and
> drawable
> > is
> > >> passed to the plugin when first opened.  Perhaps I should explain
> > further.
> > >> I'm trying to build more of an extension that is opened just once, and
> > >> updates as you move from image to image. (Its a time tracking window
> > which
> > >> stays open along side gimp).  I wanted to make it so that a new
> > instance of
> > >> the plugin doesn't have to run for each image - just open it once, and
> > it
> > >> "knows" which image is currently active so that it can populate my
> > sqlite
> > >> database.
> > >>
> > >> Is there a way to do this at in in gimp?
> >
> > No, there is not - at least no clean ways that I can think of. There
> > is nothing on the GIMP's API that marks an image as the
> > currently active image.(The "unclean way" I can think of  would mean
> > to use GTK+ instrumentation for GUI debugging to be able to introspect
> > active
> > windows, and infere the active image from its title)
> >
> > Another "unclean", but tidier, way would be to create a very simple
> > script, with no parameters but "image and drawable" that would just
> > signal your main plug-in when called - and you could bind it to a
> > shortcut key and press it everytime you switch the active image.
> >
> > To notify your mainplug-in you could use some file-system signaling
> > mechanism, xmlrpc, or some gtk+ mechanism..
> >
> > I'd use this second approach.
> >
> > >
> > > I'm not sure (reposting to list - be sure to 'reply-all' vs just
> > 'reply').
> > >
> > > Chris
> > > ___
> > > gimp-developer-list mailing list
> > > gimp-developer-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/gimp-developer-list
> >
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://mail.gnome.org/archives/gimp-developer-list/attachments/20120403/ca5746ec/attachment.html
> >
>
> --
>
> Message: 2
> Date: Tue, 3 Apr 2012 05:54:44 -0400
> From: Jon Decker 
> To: gimp-developer-list@gnome.org
> Subject: [Gimp-developer] Plugin registration question
> Message-ID:
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello
>
> The plugin I have been developing doesn't really relate to individual
> images (its more of an extension).  In my registration call, how do I make
> it so that the listing in the menu is never grayed out?  Currently I just
> open any image to make the entry active, but I'm sure there is a way to
> make certain entries always active.  I'm using the gimpplugin module.
> Thanks
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://mail.gnome.org/archives/gimp-developer-list/attachments/20120403/d1f9c0d1/attachment.html
> >
>
> --
>
> Message: 3
> Date: Tue, 3 Apr 2012 07:01:40 -0400
> From: Jon Decker 
> To: gimp-developer 
> Subject: [Gimp-developer] Python plugin debugging and workflow
> Message-ID:
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello
>
> I have a lot of work into my first large plugin.  One thing that really
> slows my progress is the lack of any kind of debugging or work flow.  For
> example, if I make a syntax error, the plugin wil

Re: [Gimp-developer] gimp-developer-list Digest, Vol 6, Issue 26

[Ricardo Klein]

thanks for all of you for answer me, I sent your replies to the teacher who
will lead the translation project. He will contact some of you (or maybe
enter the list) soon.


--
regards.

Ricardo Felipe Klein
klein@gmail.com


On Wed, Mar 14, 2012 at 6:56 AM, wrote:

> Send gimp-developer-list mailing list submissions to
>gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
>gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
>gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>   1.  Translate to pt_BR (Ricardo Klein)
>   2. Re:  Translate to pt_BR (Michael Schumacher)
>   3. Re:  Translate to pt_BR (Tobias Jakobs)
>   4. Re:  Easy access for contributors (grafxuser)
>   5.  ANNOUNCE: GIMP 2.7.5 released (Michael Natterer)
>   6. Re:  Translate to pt_BR (Joao S. O. Bueno)
>   7. Re:  Easy access for contributors (Alexandre Prokoudine)
>   8. Re:  Translate to pt_BR (Ricardo Klein)
>
>
> --
>
> Message: 1
> Date: Tue, 13 Mar 2012 10:10:37 -0300
> From: Ricardo Klein 
> To: gimp-developer-list@gnome.org
> Subject: [Gimp-developer] Translate to pt_BR
> Message-ID:
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi there,
>
> I work in an University in South of Brazil and we have here one teacher who
> want to make students of Information Systems learn English by
> software/documentation translation, so, I came to as you if you need help
> on pt_BR translation, who I need to talk to know how it will be done and,
> then, I will put the teacher to talk with this responsible for translation.
>
> Thanks and btw, GIMP is a great project... congrats.
>
> --
> Att...
>
> Ricardo Felipe Klein
> klein@gmail.com
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://mail.gnome.org/archives/gimp-developer-list/attachments/20120313/08c2ae88/attachment.html
> >
>
> --
>
> Message: 2
> Date: Tue, 13 Mar 2012 15:52:41 +0100
> From: "Michael Schumacher" 
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Translate to pt_BR
> Message-ID: <20120313145241.285...@gmx.net>
> Content-Type: text/plain; charset="utf-8"
>
> > Von: Ricardo Klein 
>
> > I work in an University in South of Brazil and we have here one teacher
> > who want to make students of Information Systems learn English by
> > software/documentation translation, so, I came to as you if you need help
> > on pt_BR translation, who I need to talk to know how it will be done and,
> > then, I will put the teacher to talk with this responsible for
> > translation.
>
> Hi Ricardo,
>
> the translation progress for Brazilian Portuguese ranges from 50%
> (libgimp) to 100% (tags; with 2 translatable strings), so there is plenty
> of work left. See http://l10n.gnome.org/module/gimp/ for details of the
> progress per translation domain within GIMP.
>
> The coordinator and active members of the Brazilian Portuguese translation
> team are listed at http://l10n.gnome.org/teams/pt_BR/
>
> Thanks in advance for your effort, and please don't hesitate to ask for
> clarification of any unknown or ambiguous English terms you may encounter -
> we'll be happy to explain the concepts if necessary.
>
>
> Regards,
> Michael
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
>
>
> --
>
> Message: 3
> Date: Tue, 13 Mar 2012 16:24:49 +0100
> From: Tobias Jakobs 
> To: Michael Schumacher 
> Cc: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Translate to pt_BR
> Message-ID:
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Mar 13, 2012 at 15:52, Michael Schumacher  wrote:
> >> Von: Ricardo Klein 
> >
> >> I work in an University in South of Brazil and we have here one teacher
> >> who want to make students of Information Systems learn English by
> >> software/documentation translation, so, I came to as you if you need
> help
> >> on pt_BR translation,
>
> Have a look at the documentation, there is only 1% translated:
> http://l10n.gnome.org/languages/pt_BR/gnome-gimp/doc/
>
> Regards,
> Tobias
>
>
> --
>
> Message: 4
> Date: Tue, 13 Mar 2012 17:20:22 +0100
> From: grafxuser 
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Easy access for contributors
> Message-ID: <4f5f73c6.1020...@online.de>
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>
>  > On that my only comment is: I wish you spent as much time contributing
>  > as you spent proposing  But that

Re: [Gimp-developer] gimp-developer-list Digest, Vol 6, Issue 11

[Alexandre Prokoudine]

On Wed, Mar 7, 2012 at 9:02 AM, Alexandre Prokoudine
 wrote:
> On Wed, Mar 7, 2012 at 2:55 AM,   wrote:
>> Thank you Very much Alexandre.
>> It is helpful , but I'm not  sure what mean
>> $ gimptool --install
>
> It means, literally, that you run this command in condole to build and
> install a .c plug-in.
>
> $ gimptool -- install your_plugin.c

--install, of course

Alexandre Prokoudine
http://libregraphicsworld.org
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 6, Issue 11

[Alexandre Prokoudine]

On Wed, Mar 7, 2012 at 2:55 AM,   wrote:
> Thank you Very much Alexandre.
> It is helpful , but I'm not  sure what mean
> $ gimptool --install

It means, literally, that you run this command in condole to build and
install a .c plug-in.

$ gimptool -- install your_plugin.c

Of course, you could be using a plug-in template instead, and in that
case, it would be the usual ./configure && make && sudo make install
routine (on Linux).

Alexandre Prokoudine
http://libregraphicsworld.org
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 6, Issue 11

[HISystem]

Thank you Very much Alexandre.
It is helpful , but I'm not  sure what mean  
$ gimptool --install
 
Best Regards Jacob
 
 
 
 
In a message dated 3/6/2012 7:00:24 A.M. Eastern Standard Time,  
gimp-developer-list-requ...@gnome.org writes:

>  Hello
> I'm trying to write and run plug-ins, but don't know how to  install plug 
in

$ gimptool  --install

http://wiki.gimp.org/index.php/Hacking:Plugins#Installation_of_GIMP_Plug-ins

Alexandre  Prokoudine
http://libregraphicsworld.org
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

Re: [Gimp-developer] gimp-developer-list Digest, Vol 4, Issue 31

[Gerard BRESOLIN]

BONSOIR , et GRAND   MERCI ,mais pour moi l'anglais que j'aime bien est
trop loin pour moi 43 ans  MERCI de me comprendre PS: je ne peux pâs suivre
.Gerard leseniorprovencal .




2012/1/26 

> Send gimp-developer-list mailing list submissions to
>gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
>gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
>gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>   1. Re:  something's starting, it is the text tool (Thorsten Wilms)
>   2.  fonts (Ben Harrington-Ellsmore)
>   3. Re:  something's starting, it is the text tool (peter sikking)
>   4. Re:  something's starting, it is the text tool
>  (gespert...@gmail.com)
>   5. Re:  something's starting, it is the text tool
>  (gespert...@gmail.com)
>   6.  Naming of thumbnails in Gimp on Windows (Ragnar Brynj?lfsson)
>   7. Re:  Naming of thumbnails in Gimp on Windows
>  (Mukund Sivaraman)
>
>
> --
>
> Message: 1
> Date: Thu, 26 Jan 2012 12:49:37 +0100
> From: Thorsten Wilms 
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] something's starting, it is the text
>tool
> Message-ID: <4f213dd1.3000...@freenet.de>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 01/26/2012 12:03 PM, peter sikking wrote:
>
> > ?text never is the main purpose in GIMP work (like it is in scribus
> > or libreOffice writer), it only plays a supporting role within
> > a graphical work?
>
> I could see myself using text in GIMP for
> - text in mockups
> - annotations
> - as integral part of ... poster design
>
> For mockups, I prefer Inkscape, these days. GIMP only wins for some
> modifications of screenshots.
>
> With annotations I mean simple text placed on images. Usually small and
> without any effect or only effects like drop shadow or blurring the
> background for better legibility. This is all about convenience: to not
> have an additional export/import/export with another application involved.
>
> For text as integral part of a poster (or similar setting), it's hard to
> compete with the flexibility and rich functionality of vector graphics
> applications like Inkscape. Reasons to use GIMP could be a need for
> tricky blending and pixel-based effects like grungy edges.
>
> That would be text that is primarily an element of a graphical
> composition, then. In contrast to text where its exact shape and
> placement are secondary. I would not speak of a supporting role, as the
> text might well take center stage and/or be the backbone of the work.
>
> Such text, that is all about explicit shapes and exact/direct placement,
> is the opposite to the result of some raw string of text with a set of
> formatting rules applied to it.
>
>
> --
> Thorsten Wilms
>
> thorwil's design for free software:
> http://thorwil.wordpress.com/
>
>
> --
>
> Message: 2
> Date: Thu, 26 Jan 2012 11:53:19 +
> From: Ben Harrington-Ellsmore 
> To: 
> Subject: [Gimp-developer] fonts
> Message-ID: 
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> been trying to work out for a while how to limit the fonts that load on
> startup
> can anyone tell me where the file I need to edit is to restrict it to only
> loading
> home/.gimp2.6/fonts rather than also loading all the system fonts as well?
>
>
> http://www.freewebs.com/noughtypixy/
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://mail.gnome.org/archives/gimp-developer-list/attachments/20120126/e6aad258/attachment.html
> >
>
> --
>
> Message: 3
> Date: Thu, 26 Jan 2012 15:53:47 +0100
> From: peter sikking 
> To: gimp-developer 
> Subject: Re: [Gimp-developer] something's starting, it is the text
>tool
> Message-ID: 
> Content-Type: text/plain; charset=us-ascii
>
> wow,
>
> Thorsten Wilms' reply is exactly the type of information
> I am looking for.
>
> > I could see myself using text in GIMP for
> > - text in mockups
> > - annotations
> > - as integral part of ... poster design
> >
> > For mockups, I prefer Inkscape, these days. GIMP only wins for some
> modifications of screenshots.
> >
> > With annotations I mean simple text placed on images. Usually small and
> without any effect or only effects like drop shadow or blurring the
> background for better legibility. This is all about convenience: to not
> have an additional export/import/export with another application involved.
> >
> > For text as integral part of a poster (or similar setting), it's hard to
> compete with the flexibility and rich functionality

Re: [Gimp-developer] gimp-developer-list Digest, Vol 4, Issue 18

[Gerard BRESOLIN]

BONJOUR , et MERCI l'anglais est trop loin pour moi c'est 43 ans MERCI de
me comprendre Gerard le seniorprovencal .



2012/1/14 

> Send gimp-developer-list mailing list submissions to
>gimp-developer-list@gnome.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://mail.gnome.org/mailman/listinfo/gimp-developer-list
> or, via email, send a message with subject or body 'help' to
>gimp-developer-list-requ...@gnome.org
>
> You can reach the person managing the list at
>gimp-developer-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gimp-developer-list digest..."
>
>
> Today's Topics:
>
>   1. Re:  something's starting, it is the text tool
>  (Alexandre Prokoudine)
>   2. Re:  something's starting, it is the text tool (Jay Smith)
>   3. Re:  something's starting, it is the text tool (Michael Natterer)
>   4. Re:  something's starting, it is the text tool (Michael Natterer)
>   5.  Request for 2.8 - treat images as items (Saul Goode)
>
>
> --
>
> Message: 1
> Date: Fri, 13 Jan 2012 22:55:25 +0400
> From: Alexandre Prokoudine 
> To: gimp-developer 
> Subject: Re: [Gimp-developer] something's starting, it is the text
>tool
> Message-ID:
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, Jan 13, 2012 at 10:54 PM, Alexandre Prokoudine wrote:
>
> > 1. Really small text frames: with few words in not more than two rows
> > (think logos, captions for screenshots etc.). Adjustments: font, font
> > face, size, letter spacing, baseline offset, color. Missing property:
> > stroke color.
>
> My bad: stroke color _and_ stroke width
>
> Alexandre Prokoudine
> http://libregraphicsworld.org
>
>
> --
>
> Message: 2
> Date: Fri, 13 Jan 2012 14:11:59 -0500
> From: Jay Smith 
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] something's starting, it is the text
>tool
> Message-ID: <4f1081ff.5030...@jaysmith.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 01/13/2012 12:12 PM, peter sikking wrote:
> >
> > so please help us by replying here, with you answer what
> > text means to you when working with GIMP.
>
>
> One of my major uses is composing textual elements of book covers and
> spines.
>
> Another use is minor overlays of bits of text on photographs to point
> out relevant technical features in the photos.
>
>
> What I wish to see in text tools
>
> - Always editable text as long as file in a format that is not flattened.
>
> - Important (to me): Most recently used text settings (i.e. typestyle,
> size, bold/italic, color, etc.) to be saved (including between Gimp
> restarts) for default us in next operation.  (Too many settings in Gimp
> are not saved, even while editing within session of editing a single
> image -- this should be a focus of improvement soon.)
>
> - Per above, save settings as a "set" of settings that can be brought
> back for use (like Curves are saved).  These "sets" of settings should
> be nameable by the user (or if not named by user, then default name of
> date/time).  Naming is very important to be able to quickly find
> settings for various projects.
>
> - Once text is created, always be able to change typestyle, size,
> bold/italic, color, etc., etc.
>
> - In this context, be able to stay in the text dialog and
>   be able to highlight & change differing parts of the text.
>   i.e. Don't have to get out of dialog for each such change.
>   i.e. Changes are _not_ all-or-nothing.
>
> - When editing existing text, if user clicks in the middle to text, then
> further typing of characters uses the attributes in which it is in the
> middle.  Same for either end of string, but I understand that the user
> must be sure to get to the beginning or end of string in a way that
> keeps the user inside the current attributes of the text.
>
> - Text to be rotatable as any other layer without losing quality.
>
> - Multiple text layers that can be edited individually or locked
> together for movement of layers as a group.
>
> - Preview window showing net effect of text on total image.  If the user
> has to edit text and then get out of dialog and render to be able to see
> the net effect, the process can get very time consuming.
>
> ? Maybe have a warning if image resolution is too low to render the text
> without having "jaggies".
>
> Jay
>
>
> --
>
> Message: 3
> Date: Fri, 13 Jan 2012 20:24:02 +0100
> From: Michael Natterer 
> To: Jay Smith 
> Cc: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] something's starting, it is the text
>tool
> Message-ID: <1326482642.29255.0.camel@localhost>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi Jay,
>
> all of that, apart from rotating while staying editable,
> is implemented and will be in gimp 2.8.
>
> --mitch