[Gimp-developer] What makes the GIMP toolbox special?
hi, question: On Mon, Nov 24, 2003 at 06:42:21PM +0100, Sven Neumann wrote: Hi, Rapha??l Quinet [EMAIL PROTECTED] writes: You can already add a tools list/grid to whatever dock you like. But this list or grid of tools does not behave like the one in the toolbox, unfortunately. The grid view does not behave as set of buttons (different background color, no highlighting on mouse-over) and it is not possible to drag drop images (as mentioned in Dave's message). It would be nice to replace the main tools area in the toolbox by a grid view of the tools if these differences could be fixed. But then there would be even less reasons to treat the toolbox differently from all other docks. Exactly and that's why the toolbox is special. It holds the tool buttons, it decides what tool is active, it has the most important menu and for that reason it also creates images when things are dropped there. If the menu could also be removed or dragged to another dock, then the last difference between the toolbox and the other docks would go away. Or did I miss something important? You missed the important fact that the menu cannot be removed and that we don't intent to change this. Face it, as it stands, the toolbox is special. I really don't understand why you are questioning this. It's a fact. What about the tools that only appear in the menus? carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] What makes the GIMP toolbox special?
Hi, Carol Spears [EMAIL PROTECTED] writes: What about the tools that only appear in the menus? They are tools but not in the toolbox, so what? Actually the toolbox editor that I roughly outlined would allow you to decide for yourself which tools are in the toolbox and which can only be accessed thru the menus. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CMS under Gimp.
Am 24.11.03, 11:29 +0100 schrieb Sven Neumann: Hmm? As I already outlined, the configure check in GIMP doesn't help external plug-ins and modules. Also, GIMP does not depend on lcms now, so I wonder what exactly you are trying to do with it ...? I guessed You mean to set an variable which helps to set lcms paths and switches in the Makefile. For instance the separate plug-in from Alastair M. Robinson and the color-manager from Karl Heinz Kremer need to detect lcms separately from the main app. These are plug-ins helping to work with different colour spaces. Will they not included in gimps main release? To my plans. As I was asked by users to make cinepaints tiffreader compile in gimp because of its multilayer capabilities I like to reach the most common behaviour. Recently I started to use lcms to convert undisplayable colour spaces to RGB. So I am now able to open CMYKs and Lab to an visible image. But it is not clear at the moment how to handle it at all. Maybe the upcoming CMS framework of gimp is an better solution to handle this. Next would be to apply an embedded profile to the image data and load the converted image into the app. This could help to justify the workspace. Other CMS issues stay on my plan. I found tiff has very good colour management capabilities, so I work mostly on supporting this format. I liked to offer the compatible plug-in with all features of gimp plug-in and the additionals of cinepaint for gimps 2.0 realease. At the moment Recently a friend and I managed the plug-in to compile with gimp-1.3.23 . This is part of what I plan to give back to gimp. To work for both apps at once makes it more likely that people will enjoy the advantages of tiff . Hope this helps avoiding some further code duplication. Kai-Uwe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CMS under Gimp.
Hi, Kai-Uwe Behrmann [EMAIL PROTECTED] writes: I guessed You mean to set an variable which helps to set lcms paths and switches in the Makefile. For instance the separate plug-in from Alastair M. Robinson and the color-manager from Karl Heinz Kremer need to detect lcms separately from the main app. Separate plug-ins need to provide their own build framework. We make it relatively easy by providing pkg-config files, automake macros and a plug-in template. However third-party plug-ins and modules will need to check for lcms on their own. It's not really rocket science though and people can of course copy the check from GIMP's configure script. These are plug-ins helping to work with different colour spaces. Will they not included in gimps main release? They should probably be included at some point. Actually our goal was to move as much plug-ins out of the main distribution as possible and not to accept any new plug-ins. However since there's still no useable plug-in registry, we lately changed this policy and started to add plug-ins to the 1.3 tree. However it's a bit late to still add plug-ins for 2.0 but we can start now to implement a reasonable CMS framework in plug-ins and modules and integrate these into the distribution for the 2.2 release. To my plans. As I was asked by users to make cinepaints tiffreader compile in gimp because of its multilayer capabilities I like to reach the most common behaviour. Recently I started to use lcms to convert undisplayable colour spaces to RGB. So I am now able to open CMYKs and Lab to an visible image. libtiff does these color conversions for you already. The GIMP tiff plug-in is able to read CMYK files, not sure about Lab. The ability to read multiple pages from TIFF files should be added to GIMP's standard TIFF plug-in. This is a frequently requested feature and we are waiting for a patch for quite some time already: http://bugzilla.gnome.org/show_bug.cgi?id=66886 I liked to offer the compatible plug-in with all features of gimp plug-in and the additionals of cinepaint for gimps 2.0 realease. At the moment Recently a friend and I managed the plug-in to compile with gimp-1.3.23 . As I said, it's a bit late to get this into 2.0. But it all depends on how large the changes are. I don't think we can integrate color management at this point but a clean patch for loading multiple pages could be accepted into 2.0 still. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CMS under Gimp.
Am 26.11.03, 12:32 +0100 schrieb Sven Neumann: They should probably be included at some point. Actually our goal was to move as much plug-ins out of the main distribution as possible and not to accept any new plug-ins. However since there's still no useable plug-in registry, we lately changed this policy and started to add plug-ins to the 1.3 tree. I understand. However it's a bit late to still add plug-ins for 2.0 but we can start now to implement a reasonable CMS framework in plug-ins and modules and integrate these into the distribution for the 2.2 release. The later sounds interessting. convert undisplayable colour spaces to RGB. So I am now able to open CMYKs and Lab to an visible image. libtiff does these color conversions for you already. The GIMP tiff Yes, CMYK is converted natively by libtiff. The plug-in is able to do it with an embedded ICC profile. This may remain for the CMS framework of gimp You mentioned. plug-in is able to read CMYK files, not sure about Lab. The ability to read multiple pages from TIFF files should be added to GIMP's standard TIFF plug-in. This is a frequently requested feature and we are waiting for a patch for quite some time already: http://bugzilla.gnome.org/show_bug.cgi?id=66886 Loading it up with my login failed. Are there other ways to send it? As I said, it's a bit late to get this into 2.0. But it all depends on how large the changes are. I don't think we can integrate color management at this point but a clean patch for loading multiple pages could be accepted into 2.0 still. It is more a new plug-in in terms of size. My goal was not to split the code for different apps. So take a look on it yourselfe. Kai-Uwe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] CMS under Gimp.
Hi, Kai-Uwe Behrmann [EMAIL PROTECTED] writes: http://bugzilla.gnome.org/show_bug.cgi?id=66886 Loading it up with my login failed. Are there other ways to send it? Patches can be send to the gimp-developer mailing-list. As I said, it's a bit late to get this into 2.0. But it all depends on how large the changes are. I don't think we can integrate color management at this point but a clean patch for loading multiple pages could be accepted into 2.0 still. It is more a new plug-in in terms of size. My goal was not to split the code for different apps. So take a look on it yourselfe. I don't think we want the replace the TIFF plug-in with a completely different version at this point of development. Too many bug-fixes went into the plug-in even since GIMP-1.2. We would risk to loose these. I would prefer a set of patches. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] What makes the GIMP toolbox special?
Well ... On Wed, Nov 26, 2003 at 10:17:46AM +0100, Sven Neumann wrote: Carol Spears [EMAIL PROTECTED] writes: What about the tools that only appear in the menus? They are tools but not in the toolbox, so what? Actually the toolbox editor that I roughly outlined would allow you to decide for yourself which tools are in the toolbox and which can only be accessed thru the menus. it was such a thorough discussion of the tools and such, i was interested to see so much exchanged about them and the tools that are only found in menus not mentioned. are there other instances of tools that do not appear in either the menus or in the toolbox? carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] multilayer tiff
Am 26.11.03, 14:38 +0100 schrieb Sven Neumann: Loading it up with my login failed. Are there other ways to send it? Patches can be send to the gimp-developer mailing-list. So here comes the gzipped code. The old bugs I had visited and all but one checked. I could not see the patch for 97352 TIFF plugin shows progress bar when run non-interactive . So this may remained open. regards Kai-Uwe Behrmann tiff.c.gz Description: tiff.c.gz ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
