Re: [Gimp-developer] no image open spec...
On Fri, 2008-02-08 at 19:12 +0100, peter sikking wrote: > Tobias Jakobs wrote: > > > I thought about it and I created this mock-up: > > http://hagemaenner.de/stuff/gimp/PlanB/6.png [...] > I have been moving in the same direction in the last days. > > If the main function of the window 'body' under the menu bar > is to have a nice size drag + drop area, let's on its look + feel > for that. As for the size of this window: just wide enough to fit > the menubar for the running localisation,height of the window, > 1/4 or 1/3rd of the width, some nice proportion. Perhaps it could contain an icon for each active image, so that left-clicking on the image would bring the image window and any associated pallettes or whatever to the front, and right-clicking (or the reverse for left-handed people) would give an image-specifc context menu as one would expect, either with "close, save a copy, save as, revert, properties" or the same menu as clicking on the image. If you make the area useful (drop an image...) and then when the image is dropped, that area and message are replaced by the image, it's no longer clear how to open a second image. The obvious way would be to drop it in the same place, but that wouldn't work, it would add a layer. So then you need a visible drop target... One solution would be that opening an image makes also a new empty image window to drop things in but that's absurd. Another (better I think) would be to have a drop target pallette area/window, that could be docked. None of this really helps the "window with no image for beginners" question though. 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
Re: [Gimp-developer] no image open spec...
>> I thought about it and I created this mock-up: >> http://hagemaenner.de/stuff/gimp/PlanB/6.png >> >> In the center of the area I've added a simpel text "Drop Images >> here to >> open them." (Perhaps a native speaker should change the wording.) >> I really like this image. I think what could make it really good is adding to it a toolbar with "new" and "open" buttons at its top. I understand Peter when he says having the "new image" and "open document" displayed prominently can get annoying, however having it as icons in a toolbar like in most applications do would be a good compromise in my opinion ___ 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 spec...
Tobias Jakobs wrote: > I thought about it and I created this mock-up: > http://hagemaenner.de/stuff/gimp/PlanB/6.png > > In the center of the area I've added a simpel text "Drop Images > here to > open them." (Perhaps a native speaker should change the wording.) I have been moving in the same direction in the last days. If the main function of the window 'body' under the menu bar is to have a nice size drag + drop area, let's on its look + feel for that. As for the size of this window: just wide enough to fit the menubar for the running localisation,height of the window, 1/4 or 1/3rd of the width, some nice proportion. Forget about the slider, please. It belonged to another strategy, another time, another place... --ps founder + principal interaction architect man + machine interface works http://mmiworks.net/blog : on interaction architecture ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP on gtk-macosx, anyone?
Hi everyone, I'm not sure I understand fully your packaging mechanism, but would it be > possible to have script-fu and the launcher as faceless background > apps? I > know it's possible to disable the dock presence (for a given app) -- but I > am not sure if it's really needed a UI for the extra 2 processes in your > new > scheme. If I understand the intentions of the project (make GIMP a > seamless > first-class citizen on OS X), in theory the user shouldn't need to worry > about those technical details: so I'm thinking, maybe any config-related > UI > elements could be removed or moved somewhere else and have the 2 > additional > processes as background daemons. Actually the goal at the moment is to get rid of the launcher, only this way can GIMP be a true mac app (this includes the ability to open documents by dropping them on its icon, all general interaction from the dock, using application switchers, etc. none of these native features could be performed properly with a hidden launcher. That's why I'm working towards removing the launcher altoghether and itneraction directly with the gimp executable. Making script-fu a faceless background process is probably possible but I still need to experiment. Also, keep in mind removinf the launcher IS possible, I've already done it, I just need to refine my instructions. I am thinking about creating some sort of GTK binary distribution for mac (anyway if I don't someone else will do. such a distribution would ease the process A LOT). > > You would also have to do this (or something like this) for all > plug-ins. Script-Fu just happens to run as an extension. But there might > be other GIMP extensions and since all plug-ins are separate processes, > they would probably all show up in the dock when they are being run. Ok. Well I will first try to figure out the appropraite code to do that (I have sample code I think could work but I still have to test it). When I figure that out, we can think about polishing things. Also, just removing the launcher would already improve the interaction a lot so I may start with that instead. > > Has this been reported upstream? It has, and it might even be fixed, I don't know, I need to update my GTK version and test again (I'm doing it at the moment but it takes a rather long time to compile everything on my computer) ___ 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 spec...
Hi Tobias, I like the simple, functional design of this. Do you know, has what the toolbox would become, already been resolved? I notice this does not seem to concern people presently. On Feb 8, 2008 9:01 AM, Tobias Jakobs <[EMAIL PROTECTED]> wrote: > > Am Dienstag, den 05.02.2008, 11:26 +0100 schrieb peter sikking: > > GIMPsters, > > > > Let me state that I wrote my first email in this thread because (yes) > > I am struggling what to put there. It is easy for me to make the > > list of gimmicks that not should go in there. Every on of those > > sucks so much... But what is left? The window needs to be there, > > already outlined above the functions it does. So instead of just > > plain bgcolor, let's do something a bit more stylish, without > > drawing any attention to it. > > > I thought about it and I created this mock-up: > http://hagemaenner.de/stuff/gimp/PlanB/6.png > > The idea is to use a simple radial gradient from the upper left corner > to the lower right. (This should be switched for RTL languages.) > > The gradient colours are calculated from the "selected forecolour" from > the GTK theme. This way it fits nicely into every desktop environment. > > In the center of the area I've added a simpel text "Drop Images here to > open them." (Perhaps a native speaker should change the wording.) > This is NOT the "Tip of the Day" and should NOT change. > The colour of the text is the brightest colour from the gradient. This > will give us a nice contrast and it will fit to the theme colours. > > > >> the slider is a dead serious key in the whole experience. to > > >> seamlessly > > >> track the mood of users over a a working day (or a hobby night) is > > >> worth gold in user interaction. > > > > > > Would you please care to explain this? > > > > I am going to let the slider rest until the window content is sorted > > out. > > Then redesign the whole package so it all fits together... > > > I don't get you slider idea. But if you think about a small timewaster > what do you think about adding a colour slider to my mock-up? > > Regards, > Tobias > > > ___ > Gimp-developer mailing list > Gimp-developer@lists.XCF.Berkeley.EDU > https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer > ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP on gtk-macosx, anyone?
On Fri, 2008-02-08 at 09:14 +0100, Sven Neumann wrote: > Hi, > > On Thu, 2008-02-07 at 12:18 -0500, M Gagnon wrote: > > > * There's a few major showstopper bugs, and we're waiting on GTK folks > > to fix them. The most important one is that keyboard shortcuts > > currently do not care about the open window and can catch keys > > randomly - for instance if you try to type a S in the text editor > > tool, the S key down event will be stolen by the toolbox window, and > > used to select whatever tool uses shortcut S. > > Has this been reported upstream? It is exactly the same issue we fixed by having a custom key event handler on docks (gimp_dock_key_press_event), and the proposed fix seems inspired by this solution. Basically you would have to call a function from your app to get the menu events handled at the right time. The upstream bug is here: http://bugzilla.gnome.org/show_bug.cgi?id=473822 The complete GDK patch is here: http://ardour.org/files/patches/gtk.patch Gimp would simply call gdk_quartz_possibly_forward() (badly named) from the right spot in the dock key event handler. ciao, --mitch ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP on gtk-macosx, anyone?
Hi, On Thu, 2008-02-07 at 12:18 -0500, M Gagnon wrote: > * There's a few major showstopper bugs, and we're waiting on GTK folks > to fix them. The most important one is that keyboard shortcuts > currently do not care about the open window and can catch keys > randomly - for instance if you try to type a S in the text editor > tool, the S key down event will be stolen by the toolbox window, and > used to select whatever tool uses shortcut S. Has this been reported upstream? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP on gtk-macosx, anyone?
Hi, On Thu, 2008-02-07 at 15:17 -0800, Ettore Pasquini wrote: > I'm not sure I understand fully your packaging mechanism, but would it be > possible to have script-fu and the launcher as faceless background apps? You would also have to do this (or something like this) for all plug-ins. Script-Fu just happens to run as an extension. But there might be other GIMP extensions and since all plug-ins are separate processes, they would probably all show up in the dock when they are being run. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] fonts in gimp
Hi, On Thu, 2008-02-07 at 18:56 -0500, Andrei Simion wrote: > This is what we use and it worked fine with Gimp 1.2. version, but I've > been told the font description has changed for 2.x versions. What you used is certainly not the format that GIMP 1.2 expected. The format for GIMP 1.2 was XLFD as described in http://ftp.xfree86.org/pub/XFree86/4.5.0/doc/xlfd.txt Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
