Re: [Gimp-developer] no-image-open redux
I'm afraid that this "no image window" sounds more and more like the photoshop-esque gray background window that everybody have been asking for all these years. The idea of keeping it, even when there is an image open, seems to back that up. It will end up as a maximizable window and all the other windows will have a always-on-top hint. And we'll have WiW. :-p Until I don't see the proposal of the UI team, I won't understand why an introductory window with common tasks (new, open, open recent) is a bad idea. Gez. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] script-fu menu
Sven Neumann wrote: > On Tue, 2008-03-04 at 17:16 -0500, Kevin Cozens wrote: >> This feature would be of enough general use that it should be available to >> all >> scripting systems. > > I don't see this as a feature that the GIMP core would implement. It is > up to the scripting language(s) to do that. I don't know if you would consider a library as being part of the GIMP core. This feature could be implemented in a new GIMP library or as part of libgimpui. An existing GSoC 2008 project idea is to provide a unified UI for scripting. If a unified UI is considered a desirable feature, why would you say that each language binding should provide its own method of registering/providing preview images? > Just add a function like script-fu-example-image-register that > associates an image filename with the procedure. The images could live > in the scripts folder, right next to the script. The one question I forgot to ask is how would a person get to see these preview images? Using an image preview browser? A "show preview" button (or menu item) in the scripts UI window? Some other mechanism (yet to be decided)? -- Cheers! Kevin. http://www.ve3syb.ca/ |"What are we going to do today, Borg?" Owner of Elecraft K2 #2172 |"Same thing we always do, Pinkutus: | Try to assimilate the world!" #include | -Pinkutus & the Borg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
Hi, I should probably add that of course the toolbox and probably another dock window will also be open. So there is really no point in making this a small window. It should be large enough to serve as the parent window for all palette windows that the user configured for GIMP. A lot of users will probably even maximize this window. And we should add code that remembers this state and open it maximized the next time GIMP is started. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
Hi, On Sat, 2008-03-08 at 09:49 -0800, Bill Skaggs wrote: > After discussing these things with Enselic on IRC, I've come to > realize that the most basic question is what we expect the user > to do with this window. If we expect the user to mainly keep it > minimized, and only bring it up when intending to open an image, > then there is no problem if it is large and full of empty space. (It > still shouldn't be *too* large if it is going to be a drop target, or > it will tend to cover up the drag source.) If, however, we expect > the user to keep it open in a corner of the screen, then it needs > to be relatively small, and visually attractive. I have been designing > with the small-attractive goal in mind, but maybe that is the wrong > approach. Why should a user keep the no-image window open? This window will only ever be there, in this mode, for a few seconds. It is shown when GIMP is started without specifying images on the command-line. The user will then either create a new image or open an existing one. And it will be there when the user closes the last image. At that point she is either done using GIMP and exits the application or she starts to work on another image. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
On Saturday 08 March 2008 19:49:48 Bill Skaggs wrote: > After discussing these things with Enselic on IRC, I've come to > realize that the most basic question is what we expect the user > to do with this window. My two cents: nether wasking space on screen or behind other windows cluttering the taskbar is a good option... How about making it non-taskbar and accessible through an icon in notification tray where it comes up as notice window and stays above all other windows for easy D&D until dismissed either by [x] click or click on the icon? It would have an added benefit of keeping gimp running all the time to quickly open an image without desktop clutter... That way the window would be very useful. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
On Sat, Mar 8, 2008 at 5:21 AM, Sven Neumann <[EMAIL PROTECTED]> wrote: > Resorting the menus is something that we should avoid to do > again. And I don't think that the current menu is too wide. Just > make the image window wider. A typical application window > nowadays takes 2/3 of the screen width or even all of the screen. > I don't see why the GIMP image window should not be allowed to > do that as well. After discussing these things with Enselic on IRC, I've come to realize that the most basic question is what we expect the user to do with this window. If we expect the user to mainly keep it minimized, and only bring it up when intending to open an image, then there is no problem if it is large and full of empty space. (It still shouldn't be *too* large if it is going to be a drop target, or it will tend to cover up the drag source.) If, however, we expect the user to keep it open in a corner of the screen, then it needs to be relatively small, and visually attractive. I have been designing with the small-attractive goal in mind, but maybe that is the wrong approach. Of course we must not force one behavior or the other on the user, but the way the window is designed will inevitably favor one of the two ways of using it. -- Bill ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
On Sat, Mar 8, 2008 at 5:06 AM, Martin Nordholts <[EMAIL PROTECTED]> wrote: > > But what you currently have seems to be very far from the spec [1]. > Is this intentional or have you just not been able to steer your > current work into the direction of the spec? Just asking since it > would be sad if someone worked hard on something that isn't going > to be used anyway :/ The spec is currently underspecified. It says a great deal about what should *not* go into the window, but almost nothing about what *should*, with the exception of an idea that Peter has dropped (a slider). Well, _something_ has to go there. I have been trying to incorporate the results of the discussion that followed the specification. As usual, the results were somewhat ambiguous, so I have had to make decisions which might be wrong. Mostly I thought that it was necessary to show something concrete, to keep the topic from fading. Second, please don't worry too much about how hard I am working. I have tried a hundred variations by now, and am happy to try a hundred more. And even if none of this ends up being used, I have learned a tremendous amount in the process. -- Bill ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
Hi, On Fri, 2008-03-07 at 13:37 -0800, Bill Skaggs wrote: > 1) The toolbar shows most of the things a user might want to > do with no image open, but not quite all. "Aquire", or "Open as > layers", could be added, or even "Create", which would access > the menu for creating buttons, logos etc. "About" could, and > probably should, be removed. I don't think such a toolbar should be added. If at all then it should be added to the image window all the time. And we would have to consider carefully what we want to show there. Only adding it for the no-image case is confusing and inconsistent. > 2) I felt like I had to shorten the main menu, because it made the > window too wide. I did this by shifting the categories I use least > into submenus -- "View" into "Image", and "Tools", "Dialogs", and > "Xtns" into a new "Gimp" category. Resorting the menus is something that we should avoid to do again. And I don't think that the current menu is too wide. Just make the image window wider. A typical application window nowadays takes 2/3 of the screen width or even all of the screen. I don't see why the GIMP image window should not be allowed to do that as well. Anyway, this is something that the UI team should specify. I hope that we will get some more input from Peter on this soon. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
Hi, On Fri, 2008-03-07 at 20:48 -0500, Rick Yorgason wrote: > I understand that people want to find a way to show tips in an > unobtrusive way, but maybe we can take a hint (no pun intended) from > video games here: the loading screen would be a great place for tips, > since the user has nothing to do but twiddle their thumbs during that > time anyway. Starting GIMP takes about three to five seconds. I don't think that gives anyone enough time to twiddle thumbs or to read tips. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
Bill Skaggs wrote: > To keep the ball rolling, I thought it might be useful to show a > copy of my current experimental version of a no-image-open > window. Hello First of all, it's great that someone is working on and looking into how to best fix most aching UI problems GIMP has. But what you currently have seems to be very far from the spec [1]. Is this intentional or have you just not been able to steer your current work into the direction of the spec? Just asking since it would be sad if someone worked hard on something that isn't going to be used anyway :/ Best regards, Martin Nordholts [1] http://gui.gimp.org/index.php/No_image_open_specification ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no-image-open redux
On Fri, 2008-03-07 at 20:48 -0500, Rick Yorgason wrote: > Has anybody come to a consensus about whether or not the no-image dialog > should persist after an image is opened? This idea is new to me. The whole point is to represent GIMP if there's no image, right? So it's not even a dialog, but the main app window. > Even for expert users, it > might be useful to keep the no-image dialog open as a drop-target for > opening more images, but I can also see how it would annoy some users. I can see how it would annoy pretty much all users. It would very likely end up hidden below the image window ... -- 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
