> > This is not at all a distribution issue. Linux is a *multi*-user system, so
>
> a good answer for it. From my point of view, Gimp is not a multi-user tool
> (even if it can run happily on multi-user systems) so should be packaged
> for single users. University admins would probably argue ot
> Well, I don't know of anyone using it frequently. Only probably to
> look up or change keybindings, so I guess we can easily add another
> level of submenus in here. A menu that doesn't fit into 640x480 is
> indeed a bug.
Sven, EVERY menu can be made to not fit on ANY screen size. The problem
On Thu, Jan 27, 2000 at 10:44:34AM -0100, Mike <[EMAIL PROTECTED]> wrote:
> get_text_fontname is called with a font size argument of -112, which of course
> doesn't make sense, and causes the sigsegv.
i'll look into that ;) Maybe a constraint is missing somewhere.
> Having corrected the subrouti
Marc Lehmann spontaneously blurts out:
>
> The solution to too large menus is a better way to display them, not
> demanding that I use the same font as you.
>
Exactly! Scaling is one of the the biggest problems with modern (especially
Open Source) GUI design. Stuff gets written to accommodate t
On Sat, 29 Jan 2000 11:27:16 -0600 (CST), Dean Johnson <[EMAIL PROTECTED]> said:
>EVERY gui developer (casual or not) should be required to read
>Tufte's design books before being allowed to code.
Heh. Send me copies and I'll gladly read them. :)
Kelly
Kelly Lynn Martin spontaneously blurts out:
>
> On Sat, 29 Jan 2000 11:27:16 -0600 (CST), Dean Johnson <[EMAIL PROTECTED]> said:
>
> >EVERY gui developer (casual or not) should be required to read
> >Tufte's design books before being allowed to code.
>
> Heh. Send me copies and I'll gladly rea
Here is an interesting colormanagement for future GIMP releases:
http://www.abaforum.es/martim/lcms.htm
http://www.efg2.com/Lab/Library/Color.htm
Howdy,
Is there a feature request database for Gimp? If not, I would like to
request that a bug group for feature requests (preferrably with some
level of urgency) be added to the bugtracker on sourceforge. It would
be nice to have an exhaustive list of what people wanted and not depend
on "insti
On Sat, Jan 29, 2000 at 02:28:47PM -0600, Dean Johnson wrote:
> Howdy,
> Is there a feature request database for Gimp?
Yes, file a bug as usual, but set your (is it urgency? priority? I
don't remember, but I'm pretty sleepy right now) to show that it's a
feature request/ request for enhancement.
On Sat, 29 Jan 2000 14:28:47 -0600 (CST), Dean Johnson <[EMAIL PROTECTED]> said:
>Howdy, Is there a feature request database for Gimp? If not, I would
>like to request that a bug group for feature requests (preferrably
>with some level of urgency) be added to the bugtracker on
>sourceforge. It wo
On Sat, Jan 29, 2000 at 04:38:52PM -0500, Kelly Lynn Martin wrote:
> If by "color table" you mean the indexed color palette, that will
> require core modifications (I believe) because I don't think palettes
> are exposed to plug-ins well enough to do operations on them.
What do you mean by "well
On Sat, Jan 29, 2000 at 12:39:09PM -0500, Kelly Lynn Martin
<[EMAIL PROTECTED]> wrote:
> >EVERY gui developer (casual or not) should be required to read
> >Tufte's design books before being allowed to code.
>
> Heh. Send me copies and I'll gladly read them. :)
Selecting a very large or very sm
On Sat, Jan 29, 2000 at 11:41:17AM -0500, Kelly Lynn Martin
<[EMAIL PROTECTED]> wrote:
> If Mitch has gone to the effort to normalize existing plug-ins, I
> think would be nice of him to write up exactly what standards he
> followed so we can have a nice document on plug-in UI standards. :)
Inde
On Sat, 29 Jan 2000 21:53:47 +, Nick Lamb <[EMAIL PROTECTED]> said:
>All the existing plug-ins that work with palettes (INDEXED images
>would be even more useless than they already are if no plug-ins could
>work with them) use calls like:
I guess it's GIMP palettes that are badly exposed. I
On Sat, Jan 29, 2000 at 04:38:52PM -0500, Kelly Lynn Martin
<[EMAIL PROTECTED]> wrote:
> GIMP feature requests should be submitted as "severity: wishlist" to
> the GNOME bug tracker. However, requests to _write plug-ins_ can be
> submitted as low-priority "bugs" on the Sourceforge page.
Unfor
On Sat, Jan 29, 2000 at 09:53:47PM +, Nick Lamb <[EMAIL PROTECTED]> wrote:
> What do you mean by "well enough to do operations on them" ?
Probably "You cannot read/modify/list/do anything with the colormaps in
the gimp."
The only thing you can work on is the colormap of some indexed image. B
On Sun, 30 Jan 2000 00:11:47 +0100, Marc Lehmann <[EMAIL PROTECTED]> said:
>If there were a way of adding a prominent notice like "DO NOT USE
>THIS BUG-TRACKER TO REPORT GIMP BUGS, INSTEAD, GO TO http..."...
Have you asked Sourceforge?
Kelly
On Sat, Jan 29, 2000 at 07:08:49PM -0500, Kelly Lynn Martin
<[EMAIL PROTECTED]> wrote:
> >If there were a way of adding a prominent notice like "DO NOT USE
> >THIS BUG-TRACKER TO REPORT GIMP BUGS, INSTEAD, GO TO http..."...
>
> Have you asked Sourceforge?
I would rather have them fixed their %$
On Sun, Jan 30, 2000 at 12:10:16AM +0100, Marc Lehmann wrote:
> Probably "You cannot read/modify/list/do anything with the colormaps in
> the gimp."
Well, the mail I replied to (from Kelly I think) talked about indexed
palettes or colourmaps or somesuch, and the word indexed to me means
the kind
On Sun, Jan 30, 2000 at 01:31:52AM +, Nick Lamb <[EMAIL PROTECTED]> wrote:
> Well, the mail I replied to (from Kelly I think) talked about indexed
> palettes or colourmaps or somesuch, and the word indexed to me means
> the kind applied to INDEXED images. So I explained how to get at them
> fr
On Sun, Jan 30, 2000 at 02:38:07AM +0100, Marc Lehmann wrote:
> So plug-ins should duplicate the palette file parser, scan all direcrories
> where gimp looks for palette files to find the palette is looking for, and
> then restart gimp to take notice of the changed files?
"duplicate the palette f
On Sun, Jan 30, 2000 at 02:10:33AM +, Nick Lamb <[EMAIL PROTECTED]> wrote:
> "duplicate the palette file parser" rather overstates the problem, if
You picked probably the least important problem :(
> Then you open a dialog which says 'Sorry about this old chap, but
> I'm afraid you'll have t
On Sun, 30 Jan 2000 01:31:52 +, Nick Lamb <[EMAIL PROTECTED]> said:
>Gimp palettes are files :)
Yes, but when you have LOTS of custom palettes, having "Reload" as the
only way to get a new palette into the GIMP is NOT pleasant. (I have
hundreds of custom palettes and have had, at times, THO
Ar't writes:
> proposition (despite Gimp freezing):
I like your idea. (I still think it's definitely inappropriate to add
this kind of new functionality, even if it is very nice, to GIMP 1.1
(1.2), sorry.)
However, I don't quite see how dragging the mouse around in the
popped-up window could be
On Sat, 29 Jan 2000 10:53:54 +0200 (FLE Standard Time), Tor Lillqvist <[EMAIL PROTECTED]>
said:
>Drag small circles clockwise to increase V, counter-clockwise to
>decrease V, for instance. It's hard to say without experimenting...
Ew! What an evil idea!
Kelly
Thus spoke Marc Lehmann
> This is not at all a distribution issue. Linux is a *multi*-user system, so
> there is not much sense in tailoring the number of installed plug-ins to the
> needs of, say, the admin.
Playing the devils advocate here, you could also say there is not much
sense in tailorin
>
> Does translation of filter help tips make any sense ?
> Or would it be like with internal function help tips
> and they are going to be excluded ? (1.1.6->1.1.10).
>
I'm not really sure. It surely creates lots of work for the
translators and I don't know if it is worth it. If we could
agre
On Fri, 28 Jan 2000, Michael J. Hammel wrote:
> Thus spoke Marc Lehmann
> > This is not at all a distribution issue. Linux is a *multi*-user system, so
> > there is not much sense in tailoring the number of installed plug-ins to the
> > needs of, say, the admin.
>
> Playing the devils advocate
On Fri, Jan 28, 2000 at 07:14:49PM -0700, "Michael J. Hammel"
<[EMAIL PROTECTED]> wrote:
> There are some menus that need adjusting to reduce the number of entries.
Some menus (like the file type in the file dialog) still are unusable with
some font/screen combination since most of it will be ou
On Sat, 29 Jan 2000 10:59:23 +0100, Sven Neumann <[EMAIL PROTECTED]> said:
>This is handled much better after Mitch overworked most plug-ins UI
>once again. If you still find places that should be changed, please
>provide a patch.
If Mitch has gone to the effort to normalize existing plug-ins,
Kelly Lynn Martin wrote:
>
> On Sat, 29 Jan 2000 10:59:23 +0100, Sven Neumann <[EMAIL PROTECTED]> said:
>
> >This is handled much better after Mitch overworked most plug-ins UI
> >once again. If you still find places that should be changed, please
> >provide a patch.
>
> If Mitch has gone to th
On Sun, Jan 30, 2000 at 02:09:21AM +0100, Mitch wrote:
> Kelly Lynn Martin wrote:
> > If Mitch has gone to the effort to normalize existing plug-ins, I
> > think would be nice of him to write up exactly what standards he
> > followed so we can have a nice document on plug-in UI standards. :)
>
>
On Sun, 30 Jan 2000 02:09:21 +0100, Michael Natterer <[EMAIL PROTECTED]> said:
>The main part of this standard will be: "Use the libgimp
>constructors" ;-)
Are those documented anywhere? (yeah, right)
Kelly
34 matches
Mail list logo
