Re: [Gimp-developer] GIMP 2.3.4
I compiled GIMP 2.3.4 from tarball the other day and I've noticed a few things. 1) The last 2 times I've compiled GIMP, I've found my installation missing some key libraries at the end of the build. Is this normal? (Missing libraries differed each time) To fix it I pulled libraries from my stable GIMP 2.2 installation and that seems to work but some odd things occur in the build that I wouldn't expect - even of a development release. 2) One of those odd things is that the entire layer dialog is non-responsive. No lock ups or anything, it just sits there, does nothing (even when layers are created, etc), and doesn't accept commands. Is this to be expected in the 2.3.4 release or should I expect that something else is wrong. Here are my system specs Windows XP SP2, GTK+ 2.6.9 MinGW, MSys, ActivePerl I built GIMP 2.3.4 with Glib 2.8.0 and GTK+ 2.6.9. I also used atk 1.9.0 and pango 1.8.2 The other dependencies (for various plugins) were the latest stable versions that I could find. Any ideas what might cause this type of behavior? Sven Neumann wrote: Hi, Michael Schumacher [EMAIL PROTECTED] writes: Reinstalling the same version wouldn't help, I'm talking about a hard timeout there - created when the release tarball is made, for example, and set to e.g. 60 or 90 days into the future. What's all this fuss? There is absolutely no reason why we should cripple any GIMP release, development version or not, by doing such silly things. This is Free Software. We are distributing it as source code. If someone wants to build binaries and distribute them, so be it. You might not have noticed yet, but binary distribution of the GIMP 2.3 series is not in any way discouraged. Of course we appreciate if pacakagers make it clear that they are distributing an unfinished development release but that's something we can only ask for. Sven ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ 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
On Tuesday 27 September 2005 21:01, [EMAIL PROTECTED] wrote: http://eyegene.ophthy.med.umich.edu/unicode/fontdialog/ snipped We on the Scribus Team have struggled with this too and with the changes in our 1.3.x series to enhance non-Latin support and complex glyphs will make this even more important. We have made some improvements vis a vis 1.2.x, but its not a 100% solution. I would recommend you bring this to [EMAIL PROTECTED] as well, as well as the Scribus mailing list. I am sure this will be considered carefully. Your site is an excellent resource and already on our links page on www.scribus.net Cheers, Peter ___ 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
Hi, Lance Dockins [EMAIL PROTECTED] writes: I compiled GIMP 2.3.4 from tarball the other day and I've noticed a few things. 1) The last 2 times I've compiled GIMP, I've found my installation missing some key libraries at the end of the build. Is this normal? (Missing libraries differed each time) To fix it I pulled libraries from my stable GIMP 2.2 installation and that seems to work but some odd things occur in the build that I wouldn't expect - even of a development release. You did what??? There is really no point in doing such things unless you know very well what you are doing. If you have problems to compile GIMP, ask. And if you ask, please describe your problems in detail. I have left my crystal ball at home today so I really can't figure out what some missing key libraries at the end of the build are. Sven ___ 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 H. Trager [EMAIL PROTECTED] writes: ... 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. Interesting. The GIMP font selection scheme does certainly leave a lot to desire. There are some good suggestions in Bugzilla, just waiting to be implemented: http://bugzilla.gnome.org/show_bug.cgi?id=137624 http://bugzilla.gnome.org/show_bug.cgi?id=150500 and somewhat related but more technical: http://bugzilla.gnome.org/show_bug.cgi?id=168102 The proposal also attempts to fully address aspects of internationalization related to font selection that I believe have been largely overlooked until now. I don't think they've been overlooked. At least for the GIMP font selection, the reason for the fact that the font selection is still that simple, is lack of developer resources. Providing a common framework might help to overcome this problem. Finally, the proposal suggests using a common XML configuration file which for storing font collection information. Could this perhaps become part of fontconfig? We already have XML font configuration there. Loading another XML file would slow down startup further. Sven ___ 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
On 9/27/05, Edward H. Trager [EMAIL PROTECTED] wrote: ... 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 http://eyegene.ophthy.med.umich.edu/unicode/fontdialog/ As a user, this sounds like a very awesome proposal, and if implemented, would revolutionize font GUIs for users. I don't know whether it could cause a problem with Usability (e.g. Text to Speech systems) though... Just a note (and yes, I'm nit-picking), but there is no such thing as 'a Chinese pangram'. Chinese uses individual characters for every word (AFAIK), so you'll just have to choose some sample text that is representative of the language, or make some up. IIRC, Japanese has an alphabet, though, and Chinese has a sort of 'proununciation' alphabet (but that's seperate). -- ~Mike - Just my two cents - No man is an island, and no man is unable. ___ 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
Nice proposal. A lot of apps could benefit from a good shared font selector -- it's not just an issue of one app, as you point out. I love the idea of font groupings. I don't mind editing an XML file, but I'm sure it wouldn't take much to whip up an app to help people customize their downloaded fonts, compared with the rest of the work involved in the proposal. Tooltips over menus can be really annoying, because while they're showing more information about one entry they're preventing you from scanning all the other entries. You can move the mouse outside the menu, but it's a shame to have to mouse in to scroll, then quickly mouse out before the tooltip blocks the list you're trying to read. Please consider making that part optional, or skipping it. One more UI issue you don't address: the length of the font list can be a problem, especially if you have a lot of fonts installed. The current GIMP font list (and your proposal looks similar) pops up as a combobox that shows, on my system, 9 fonts at a time. Exploring the whole list through this small window takes a long time and a lot of clicking. Sometimes I really miss having a font selector dialog which I could resize to show a long list, so that I could scan through more quickly without needing to scroll so many times. ...Akkana ___ 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 H. Trager wrote: I welcome the community's suggestions and criticisms -- One easily overlooked feature which I consider to be most important is keyboard support. 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. All the best, -- Alastair M. Robinson ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
