Re: [Gimp-developer] Designing a Better Font Selection Widget for use in Open Source Software
Hi, Roman Joost <[EMAIL PROTECTED]> writes: > I really like the fact, that the fonts are categorized. That is > something which I really miss in the font selection dialogs currently. > If a user has installed a motherload of fonts, he mostly has to scroll > and scroll and scroll to pick a font. Using a drop down widget has the > disadvantage, that I still have to scroll like mad to pick a font, even > if they are categorized. I'm able to find the font much faster, but > picking a font is cumbersome as it is now. Just a hint, in case you or someone else didn't notice yet: If you know the name of the font, you can limit the fonts being displayed in the dropdown list using the text entry next to the font button. Sven ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Designing a Better Font Selection Widget for use in Open Source Software
Hi, [EMAIL PROTECTED] (2005-09-27 at 1336.45 -0400): > This message is an open letter to: [...] > ... regarding a proposal for an improved font selection drop-down > widget that would be ideal for use in professional-quality Open Source > word processing, desktop publishing, and graphic design programs > such as OpenOffice.org, Gimp, Inkscape, and similar > programs. [...] > The proposal at http://eyegene.ophthy.med.umich.edu/unicode/fontdialog/ > addresses how these goals can be met. Implementation of the proposed > font selection widget at the GUI toolkit level (i.e., in GTK+ and in KDE) > along with an XML-based configuration scheme standardized across > toolkits and desktops would do much to help create a more intuitive and > more uniform user experience on Linux and related Open Source platforms. > > I welcome the community's suggestions and criticisms -- I doubt a menu is a good idea, both from coding and user point of view, as a huge menu is nasty for speed. Menu creation takes time or a lot of effort to make it really fast (the coding part) and so does navigating it, penalizes failure or experimentation and disallows keeping it open (the user part). A window more like the MacOSX one would be better, IMO. The preview as name, on the other hand, would be a nice addition to the dialog. It could even become a helper tool, like calculator ones. With a simple method to pass back the info (a la popen(), no need of overengineering things), as well as copy&paste and drag&drop, it would indeed help. GSR ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Designing a Better Font Selection Widget for use in Open Source Software
Hi, [EMAIL PROTECTED] (2005-09-28 at 0142.32 +0100): > > I welcome the community's suggestions and criticisms -- > One easily overlooked feature which I consider to be most important is > keyboard support. Indeed. > In many Windows apps (and OpenOffice), I can type the first few > characters into the font selector combo and that's usually enough to > narrow it down to the font I'm going to use. This feature makes an > *incredible* difference to working efficiency. Yet another overlooked feature is being able to search for something in the middle. GSR ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Another nice donation
Hi all, Just letting people know that we got a nice donation to the GIMP of $1000 from people at BackupAssist.com. In the words of Matthew Lim, who was the guy who asked that they donate, and he said his boss was "willing to donate $1000 [...] because the GIMP saves us money over Adobe". In the next couple of days, I'd like to update the donors page to acknowledge the money coming in through the friends of GIMP (I may not have time for the next few days though). If anyone else is able to help with this, it would be appreciated. Please email me if you have 3 or 4 hours of availability to do some drudge work over the next couple of weeks. And you like that kind of thing :) Cheers, Dave. -- David Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.3.4 crash on winxp
John Cupitt writes:
> > glib-2.8.2 glib-dev-2.8.2 gtk+-2.8.4 gtk+-dev-2.8.4 pango-1.10.0
> > pango-dev-1.10.0 atk-1.10.1 atk-dev-1.10.1 cairo-1.0.0 cairo-dev-1.0.0
> You pango and atk seem very old, but your glib and gtk seem too new.
No, atk 1.10.1 and Pango 1.10.0 are quite new, the latest
versions. (Actually, for performance reasons, one should make sure to
use the latest pango 1.10.0 snapshot (20050922) from the ftp.gtk.org
site.) (GTK+ 2.8 won't even work with any older Pango.) They are
available from ftp.gtk.org but not really "advertised" yet on the GTK+
for Win32 download page on the GIMP site.
Sigh, I had hoped that the infamous "shape.c: line 75" assertion
failure would have been a thing of the past with GTK+ 2.8 and Pango
1.10. But apparently not. Try the usual stuff, mainly try without the
ms-windows theme ("wimp"). (Edit the etc/gtk-2.0/gtkrc file.) Or check
what your default font in the Display Properties is, try changing that
to for instance Arial.
--tml
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: R: [Gimp-developer] GIMP 2.3.4 crash on winxp
On 9/30/05, Paolo Magnoli <[EMAIL PROTECTED]> wrote: > Sorry but my pango is pango-1.10.0 when Thor's one is pango-1.8.2, so mine > should be more recent. D'oh! Sorry. So it sounds like a pango fonts problem. Do any of the pango examples work? ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
R: [Gimp-developer] GIMP 2.3.4 crash on winxp
Sorry but my pango is pango-1.10.0 when Thor's one is pango-1.8.2, so mine should be more recent. Regards paolo > -Messaggio originale- > Da: John Cupitt [mailto:[EMAIL PROTECTED] > Inviato: venerdì 30 settembre 2005 11.18 > A: Paolo Magnoli > Cc: GIMPDev > Oggetto: Re: [Gimp-developer] GIMP 2.3.4 crash on winxp > > > On 9/30/05, Paolo Magnoli <[EMAIL PROTECTED]> wrote: > > Hi, I just compiled Gimp 2.3.4 on winxp mingw but when I try to > run it I get > > a windows with this error: > > > > "Pango-ERROR**: file shape.c: line 75 (pango_shape): assertion failed: > > (glyphs->num_glyphs > 0) aborting ..." > > > > then it closes down. > > My GTK libs are: > > glib-2.8.2 glib-dev-2.8.2 gtk+-2.8.4 gtk+-dev-2.8.4 pango-1.10.0 > > pango-dev-1.10.0 atk-1.10.1 atk-dev-1.10.1 cairo-1.0.0 cairo-dev-1.0.0 > > You pango and atk seem very old, but your glib and gtk seem too new. > I'd try again with the packages on Tor's download page: > > http://www.gimp.org/~tml/gimp/win32/downloads.html > > John > ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.3.4 crash on winxp
On 9/30/05, Paolo Magnoli <[EMAIL PROTECTED]> wrote: > Hi, I just compiled Gimp 2.3.4 on winxp mingw but when I try to run it I get > a windows with this error: > > "Pango-ERROR**: file shape.c: line 75 (pango_shape): assertion failed: > (glyphs->num_glyphs > 0) aborting ..." > > then it closes down. > My GTK libs are: > glib-2.8.2 glib-dev-2.8.2 gtk+-2.8.4 gtk+-dev-2.8.4 pango-1.10.0 > pango-dev-1.10.0 atk-1.10.1 atk-dev-1.10.1 cairo-1.0.0 cairo-dev-1.0.0 You pango and atk seem very old, but your glib and gtk seem too new. I'd try again with the packages on Tor's download page: http://www.gimp.org/~tml/gimp/win32/downloads.html John ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] GIMP 2.3.4 crash on winxp
Hi, I just compiled Gimp 2.3.4 on winxp mingw but when I try to run it I get a windows with this error: "Pango-ERROR**: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0) aborting ..." then it closes down. My GTK libs are: glib-2.8.2 glib-dev-2.8.2 gtk+-2.8.4 gtk+-dev-2.8.4 pango-1.10.0 pango-dev-1.10.0 atk-1.10.1 atk-dev-1.10.1 cairo-1.0.0 cairo-dev-1.0.0 And other mingw packages are: libpng-1.2.8-bin libpng-1.2.8-dep libpng-1.2.8-lib jpeg-6b-4-bin jpeg-6b-4-dep jpeg-6b-4-lib tiff-3.7.2-bin tiff-3.7.2-lib freetype-2.1.8-bin freetype-2.1.8-lib zlib-1.2.2-bin zlib-1.2.2-lib libgw32c-0.4-lib libiconv-1.8-1-bin libiconv-1.8-1-lib Hope you'll find a way to solve this. Thanks in advance paolo ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Designing a Better Font Selection Widget for use in Open Source Software
Hi Edward, thanks for you proposal. On Tue, Sep 27, 2005 at 01:36:45PM -0400, Edward H. Trager wrote: > To see the full proposal, please see: > > http://eyegene.ophthy.med.umich.edu/unicode/fontdialog/ > > The rest of this email provides a synopsis of the proposal. Speaking as a user here, I'm not sure if your proposal of a drop down is really what solves the problem here. I really like the fact, that the fonts are categorized. That is something which I really miss in the font selection dialogs currently. If a user has installed a motherload of fonts, he mostly has to scroll and scroll and scroll to pick a font. Using a drop down widget has the disadvantage, that I still have to scroll like mad to pick a font, even if they are categorized. I'm able to find the font much faster, but picking a font is cumbersome as it is now. In fact, the only dialog which I endore is the font dialog from Apples Mac OS X. You still have to scroll to pick a font, if there are lots of fonts in one category, but it minimizes the effort. Well, just my 2 cents to your proposal :) Greetings, -- Roman Joost www: http://www.romanofski.de email: [EMAIL PROTECTED] pgp7DqfMmwmPB.pgp Description: PGP signature
