[Gimp-developer] Re: [Gegl-developer] The GUADEC meeting
On Tuesday 07 June 2005 07:26, Sven Neumann wrote: Leon Brooks [EMAIL PROTECTED] writes: I'd like to see menu themes so that a frustrated refugee from other graphics programs (not just PS) can load a theme and have menus arranged like their other system, but have not yet looked to see how hard that is. Rearranging the core menus is a matter of editing a couple of XML files. Excellent! I have RDP access to a W2k3 server with much software available, so I'll see about cobbling up some menus compatible with what I have to hand. I think that rather than disturb the existing GIMP development structure for now, I'll offer the alternate layouts separately at least for a few months and see what eventuates. How hard is it at the moment for a user to select alternate menu layouts on the fly? Cheers; Leon -- http://cyberknights.com.au/ Modern tools; traditional dedication http://plug.linux.org.au/ Member, Perth Linux User Group http://slpwa.asn.au/Member, Linux Professionals WA http://osia.net.au/ Member, Open Source Industry Australia http://linux.org.au/Member, Linux Australia ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] parsing path data from xcf files
Thanks, I'll try and mudle through, unfortunately I am far from fluent in C (my CV includes Java, php, perl and python. Pointers! arh ;) ). So if off the top of their head anyone can give me a bit more info to get me started it would be much appreciated. Is there not documentations that describes the xcf file format? P.s. Well done on a great app, it really kicks ass. Rian On 6/7/05, Sven Neumann [EMAIL PROTECTED] wrote: Hi, Rian Kruger [EMAIL PROTECTED] writes: I have a corrupt gimp file and I wish to parse the path data from the gimp file. Could anyone please tell me how the start and the end of the all the path data is indicated in the file. How does the file indicate when the data from one path ends and the other begins. Use the source, Luke. The code is in the app/xcf folder. Actually, it would be nice if GIMP would not reject your corrupt XCF file but warn and load as much of it as possible. Of course that will not be possible in all cases but it might be worth trying. You could file an enhancement request for this and attach your corrupt XCF file to it. Sven ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re : [Gimp-developer] Screenshot again: capture a window withoutdecoration
Bill, Le 05.06.2005 17:59:04, William Skaggs a écrit : [ ... ] 2005-06-05 Bill Skaggs [EMAIL PROTECTED] * plug-ins/common/screenshot.c: make no decorations option work; problem pointed out by Jean-Luc Coulon on dev list. I must add, however: it is very nice to be told about bugs in this way. It would be even nicer if you could report them using Bugzilla. Ok, I will do so in the future. I used to report bugs to balsa for instance via the list because it is the way they are managed for the CVS. So I did the same. I will now flood bugzilla :-P -- Bill Regards Jean-Luc ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Akanna Menu patch [was Re: [Gimp-developer] The GUADEC meeting]
On Mon, 6 Jun 2005, Sven Neumann wrote: Date: Mon, 06 Jun 2005 00:24:47 +0200 From: Sven Neumann [EMAIL PROTECTED] To: gimp-developer@lists.xcf.berkeley.edu Cc: [EMAIL PROTECTED] Subject: [Gimp-developer] The GUADEC meeting Hi, now that GUADEC is over and everyone's back home, you will probably want to know what has been happening related to GIMP at this year's GUADEC in Stuttgart. Let me try to give a short summary of the GIMP meeting we had on Monday. The menu reorganisation effort was raised. It seems that Akkana's proposal is widely accepted. I wasn't previously aware of this proposal (no mention of it in the wiki and I thought I was on the bug CC list but apparently not) but I eventually found a patch by Akkana which I assume is the one to which you are referring. bug report on menu reorganistion: http://bugzilla.gnome.org/show_bug.cgi?id=116145 Patch by Akkanna to get things started: http://bugzilla.gnome.org/attachment.cgi?id=46852action=view The proposed patch can be improved but it is a good start. If Akkana or someone else has time and motivation to continute to work on this, then the patch can be committed right away. The patch is a substantial improvement, an excellent start by Akkanna. It will be a big improvement to have things grouped by what they do rather than how they do it. I think it is worth mentioning though that Adobe Photoshop didn't even attempt this and instead they copped out and buried their scripts in a seperate Actions dialog, so it may be difficult to keep things managable as people want to add more and more extensions (but I still think the patch is a very good and necessary first step). http://wiki.gimp.org/gimp/GimpMenuReorganization I was thinking fo doing something similar for the python plugins (and making sure to add ellipses where needed). However some of the python plugins duplicate existing functionality so putting two Clothify plugins beside each other would only confuse users. I see Akkanna tackled this by marking the Script-Fu unsharp as Unsharp 2 but if people have idea on how to tackle this duplication of functionality I would be interested to hear it. (I must say when it comes to learning to port scripts to python I found it very helpful to have similar examples written in a different language) plugin written . One possible way to disambiguate similar plugins might be to give them different menu icons but expect you can probably come up with something better than that. Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/ ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Akanna Menu patch [was Re: [Gimp-developer] The GUADEC meeting]
On Tuesday 07 June 2005 09:53, Alan Horkan wrote: I was thinking fo doing something similar for the python plugins (and making sure to add ellipses where needed). However some of the python plugins duplicate existing functionality so putting two Clothify plugins beside each other would only confuse users. I see Akkanna tackled this by marking the Script-Fu unsharp as Unsharp 2 but if people have idea on how to tackle this duplication of functionality I would be interested to hear it. (I must say when it comes to learning to port scripts to python I found it very helpful to have similar examples written in a different language) plugin written . One possible way to disambiguate similar plugins might be to give them different menu icons but expect you can probably come up with something better than that. I always saidthat tehere should be some way to identificate a menu entry. Not only there will be up to four (C, script-fu, Python-fu, tiny-fu) equivalent entries on a row, as you point out - but I think one has the right to know how each menu entry got there. Today it already happens with stuff like 'filter all layers', installed with Gimp-GAP - one can't know where it came from. People suggested that an icon before menu entries would cause to much hassle to the UI - and I agree. I suggested them that right-clicking on a menu item would bring some information about it. (Like: the package where it came from, what language it is written in, and maybe even accept a new shortcut for that item, without having to enable dynamic shortcuts) Regards, JS -- Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/ ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] parsing path data from xcf files
Sven Neumann wrote: Actually, it would be nice if GIMP would not reject your corrupt XCF file but warn and load as much of it as possible. Of course that will not be possible in all cases but it might be worth trying. This is the way GIMP used to work (maybe still does?), though in quite a coarse way (any whole layers and other [meta]data up to the first obvious corruption will get loaded, and a warning issued). I might be talking 0.99-ish ancient history here, but I can't see anyone having intentionally removed such a feature. Regards, --Adam -- Adam D. Moss - [EMAIL PROTECTED] ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Akkana Menu patch [was Re: [Gimp-developer] The GUADEC meeting]
Alan Horkan writes: I was thinking fo doing something similar for the python plugins (and It was my intention to include python-fu as well. I must have missed it because python-fu didn't get built in the tree I was using (it's there now). I need to make an updated patch anyway, to include placeholders, so I'll merge in the python scripts (there don't seem to be very many of them) at the same time. Nobody's commented on any of the other questions I asked in the bug, like whether it would be a good idea to fold the short Glass Effects menu into Light Effects, or moving Enhance up to where it's just under Blur, or whether there's a reasonable place for Show Image Structure since it's now the only item in Utils. I'll go ahead and move Enhance since no one objected; maybe I'll try to come up with some place to stick Show Image Structure. (The bug is http://bugzilla.gnome.org/show_bug.cgi?id=116145 if anyone wants to comment there or read the questions in more detail.) making sure to add ellipses where needed). However some of the python plugins duplicate existing functionality so putting two Clothify plugins beside each other would only confuse users. I see Akkanna tackled this by marking the Script-Fu unsharp as Unsharp 2 but if people have idea on how to tackle this duplication of functionality I would be interested to I'd be interested too. I don't like Unsharp Mask 2 but strings like Unsharp Mask (script-fu) are likely to make the menus too long. Anyone have a better idea? Joao S. O. Bueno Calligaris writes: People suggested that an icon before menu entries would cause to much hassle to the UI - and I agree. Probably. It would be a nice idea but probably isn't worthwhile if it doesn't plug in easily to the current menu code. I do like the idea of being able to find out where a particular menu item comes from. I suggested them that right-clicking on a menu item would bring some information about it. (Like: the package where it came from, what language it is written in, and maybe even accept a new shortcut for that item, without having to enable dynamic shortcuts) The problem with that is that many people still use right-click to get the menus (you have to, if you want tear-offs, so I find I get in the habit of using right-click most of the time instead of left clicking in the menubar), and once I'm in a context menu which I brought up by right-click, I expect right-click to continue to work to invoke submenus and menu items. If that changed and suddenly right-click did something else, and probably dismissed the menu at the same time, it would take quite a while to relearn those habits (and would make gimp's context menus inconsistent with most other apps). I could see using a modifier key, e.g. control-click on a menu item, or even mouse over a menu item and hit some key (f12 for help? ctrl-i for info?) Except of course then you couldn't rebind that key any more as a keyboard shortcut, so that's probably not a good idea either. And neither a modifier-click nor a help key over the menu is very discoverable. Tooltips would be discoverable, but they'd get in the way as you explore the menu system. ...Akkana ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] forwarded message from c't computer magazine
Here we go once again... ---BeginMessage--- [Deutsche Fassung: siehe unten.] Dear Software Author, c't magazine is regulary publishing CD-ROMs with a collection of articles about a single subject. The next one of these c'thema called CDs will cover webdesign. It also features a hand-selected collection of free- and shareware programs as well as fully registered versions of software and utilities for developers of websites. Your Software The Gimp has been pre-selected to be part of this collection. For each program on the CD-ROM there will be a detailed description in the magazine. To put your software on the CD we need your consent as soon as possible, since the deadline is imminent. It can easily be given on our Website at http://www.heise.de/bin/ct/shareware/cdprod.pl?id=5566cdprod=cth0502k=122d500b87a790dcd0de93bd07b2e75dl=e where you will find a form for your data. In order to protect your information we generated the following authentification code for you: 122d500b87a790dcd0de93bd07b2e75d To be able to include your software we need your consent until the 06/09/2005 at the latest. Thanks a lot for your assistance! In case you haven't heard about c't: with about 400.000 sold copies every fortnight we are among Europe's most successful computer magazines. If you have any further questions please contact [EMAIL PROTECTED] Regards, Your c't magazine Sehr geehrte Programmautorin, sehr geehrter Programmautor, das c't magazin plant in seiner Reihe c'thema eine CD-ROM zum Thema Webdesign aufzulegen, die neben einer Artikelsammlung auch Dokumentationen sowie Free- und Shareware-Programme sowie Vollversionen ausgewählter Software für Windows, Mac OS und Linux enthalten soll. Ihr Programm The Gimp ist Teil unserer Vorauswahl. Um Ihre Software mit aufnehmen zu können, benötigen wir so schnell wie möglich Ihre Genehmigung. Die können Sie uns innerhalb weniger Minuten erteilen. Bitte rufen Sie dazu in Ihrem Web-Browser die Seite http://www.heise.de/bin/ct/shareware/cdprod.pl?id=5566cdprod=cth0502k=122d500b87a790dcd0de93bd07b2e75d auf, unter der wir ein Formular für Ihre Daten vorbereitet haben. Alles Weitere wird dort erklärt. Damit das Ganze sicher stattfindet, haben wir Ihnen einen Authentifizierungscode zugeteilt: 122d500b87a790dcd0de93bd07b2e75d Auf Grund des kurz bevorstehenden Redaktionsschlusses möchten wir Sie um eine schnellstmögliche Antwort bitten! Wir können Ihre Software nur dann noch berücksichtigen, wenn Sie bis _spätestens_ 09.06.2005 antworten. Vielen Dank für Ihre Unterstützung. Falls Sie c't noch nicht kennen: Mit ca. 400.000 verkauften Exemplaren (IVW- geprüft) gehören wir zu den erfolgreichsten Computermagazinen Europas. Bei Rückfragen wenden Sie sich bitte an [EMAIL PROTECTED] Vielen Dank für Ihre Unterstützung. Mit freundlichen Grüßen, Ihr c't magazin ---End Message--- ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Akanna Menu patch [was Re: [Gimp-developer] The GUADEC meeting]
On Tue, 7 Jun 2005, Joao S. O. Bueno Calligaris wrote: Date: Tue, 7 Jun 2005 10:39:30 -0300 From: Joao S. O. Bueno Calligaris [EMAIL PROTECTED] To: gimp-developer@lists.xcf.berkeley.edu Subject: Re: Akanna Menu patch [was Re: [Gimp-developer] The GUADEC meeting] written . One possible way to disambiguate similar plugins might be to give them different menu icons but expect you can probably come up with something better than that. I always saidthat tehere should be some way to identificate a menu entry. Not only there will be up to four (C, script-fu, Python-fu, tiny-fu) equivalent entries on a row, as you point out - but I think one has the right to know how each menu entry got there. 'kay, menu icons clearly aren't the best idea. I suggested them that right-clicking on a menu item would bring some information about it. (Like: the package where it came from, what language it is written in, and maybe even accept a new shortcut for that item, without having to enable dynamic shortcuts) I really like the idea of providing information about menu items but not the proposed implementation. The way many other Gnome and GTK give the information applications do is to show a description of a menu item in the status bar. Perhaps the existing short description/summary/blurb in most plugins could potentially be repurposed for this, what do you think? Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/ ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Akkana Menu patch
On Tue, 7 Jun 2005, Akkana Peck wrote: Date: Tue, 7 Jun 2005 10:20:21 -0700 From: Akkana Peck [EMAIL PROTECTED] To: The GNU Image Manipulation Program gimp-developer@lists.xcf.berkeley.edu Subject: Re: Akkana Menu patch [was Re: [Gimp-developer] The GUADEC meeting] Alan Horkan writes: I was thinking fo doing something similar for the python plugins (and It was my intention to include python-fu as well. I must have missed Excellent. If you could add the ellipses (...) too I'd appreciate it. Nobody's commented on any of the other questions I asked in the bug, I'd like to get your changes in as it is so difficult to get everyone to agree and then start to make more changes as we can get some sense of what changes are uncontraversial and people are happy with. like whether it would be a good idea to fold the short Glass Effects menu into Light Effects, go for it (it is probably worth mentioning though that Photoshop puts Lens under Distorts and now it the time to consider incorporating things from Gimpshop) or moving Enhance up to where it's just under Blur, or whether there's a reasonable place for Show Image Structure since it's now the only item in Utils. I thought it had been changed already but abbreviations like Utils and Decor should be avoided. I'll go ahead and move Enhance since no one objected; maybe I'll try to come up with some place to stick Show Image Structure. I'm really not sure, I think that might require a rethink of what categories are needed to accomodate third party plugins and scripts. (I'd be tempted to dumpt it beside Colour Cube analysis because I use both for similar puroposes but I know that isn't a good answer). (The bug is http://bugzilla.gnome.org/show_bug.cgi?id=116145 if anyone wants to comment there or read the questions in more detail.) I'd be interested too. I don't like Unsharp Mask 2 but strings like Unsharp Mask (script-fu) are likely to make the menus too long. Anyone have a better idea? I didn't want to mention it earlier but as you intend making another patch I should mention you used _U as the mnemonic for both Unsharps. A lot of my opinions have been added to the Wiki page but it doesn't lend itself to discussion or otherwise sorting out which ideas people really want, I suppose I should try and catch people on IRC sometime this week and thrash out which other ideas people feel strongly about rather than cluttering the list with too many little details and slowly churning through them one by one. Sincerely Alan Horkan Inkscape http://inkscape.org Abiword http://www.abisource.com ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Akkana Menu patch [was Re: [Gimp-developer] The GUADEC meeting]
On 6/7/05, Akkana Peck [EMAIL PROTECTED] wrote: Nobody's commented on any of the other questions I asked in the bug, like whether it would be a good idea to fold the short Glass Effects menu into Light Effects, Sure, although it might be nice to put a separator between them or moving Enhance up to where it's just under Blur, That makes perfect sense to me. or whether there's a reasonable place for Show Image Structure since it's now the only item in Utils. It seems to me like Show Image Structure belongs under Image/Image/Show Structure Alan Horkan writes: making sure to add ellipses where needed). However some of the python plugins duplicate existing functionality so putting two Clothify plugins beside each other would only confuse users. I see Akkanna tackled this by marking the Script-Fu unsharp as Unsharp 2 but if people have idea on how to tackle this duplication of functionality I would be interested to I'd be interested too. I don't like Unsharp Mask 2 but strings like Unsharp Mask (script-fu) are likely to make the menus too long. Anyone have a better idea? Does the script-fu version do anything the plug-in does not? If it doesn't, there isn't any sense in keeping it around. Rockwalrus ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
