Re: [Gimp-developer] some current 2.7 issues
Liam R E Quin wrote: Some nits ,some -- especially (2) and (4) -- bigger than others... (1) The file-export dialogue action button says save, not export (sounds really minor but given the save/export changes, can actually be confusing) (2) The default save location should not be ~/Documents in the case that a file has been imported - it should default to the directory containing the imported image (see the spec) (3) in most programs, save mirrors open, and export mirrors import - if GIMP is erally an XCF editor, open should work for .xcf and .xcf.gz files, and File-import should be there for the rare 99% case when you want e.g. to touch up a photo, and open a non-xcf file. So, please add file-import, with import as the label on the dialogue box. (I think?) (4) images interfere with each other. E.g. open a colour image, and a grayscale one, and watch the colour one turn to grayscale whenever the grayscae one becomes active... and the grey one goes to RGB seemingly at random, too. This and (2) are making it difficult to use GIMP right now. (5) I'm not sure that the image title bar is up to spec at all times with respect to imported/exported. At any rate the little language for setting the image title in preferences probably needs to be expanded to include . the imported image name (separately) folder . the last exported filename (separately) folder . the (imported) / (exported) string (6) There needs to be indication in the title bar (by default) of when an image has been exported/overwritten, not only immediately, but for the rest of the session, e.g. as *warmsock (*exported) warmsock (*exported) warmsock (exported) *warmsock (exported) depending on whether the image has been changed since last saved or exported respectively. Not doing this means that people will lose work. There have already been requests to get rid of the file has not been saved message when you close the image, since in most (no all) workflows it's bogus, as the exported image is the final product. So, people get used to ignoring it even when they have not exported an image, and right now you can't esaily tell if you did or not. (7) Martin is not allowed to wear shoes until (2) and (4) are fixed! (8) The curves and levels dialogues look really snazzy in full-screen mode, composited against the layer. Some problems with this (obviously incomplete) code... . no title on the doc, so may not always be obvious what it is . no way to drag the dock to a different part of the image . once docks are composited they stay that way, even after you leave full-screen mode. But they are not cmposited _before_ you go into full-screen mode, so I think it's a bug. I can file bugzilla entries for these but probably not for a few days. Liam ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer Not sure about script-fu and the others, but the python code will have to be adjusted to handle the new layer groups. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] some current 2.7 issues
Liam R E Quin wrote: (1) File-New, make an RGB image, e.g. 377x233px in size. paint a smiling face in red. (2) File-New, choose Advanced Options and make a grayscale image (I made mine 377x233px). (3) Notice how the smile in the first image is now gray - you can make the first image RGB again by going to it and hitting undo, but as soon as you go back to the 2nd image, the 1st image goes grayscale again. I am still not able to reproduce this, following the step-by-step exactly, except I used a different image size. I cleaned my GIMP2_DIRECTORY first. It is weird that your default size is 377x233 since that is not the default size in git master, you must have mixed the versions somehow. In git master the default size is 610x377 (which is what I used) / Martin -- My GIMP Blog: http://www.chromecode.com/ Reducing UI clutter, docking bars removed ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] some current 2.7 issues
Martin Nordholts wrote: Liam R E Quin wrote: (1) File-New, make an RGB image, e.g. 377x233px in size. paint a smiling face in red. (2) File-New, choose Advanced Options and make a grayscale image (I made mine 377x233px). (3) Notice how the smile in the first image is now gray - you can make the first image RGB again by going to it and hitting undo, but as soon as you go back to the 2nd image, the 1st image goes grayscale again. i can confirm, with default image size 610x377, gtk 2.18.4 glib 2.22.3 and yesterday's git master regards, yahvuu ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] some current 2.7 issues
Martin Nordholts wrote: yahvuu wrote: Martin Nordholts wrote: Liam R E Quin wrote: (1) File-New, make an RGB image, e.g. 377x233px in size. paint a smiling face in red. (2) File-New, choose Advanced Options and make a grayscale image (I made mine 377x233px). (3) Notice how the smile in the first image is now gray - you can make the first image RGB again by going to it and hitting undo, but as soon as you go back to the 2nd image, the 1st image goes grayscale again. i can confirm, with default image size 610x377, gtk 2.18.4 glib 2.22.3 and yesterday's git master Was this with a clean GIMP2_DIRECTORY? If not, could you rename it and see if you can reproduce it with a clean GIMP2_DIRECTORY? doesn't make a difference (i used export GIMP2_DIRECTORY=/some/new/empty/dir) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] some current 2.7 issues
Hi Liam Liam R E Quin wrote: (1) The file-export dialogue action button says save, not export (sounds really minor but given the save/export changes, can actually be confusing) Fixed: commit 5819c3c83a25de4b56360b9d9aa486433c7eaac4 Author: Martin Nordholts mart...@src.gnome.org Date: Sun Dec 6 08:58:27 2009 +0100 app: Have an Export button, not Save, in export dialogs (2) The default save location should not be ~/Documents in the case that a file has been imported - it should default to the directory containing the imported image (see the spec) Hmm this seems to work for me, what is the exact step-by-step? (3) in most programs, save mirrors open, and export mirrors import - if GIMP is erally an XCF editor, open should work for .xcf and .xcf.gz files, and File-import should be there for the rare 99% case when you want e.g. to touch up a photo, and open a non-xcf file. So, please add file-import, with import as the label on the dialogue box. (I think?) There is a benefit of enforcing a separation between save and export, but I don't see a big benefit of enforcing this kind of separation between open and import. Anyway, this is Peter's domain.. (4) images interfere with each other. E.g. open a colour image, and a grayscale one, and watch the colour one turn to grayscale whenever the grayscae one becomes active... and the grey one goes to RGB seemingly at random, too. This and (2) are making it difficult to use GIMP right now. I'm not able to reproduce this either, what is the step-by-step? (8) The curves and levels dialogues look really snazzy in full-screen mode, composited against the layer. Do you mean 'Colors - Curves...' and 'Colors - Levels...' together with 'View - Fullscreen'? Seems to work fine for me, what is the step-by-step? Are we even running the same version (git master)? :) Shoeless regards, Martin -- My GIMP Blog: http://www.chromecode.com/ Reducing UI clutter, docking bars removed ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] some current 2.7 issues
On Sat, 2009-12-05 at 17:34 -0500, Liam R E Quin wrote: (3) in most programs, save mirrors open, and export mirrors import - if GIMP is erally an XCF editor, open should work for .xcf and .xcf.gz files, and File-import should be there for the rare 99% case when you want e.g. to touch up a photo, and open a non-xcf file. So, please add file-import, with import as the label on the dialogue box. (I think?) AFAIK the rule in other apps is to have all formats you also can save to in Open, while Import is either for formats you can not save to, an/or to import something that will become just one part of your document (linked or embedded). -- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] some current 2.7 issues
On Sun, 2009-12-06 at 09:24 +0100, Martin Nordholts wrote: [...] app: Have an Export button, not Save, in export dialogs Thanks for fixing that! (2) The default save location should not be ~/Documents in the case that a file has been imported - it should default to the directory containing the imported image (see the spec) Hmm this seems to work for me, what is the exact step-by-step? Actually this seems to have improved in the last few days! (or more precisely, in the past month, I had not been doin a git pull because of the problem with images interfering with each other) The only time it's biting me now is that if I scan an image, the folder where I started gimp isn't listed as an option. I'll try and keep a more careful note of any other problems - oops! [...] (4) images interfere with each other. E.g. open a colour image, and a grayscale one, and watch the colour one turn to grayscale whenever the grayscae one becomes active... and the grey one goes to RGB seemingly at random, too. This and (2) are making it difficult to use GIMP right now. I'm not able to reproduce this either, what is the step-by-step? (1) File-New, make an RGB image, e.g. 377x233px in size. paint a smiling face in red. (2) File-New, choose Advanced Options and make a grayscale image (I made mine 377x233px). (3) Notice how the smile in the first image is now gray - you can make the first image RGB again by going to it and hitting undo, but as soon as you go back to the 2nd image, the 1st image goes grayscale again. (8) The curves and levels dialogues look really snazzy in full-screen mode, composited against the layer. Do you mean 'Colors - Curves...' and 'Colors - Levels...' together with 'View - Fullscreen'? Seems to work fine for me, what is the step-by-step? Are we even running the same version (git master)? :) Yes, I'm running git master. And I am not in single window mode. It turns out to depend on whether you use Colours-Curves or you click with the colour tool... (1) File-New, make a colour image, e.g. 377x233 px. (2) choose colour-curves and get a new window with the curves dialogue. Press Cancel and it goes away. (3) Go to full screen mode with F11 (say) (4) choose colour-curves again, and get a translucent in-window thing for curves. You can use the middle mouse button to drag the image under the in-window thing to see this. Press ESC to make it go away. (5) Press F11 to leave full screen mode. (6) click the image (with the colour tool still selected) and see the translucent thing. Shoeless regards, Martin :-) Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org www.advogato.org ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] some current 2.7 issues
Some nits ,some -- especially (2) and (4) -- bigger than others... (1) The file-export dialogue action button says save, not export (sounds really minor but given the save/export changes, can actually be confusing) (2) The default save location should not be ~/Documents in the case that a file has been imported - it should default to the directory containing the imported image (see the spec) (3) in most programs, save mirrors open, and export mirrors import - if GIMP is erally an XCF editor, open should work for .xcf and .xcf.gz files, and File-import should be there for the rare 99% case when you want e.g. to touch up a photo, and open a non-xcf file. So, please add file-import, with import as the label on the dialogue box. (I think?) (4) images interfere with each other. E.g. open a colour image, and a grayscale one, and watch the colour one turn to grayscale whenever the grayscae one becomes active... and the grey one goes to RGB seemingly at random, too. This and (2) are making it difficult to use GIMP right now. (5) I'm not sure that the image title bar is up to spec at all times with respect to imported/exported. At any rate the little language for setting the image title in preferences probably needs to be expanded to include . the imported image name (separately) folder . the last exported filename (separately) folder . the (imported) / (exported) string (6) There needs to be indication in the title bar (by default) of when an image has been exported/overwritten, not only immediately, but for the rest of the session, e.g. as *warmsock (*exported) warmsock (*exported) warmsock (exported) *warmsock (exported) depending on whether the image has been changed since last saved or exported respectively. Not doing this means that people will lose work. There have already been requests to get rid of the file has not been saved message when you close the image, since in most (no all) workflows it's bogus, as the exported image is the final product. So, people get used to ignoring it even when they have not exported an image, and right now you can't esaily tell if you did or not. (7) Martin is not allowed to wear shoes until (2) and (4) are fixed! (8) The curves and levels dialogues look really snazzy in full-screen mode, composited against the layer. Some problems with this (obviously incomplete) code... . no title on the doc, so may not always be obvious what it is . no way to drag the dock to a different part of the image . once docks are composited they stay that way, even after you leave full-screen mode. But they are not cmposited _before_ you go into full-screen mode, so I think it's a bug. I can file bugzilla entries for these but probably not for a few days. Liam ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
