Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8
Hi, On Tue, 2003-08-05 at 21:00, Alan Horkan wrote: I was playing around in Paint Shop Pro trying to see what it does well and what caught my interest today was that in seemingly every dialog window you are able to maximise the window unlike standard dialogs where this functionality is usually disabled/greyed out. This is more useful than it sounds, take for example the File Open Dialog. If you maximise the window the widgets reflow and the space with the document list exands to fit the avialable space (and I think the preview box expands too, but I dont have it in front of me right now). If the GIMP was to consider this feature would it require a whole lot of work to make sure the dialogs reflowed properly when maximised? (Keep in mind that users might be using text sizes larger than the defaults so static widget layouts are a really bad idea). In general all GIMP dialogs can be maximized and widgets reflow as you described. What are you talking about? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: Portable XCF
On Friday, August 15, 2003, at 11:53 PM, Carol Spears wrote: [ ... ] I looked up heuristic it said it meant heuristisch! How can this be so? Did you use an English/German dictionary? Next time use Merriam-Webster Online at www.m-w.com I thought when i cp'd something i was totally making a copy of the file and simply giving it a new name. The size never changes, so how could this be true? The contents of the file will not change, just it's representation on the disk. The ls will still report the original file size, but the file will actually use less space on the disk. Once the file is read back into memory, the hole is filled with the correct amount of zeros again. Karl Heinz ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8
On Sat, Aug 16, 2003 at 01:21:05PM +0200, Sven Neumann [EMAIL PROTECTED] wrote: (Keep in mind that users might be using text sizes larger than the defaults so static widget layouts are a really bad idea). In general all GIMP dialogs can be maximized and widgets reflow as you described. What are you talking about? File-New is the exception (it's fixed-size), but that's the only dialog I could come up with that has this problem. Because that's the dialog most often perceived as dialog, maybe he was assuming all others are the same? -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Portable XCF
On Fri, Aug 15, 2003 at 03:41:28PM +0200, Tino Schwarze [EMAIL PROTECTED] wrote: BTW: Would it be possible to get a sparse file by zeroing the unused bits? Then it would be quite space efficient (at least with some file systems). No, there is no way to do that. You will need to copy the file if you want to sparsify parts, or use os-specific interfaces to do that (if they exist, they don't exist under linux). The closest you could get is to garbage collect the file and truncate it at the end. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Portable XCF
Hi, On Sat, 2003-08-16 at 01:20, Alastair Robinson wrote: Some thought needs to be given to how parasites are going to be stored - I'm thinking particularly of embedded ICC profiles here (IIRC the TIFF plugin attaches any encountered profile as a parasite). ICC profiles shouldn't be handled as parasites. Parasites are things the core doesn't understand. It's a way to attach arbitrary data to gimp, images or drawables. As soon as the core starts to use color profiles it will know how to handle them and we don't need to use parasites for them. I already suggested to store parasites in the archive, not embedded in the XML. I've also mentioned that I don't think that we should have folders in the archive since the structural information should be in one place, not in the XML and in some sort of directory tree. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro8
On Sat, 16 Aug 2003, Phil Harper wrote: Date: Sat, 16 Aug 2003 14:15:08 + From: Phil Harper [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8 From: [EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) To: [EMAIL PROTECTED] Subject: Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8 Date: Sat, 16 Aug 2003 14:23:57 +0200 On Sat, Aug 16, 2003 at 01:21:05PM +0200, Sven Neumann [EMAIL PROTECTED] wrote: (Keep in mind that users might be using text sizes larger than the defaults so static widget layouts are a really bad idea). In general all GIMP dialogs can be maximized and widgets reflow as you described. What are you talking about? File-New is the exception (it's fixed-size), but that's the only dialog I could come up with that has this problem. Because that's the dialog most often perceived as dialog, maybe he was assuming all others are the same? hmmm, yes, it does make you wander if he's ever used the GIMP if he's making such suggestions... That was incredibly rude and entirely uncalled for. - Alan /me resisting the urge to say more ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro8
From: Alan Horkan [EMAIL PROTECTED] To: Phil Harper [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8 Date: Sat, 16 Aug 2003 20:29:53 +0100 (BST) MIME-Version: 1.0 Received: from salmon.maths.tcd.ie ([134.226.81.11]) by mc1-f24.law16.hotmail.com with Microsoft On Sat, 16 Aug 2003, Phil Harper wrote: Date: Sat, 16 Aug 2003 14:15:08 + From: Phil Harper [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8 From: [EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) To: [EMAIL PROTECTED] Subject: Re: [Gimp-developer] Allow Maximise in Dialogs, like in Paint ShopPro 8 Date: Sat, 16 Aug 2003 14:23:57 +0200 On Sat, Aug 16, 2003 at 01:21:05PM +0200, Sven Neumann [EMAIL PROTECTED] wrote: (Keep in mind that users might be using text sizes larger than the defaults so static widget layouts are a really bad idea). In general all GIMP dialogs can be maximized and widgets reflow as you described. What are you talking about? File-New is the exception (it's fixed-size), but that's the only dialog I could come up with that has this problem. Because that's the dialog most often perceived as dialog, maybe he was assuming all others are the same? hmmm, yes, it does make you wander if he's ever used the GIMP if he's making such suggestions... That was incredibly rude and entirely uncalled for. - Alan /me resisting the urge to say more i'm terribly sorry, forgot to add the ;) not that this would make the email any less rude i'm sure. Phil. _ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Allow Maximise in Dialogs, like in PaintShopPro 8
Hi, On Sat, 2003-08-16 at 21:29, Alan Horkan wrote: hmmm, yes, it does make you wander if he's ever used the GIMP if he's making such suggestions... That was incredibly rude and entirely uncalled for. Yes, the answer may have been rude but you still did not explain what dialogs you were talking about. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] winsnap plugin build problems
When compiling current cvs on win32, I get: ../../build/win32/compile-resource winsnap.rc winsnap-win32res.o /bin/sh: ../../build/win32/compile-resource: No such file or directory make[1]: *** [winsnap-win32res.o] Error 127 make[1]: Leaving directory `/c/usr/compile/gimp/plug-ins/winsnap' make: *** [all-recursive] Error 1 windres -i winsnap.rc -o winsnap-win32res.o seems to do the same as the missing command - is there any reason what this command isn't called directly by the Makefile? Michael -- The GIMP (deutsch): http://www.gimp.de COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] winsnap plugin build problems
On Sat, 2003-08-16 at 22:51, Michael Schumacher wrote: When compiling current cvs on win32, I get: ../../build/win32/compile-resource winsnap.rc winsnap-win32res.o /bin/sh: ../../build/win32/compile-resource: No such file or directory make[1]: *** [winsnap-win32res.o] Error 127 make[1]: Leaving directory `/c/usr/compile/gimp/plug-ins/winsnap' make: *** [all-recursive] Error 1 windres -i winsnap.rc -o winsnap-win32res.o seems to do the same as the missing command - is there any reason what this command isn't called directly by the Makefile? I don't have much clue about the win32 build but it looks as if you need to cvs update in the virtual build module in the toplevel directory in order to get win32/compile-resource. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Manners.
Guys and gals, Would people please simply think a bit about the tone of their emails before posting? It seems that gimp-developer is increasingly perceived as a hostile, rude, or elitist mailing list, and some small effort on the part of posters would help to alleviate this enormously. Making GIMP's development communication environment more friendly is the key first step to winning more developers. (IMO #gimp has largely lost the battle already, and I'd hate to see the mailing list fall.) Conversely, it would help if people were also slower to take offense. :) It's easy to forget that many if not most of the people here are not native English speakers and might not be able to easily gauge how antagonistic their posts consistantly sound (I've met some of the worse offenders and they're generally not at all antagonistic people :)). Kind regards, --Adam -- Adam D. Moss . ,,^^ [EMAIL PROTECTED] http://www.foxbox.org/ co:3 I am NOT a nut! I am the keeper of the seven universal truths! ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] winsnap plugin build problems
Michael Schumacher writes: When compiling current cvs on win32, I get: ../../build/win32/compile-resource winsnap.rc winsnap-win32res.o /bin/sh: ../../build/win32/compile-resource: No such file or directory ../../build/win32/compile-resource probably *is* there, but what causes that message is that it's a bash script (starts with #!/bin/bash), and you are presumably using MSYS, which doesn't have /bin/bash? (It could well be made into a /bin/sh script instead, it doesn't contain any bashisms AFAIK.) windres -i winsnap.rc -o winsnap-win32res.o seems to do the same as the missing command - is there any reason what this command isn't called directly by the Makefile? Umm, no reason. The compile-resource script's sole purpose is to keep a build number for a DLL, bumping it for each build, and expand the identifier BUILDNUMBER in the .rc file to the current build number. The winsnap.rc doesn't have any meaningful version info in its version resource anyway. (The compile-resource and lt-compile-resource scripts are awful hack, and it says so in the comments in them. I would like to get rid of them, but haven't come up myself with any better way to automatically update build numbers in version resources of DLLs, nor have I received any suggestions...) --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Manners.
Adam D. Moss ([EMAIL PROTECTED]) wrote: Conversely, it would help if people were also slower to take offense. :) It's easy to forget that many if not most of the people here are not native English speakers and might not be able to easily gauge how antagonistic their posts consistantly sound (I've met some of the worse offenders and they're generally not at all antagonistic people :)). As a non-native speaker: *please* tell me (us?) (private mail probably is more appropriate) when the sound of a mail is hostile or antagonistic. Only then we do have a chance to avoid this in the future. Thanks, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
