Re: [Gimp-developer] GTK+ 2.6, Pango 1.8

2005-02-09 Thread Raphaël Quinet
On Tue, 08 Feb 2005 22:10:37 +0100, Michael Natterer [EMAIL PROTECTED] wrote: Gimp CVS HEAD depends on GTK+ = 2.6.0 and Pango = 1.8.0 now. Some changes which make use of the new features and/or remove ugly hacks due to the lack of these features have already landed in CVS. For anyone trying

Re: [Gimp-developer] file handling, something for GIMP 2.4 ?

2005-02-09 Thread geert jordaens
Hi, if we where to write a vfs for gimp the links below provide some basic information. Anyway it helped me to understand the thread. http://www.flipcode.com/articles/article_vfs01.shtml http://koti.mbnet.fi/heitsu/vfs Geert ___ Gimp-developer mailing

[Gimp-developer] Re: color management

2005-02-09 Thread Jordi Cantón
I just released version 0.1.0 of the gimp-color-manager plugin. Important changes since last version: -Re-design of the user interface in order to clarify the workflow (Thanks to Hal suggestions) -I correct several bugs found in the code -Now it should also work on a windows box. I made a

Re: [Gimp-developer] Re: color management

2005-02-09 Thread Hal V. Engel
I just installed and tested this latest version. At this point it is good enough to be of use for those that need/want color management. The changes that were made between version 0.0.9 and this version were mostly to the user interface (big improvement) and some bug fixes. I have also

Re: [Gimp-developer] CVS HEAD dependency on glib-2.6 / gtk+-2.6

2005-02-09 Thread pcg
On Mon, Feb 07, 2005 at 11:01:07PM +0100, Sven Neumann [EMAIL PROTECTED] wrote: How would that be specific to GIMP? The problem is that there is not only the combo-box. There's a full directory view below it. It's hidden in an expander but that doesn't change the fact that it is there. On my

Re: [Gimp-developer] CVS HEAD dependency on glib-2.6 / gtk+-2.6

2005-02-09 Thread William Skaggs
Marc Lehmann wrote: On my screen, there isn't. It doesn't matter to the user how something is implemented internally, and that it is hidden but there. by default, it's not there (displayed), and it's hard to imagine why a uI element that is hidden and not used in many cases should require the