Re: [Gimp-developer] menu cluttage

2006-07-08 Thread Alan Horkan

On Wed, 5 Jul 2006, Jakub Steiner wrote:

> Date: Wed, 05 Jul 2006 12:57:49 +0200
> From: Jakub Steiner <[EMAIL PROTECTED]>
> To: Fennec <[EMAIL PROTECTED]>
> Cc: gimp-developer@lists.xcf.berkeley.edu
> Subject: Re: [Gimp-developer] menu cluttage
>
> 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.

It is certainly useful to have icons for the major types.
One icon to rule them all is not enough.

There was some concern when the icons were changed so that PNG and JPEG
had the same icons since it is particulaly useful to distinguish the
losless and lossey formats.  (I'm not sure if that was Tango/Ubuntu/Gnome
exactly and this may well have been fixed already since I last noticed
it.)

I understand you dont want to create icons for every type of graphics file
format but it might also be useful to have an icon for XCF, PSD, MNG and
perhaps other layered image file formats.

The icons in Windows were rubbish but Windows/Internet explorer did at
least provide 'picture frame' style icons for GIF, JPEG, and PNG with each
having a different central colour (green, red and pink respectively).
One option might be for the windows installer to leave the default icons
alone for these types (use the default icons provided by windows) and only
set the gimp document Icon for XCF and a few other gimp specific formats?
I've manually changed the icons like this in the past but other programs
have long since stolen the file associations back again and now only a few
of my files have the gimp icon on them.  If this sounds like what windows
users want they should talk sweetly to the developer who puts together the
windows installer.

-- 
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

2006-07-08 Thread Alan Horkan

On Wed, 5 Jul 2006, Joao S. O. Bueno Calligaris wrote:

> Date: Wed, 5 Jul 2006 21:36:51 -0300
> From: Joao S. O. Bueno Calligaris <[EMAIL PROTECTED]>
> To: gimp-developer@lists.xcf.berkeley.edu
> Subject: Re: [Gimp-developer] menu cluttage
>
> 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.

There is an equivalent web slice written in Script-fu.  I have my own
modofied copy lying around somewhere but if I recall correctly you can
find the original in the gimp plugin registry.

It will be good to have the Python support turned on by default on windows
so that developers (script writers) can count on it being there but not
including the redundant scripts isn't any great loss.

--
Alan H.

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