Re: [Gimp-developer] menu cluttage

[Sven Neumann]

Hi,

On Wed, 2006-07-05 at 21:36 -0300, Joao S. O. Bueno Calligaris wrote:

> It is allright for me if you do not install then- but I had 
> complained. - At least count that.

IIRC, there hasn't been a comment in the respective bug report, but I
might be wrong.

> Actually we could think of then case by case. Almost all of then are 
> just clones of other plugin/scripts, buyt, py-slice, for example, has 
> only an equivalent in gimp-perl, and currently py-slice is far more 
> capable.
> 
> Also, IRCC, some scripts dealing with palettes where implemented in 
> python, using some I had done as basis. These also provide unique 
> features.

Right, but as long as the scripts aren't internationalized and
localized, I am afraid we can't install them by default. So if we really
need them, someone should better look at doing that right now.

It would also be nice to give the pygimp UI an overhaul so that their
dialogs look more like the rest of the GIMP UI.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] menu cluttage

[Akkana Peck]

Sven Neumann writes:
> And so far I don't see anyone complaining about my proposal to not
> install any Python scripts at all with GIMP 2.4.

Not installing scripts that are there strictly as example code
makes sense. Would they stay in CVS head, so it would be easy
for people learning gimp-python to find them?

What about the few python scripts that perform functions that aren't
otherwise available? Even if they're not perfect, some of them
seem useful. For instance, py-slice can be very handy for some
people (if they don't have gimp-perl and perlotine).  Foggify is a
bit different from anything else that's installed by default, isn't
it? And it seems to work okay even if the default color makes me
wonder where the author lives (orange reflections from low-pressure
sodium lighting?)

...Akkana
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] menu cluttage

[Joao S. O. Bueno Calligaris]

On Wednesday 05 July 2006 09:36 pm, Joao S. O. Bueno Calligaris wrote:
> On Wednesday 05 July 2006 04:47 pm, Sven Neumann wrote:
> > Hi,
> >
> > On Tue, 2006-07-04 at 01:11 -0400, Kevin Cozens wrote:
> > > Now that GIMP handles registration of the same menu item from
> > > different plug-ins, I am just waiting for the time a user
> > > reports a bug in Whirl and Pinch (for example) and doesn't
> > > realize which version they were using (as in the Python version
> > > or the C version).
> >
> > The Python version will of course not be in any stable release.
> >
> > And so far I don't see anyone complaining about my proposal to
> > not install any Python scripts at all with GIMP 2.4.
>
> Hey.
> It is allright for me if you do not install then- but I had
> complained. - At least count that.

Forgot to say this: not only had I complained, but I also offered to 
fix the issues with the python scripts  right away, and you just said 
it was too late. 


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] menu cluttage

[Joao S. O. Bueno Calligaris]

On Wednesday 05 July 2006 04:47 pm, Sven Neumann wrote:
> Hi,
>
> On Tue, 2006-07-04 at 01:11 -0400, Kevin Cozens wrote:
> > Now that GIMP handles registration of the same menu item from
> > different plug-ins, I am just waiting for the time a user reports
> > a bug in Whirl and Pinch (for example) and doesn't realize which
> > version they were using (as in the Python version or the C
> > version).
>
> The Python version will of course not be in any stable release.
>
> And so far I don't see anyone complaining about my proposal to not
> install any Python scripts at all with GIMP 2.4.
Hey.
It is allright for me if you do not install then- but I had 
complained. - At least count that.

Actually we could think of then case by case. Almost all of then are 
just clones of other plugin/scripts, buyt, py-slice, for example, has 
only an equivalent in gimp-perl, and currently py-slice is far more 
capable.

Also, IRCC, some scripts dealing with palettes where implemented in 
python, using some I had done as basis. These also provide unique 
features.


JS
-><-

>
> Sven
>
>
> ___
> Gimp-developer mailing list
> Gimp-developer@lists.XCF.Berkeley.EDU
> https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: SoC mentors & students: mid-term evaluations!

[David Neary]

Hi,

Sven Neumann wrote:
> On Mon, 2006-07-03 at 11:03 +0200, Dave Neary wrote:
> 
>> For mentors, it is not just recommended to be subscribed here, it is a
>> requirement - as in this case, important information about the program
>> is sent to this list, and I have been working on the assumption that all
>> GIMP mentors are subscribed there.
> 
> Sorry, but the amount of traffic coming in due to this list is not
> acceptable, especially since it can hardly be managed using the lousy
> gmail interface. I stopped using my gmail account when they subscribed
> me there.

The appropriate place for this type of comment is on the summer
administrators list - silently unsubscribing yourself means you're
risking missing important info.

If that's an acceptable risk for you, then so be it. The choice is
yours, and I can't force you to sign up.

Cheers,
Dave.

-- 
Dave Neary
[EMAIL PROTECTED]
Lyon, France
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: SoC mentors & students: mid-term evaluations!

[Michael Schumacher]

Sven Neumann wrote:

> On Mon, 2006-07-03 at 11:03 +0200, Dave Neary wrote:
> 
>> For mentors, it is not just recommended to be subscribed here, it is a
>> requirement - as in this case, important information about the program
>> is sent to this list, and I have been working on the assumption that all
>> GIMP mentors are subscribed there.

> Sorry, but the amount of traffic coming in due to this list is not
> acceptable, especially since it can hardly be managed using the lousy
> gmail interface. I stopped using my gmail account when they subscribed
> me there.

Then it's probably ok to play the human gateway once more and tell
everyone that

- the deadline has been extended once more to July 10th
- you are required to check any already completed surveys due to some
bug fixes and possible changed values

And finally, organization admins might get an overview of the survey status.


HTH,
Michael

P.S. you don't need to use GMail to read this list, I'm subscribed with
my gmx mail address, too.

-- 
GIMP > http://www.gimp.org  | IRC: irc://irc.gimp.org/gimp
Wiki > http://wiki.gimp.org | .de: http://gimpforum.de
Plug-ins > http://registry.gimp.org |
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] XCF format specification

[Sven Neumann]

Hi,

On Wed, 2006-07-05 at 20:44 +0200, Henning Makholm wrote:

> Related to this: While researching the format I discovered a buffer
> overrun somewhere in the XCF parsing code. Is there a recommended way
> to report security bugs confidentially? (I asked on IRC and was
> encouraged to just use the public bugzilla, but I'm uncomfortable by
> following such advice gathered on a lazy IRC channel).

Please use Bugzilla as you have been told on #gimp.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] menu cluttage

[Sven Neumann]

Hi,

On Tue, 2006-07-04 at 01:11 -0400, Kevin Cozens wrote:

> Now that GIMP handles registration of the same menu item from different
> plug-ins, I am just waiting for the time a user reports a bug in Whirl and
> Pinch (for example) and doesn't realize which version they were using (as in
> the Python version or the C version).

The Python version will of course not be in any stable release.

And so far I don't see anyone complaining about my proposal to not
install any Python scripts at all with GIMP 2.4.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Script-Fu procedure blurb review

[Sven Neumann]

Hi,

On Sat, 2006-07-01 at 11:59 +0100, Alan Horkan wrote:

> The switch over to Tiny-Fu will result in a certain amount of
> incompatibilities anyway so it might be a good time to reconsider.

We are most likely not going to do the switch to Tiny-Fu until those
incompatibilities have been sorted out. There might be some scripts that
will stop to work when Script-Fu is changed to use the tiny-fu
interpreter, but those scripts can basically be considered broken
already. Broken because they are using undocumented misbehaviour of the
SIOD interpreter.

> > it makes a lot of sense to clean up the short strings now. Other changes
> > can be considered after 2.4.
> 
> CVS will still have the long descriptions if anyone wants to go back and
> add then in again.

Now you are forcing me to repeat myself again. There are basically no
scripts in CVS that have a long description. The scripts are merely
undocumented. If more than five scripts would use anything longer than
half a sentence as their help string, we would of course not throw it
away.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Gimp-developer] XCF format specification

[Henning Makholm]

The XCF file format is currently documented primarily by the Gimp
source, and by the very old and sketchy devel-docs/xcf.txt in the
source tree.

I have attempted to write a better specification, encouraged by Dave
Neary and partly based on my experiences writing a third-party XCF
reader (xcftools, at ). It is at

   http://henning.makholm.net/xcftools/xcfspec.txt

I would like to contribute it as a replacement for xcf.txt, but I
would like it to be correct first. I would appreciate it if somebody
who are familiar with the format could look over my text and check it
for obvious mistakes.


Related to this: While researching the format I discovered a buffer
overrun somewhere in the XCF parsing code. Is there a recommended way
to report security bugs confidentially? (I asked on IRC and was
encouraged to just use the public bugzilla, but I'm uncomfortable by
following such advice gathered on a lazy IRC channel).

-- 
Henning Makholm"*Vi vil ha wienerbrød!*"
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] What is the roadmap / plan for GIMP development?

[Sven Neumann]

Hi,

On Tue, 2006-07-04 at 16:44 +0200, Jesper de Jong wrote:
> Is there a roadmap or release planning for GIMP development?

There's bugzilla, it has milestones and you can do queries for them.
That's the tentative roadmap. Other than that, things get implemented
when someone finds the time and motivation to implement them.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: SoC mentors & students: mid-term evaluations!

[Sven Neumann]

Hi,

On Mon, 2006-07-03 at 11:03 +0200, Dave Neary wrote:

> 
> For mentors, it is not just recommended to be subscribed here, it is a
> requirement - as in this case, important information about the program
> is sent to this list, and I have been working on the assumption that all
> GIMP mentors are subscribed there.
> 
> In fact, I had understood that mentors were automatically subscribed to
> the list on being accepted as mentors - this is what happened for me.

Sorry, but the amount of traffic coming in due to this list is not
acceptable, especially since it can hardly be managed using the lousy
gmail interface. I stopped using my gmail account when they subscribed
me there.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] feature request

[Sven Neumann]

Hi,

On Sun, 2006-07-02 at 10:38 +0200, Marco Ciampa wrote:

> Why not to bring all the GIMP windows up over all the others windows when I
> clic on to one of the many GIMP windows?

Because it isn't trivial to do that. You can try the transient windows
option in the Preferences dialog of a recent 2.3 development release.
See http://svenfoo.geekheim.de/index.php/2005-05-12/transient-docks/ for
more info.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: Compiling problem with Gimp 2.3.9 in FreeBSD 6.1

[Tim Mooney]

In regard to: [Gimp-developer] Re: Compiling problem with Gimp 2.3.9 in...:


On 7/1/06, Haarald Sinihammas <[EMAIL PROTECTED]> wrote:


Well, now i can post exact info:

Configure command is:
./configure LDFLAGS=-L/usr/local/lib CFLAGS=-I/usr/local/include/
CPPFLAGS=-I/usr/local/include/

if i doing gmake, then i get for last:

 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DXTHREADS -DXUSE_MTSAFE_API
-I/usr/local/include/atk- 1.0 -I/usr/local/include/cairo
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-I/usr/X11R6/include/gtk-2.0 -I/usr/X11R6/lib/gtk-2.0/include
-I/usr/X11R6/include/pango-1.0 -I/usr/X11R6/include
-I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include
-DG_LOG_DOMAIN=\"LibGimp\" -D_REENTRANT -I/usr/local/include/glib- 
2.0-I/usr/local/lib/glib-

2.0/include -I/usr/local/include/ -DGIMP_DISABLE_DEPRECATED
-DG_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED
-DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED
-DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -I/usr/local/include/ -Wall -MT
gimp.lo -MD -MP -MF .deps/gimp.Tpo -c gimp.c  -fPIC -DPIC -o .libs/gimp.o
gimp.c: In function `gimp_main':
gimp.c:340: error: `SIGBUS' undeclared (first use in this function)
gimp.c:340: error: (Each undeclared identifier is reported only once
gimp.c:340: error: for each function it appears in.)
gimp.c:349: error: `SA_RESTART' undeclared (first use in this function)
gimp.c: In function `gimp_extension_process':


I tried to respond earlier, but got a bounce.

See

http://bugzilla.gnome.org/show_bug.cgi?id=344203

It's marked as fixed in CVS.

Tim
--
Tim Mooney  [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building  (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Gimp-developer] Re: Compiling problem with Gimp 2.3.9 in FreeBSD 6.1

[Haarald Sinihammas]

Hello again!I don't find any solution yet. Seems like signal.h is not included - but why?If anybody need more information or clarification to help in this problem, please tell me.Thanks in advance,
HaaraldOn 7/1/06, Haarald Sinihammas <[EMAIL PROTECTED]> wrote:
Well, now i can post exact info:Configure command is:./configure LDFLAGS=-L/usr/local/lib CFLAGS=-I/usr/local/include/ CPPFLAGS=-I/usr/local/include/if i doing gmake, then i get for last: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DXTHREADS -DXUSE_MTSAFE_API -I/usr/local/include/atk-
1.0 -I/usr/local/include/cairo -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include/gtk-2.0 -I/usr/X11R6/lib/gtk-2.0/include -I/usr/X11R6/include/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DG_LOG_DOMAIN=\"LibGimp\" -D_REENTRANT -I/usr/local/include/glib-
2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/ -DGIMP_DISABLE_DEPRECATED -DG_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -I/usr/local/include/ -Wall -MT 
gimp.lo -MD -MP -MF .deps/gimp.Tpo -c gimp.c  -fPIC -DPIC -o .libs/gimp.ogimp.c: In function `gimp_main':gimp.c:340: error: `SIGBUS' undeclared (first use in this function)gimp.c:340: error: (Each undeclared identifier is reported only once
gimp.c:340: error: for each function it appears in.)gimp.c:349: error: `SA_RESTART' undeclared (first use in this function)gimp.c: In function `gimp_extension_process':gimp.c:1335: error: syntax error before "readfds"
gimp.c:1349: warning: implicit declaration of function `FD_ZERO'gimp.c:1349: error: `readfds' undeclared (first use in this function)gimp.c:1350: warning: implicit declaration of function `FD_SET'gimp.c:1352: warning: implicit declaration of function `select'
gimp.c:1352: error: `FD_SETSIZE' undeclared (first use in this function)gimp.c: In function `gimp_plugin_sigfatal_handler':gimp.c:1475: error: `SIGBUS' undeclared (first use in this function)gmake[2]: *** [
gimp.lo] Error 1gmake[2]: Leaving directory `/usr/home/zwoz/Desktop/Downloads/gimp-2.3.9/libgimp'gmake[1]: *** [all-recursive] Error 1gmake[1]: Leaving directory `/usr/home/zwoz/Desktop/Downloads/gimp-2.3.9'

gmake: *** [all] Error 2
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] menu cluttage

[Alan Horkan]

On Tue, 4 Jul 2006, Fennec wrote:

> Date: Tue, 04 Jul 2006 11:13:47 -0400
> From: Fennec <[EMAIL PROTECTED]>
> Cc: gimp-developer@lists.xcf.berkeley.edu
> Subject: Re: [Gimp-developer] menu cluttage
>
> [EMAIL PROTECTED] wrote:
> > Currently the GIMP on Windows has 1 icon that is used for all file formats
> > associated with it. It would be possible to have separate icons for every
> > format handled by the GIMP, but somebody would have to create them.

> I don't suppose the Tango project has anything we could swipe, does it?
> We should ask them to do it. :)

The gnome (and tango) icons sizes aren't particularly useful on Windows.

You might be better off to try checking the gimp Windows mailing list, I
vaguely recall previous attempts to create a suitable set of document
icons but I dont know if anything came of it.

-- 
Alan
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] menu cluttage

[Jakub Steiner]

On Tue, 2006-07-04 at 11:13 -0400, Fennec wrote:
> [EMAIL PROTECTED] wrote:
> > Currently the GIMP on Windows has 1 icon that is used for all file formats
> > associated with it. It would be possible to have separate icons for every
> > format handled by the GIMP, but somebody would have to create them.
> I don't suppose the Tango project has anything we could swipe, does it? 
> We should ask them to do it. :)

Hi.
Actually I've been trying to avoid the mimetype hell and only drawn
generic types for now. Making a distinct icons for XCFs may sound like a
usable thing to do. But I don't think having a distinct icon for each
and every image type out there will bring us any good.

cheers

-- 
Jakub Steiner <[EMAIL PROTECTED]>

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer