[Gimp-developer] wilber
we are moving things around on wilber. if you have a directory there, perhaps you should back things up. if you have any ideas, perhaps you should pipe up with them. carol -- The sooner you fall behind, the more time you have to catch up. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Latest GimpCVS
On Mon, 2003-06-16 at 06:12, Owen wrote: Removed the plug-in and no other problems Looks like you've installed on top of an old 1.3.x installation. The tool-safe-mode plug-in has recently been removed. Sincerely, ./Brix -- Henrik Brix Andersen [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Setting Up Wilber
On Sat, 14 Jun 2003 14:33:21 -0400, Carol Spears [EMAIL PROTECTED] wrote: Wilber is the name of the computer housed at berkeley. Looks like we will be planning what will become of Wilber tomorrow. I apologize as this is short notice for something that is long overdue, but there you go. What does that mean? There was no discussion and no announcement about that. Before anything is done, can we have a bit more information (and discussion, if possible) about what is going to happen? Sorry about the weekend notice also, probably i followed the WrongMethod like they did to notify poor Arthur Dent of his homes demise in the first of the hitchiker books. Yes, sending an unexpected announcement during the week-end is probably not the best way to communicate with those who are usually not on the 'net at that time. Please send your ideas or needs to this list or any other. But what is planned exactly? It is difficult to send any ideas or needs if there is no information about what is going to happen, why and when... Lets call this 24 hour notice. This is definitely too short, especially since there was no early warning nor discussion on any of the mailing lists (AFAIK). On Mon, 16 Jun 2003 02:41:02 -0400, Carol Spears [EMAIL PROTECTED] wrote: we are moving things around on wilber. if you have a directory there, perhaps you should back things up. I won't be able to back up anything before Wednesday due to lack of time and disk space, so I hope that nothing is going to happen today. Anyway, what is going to happen to Wilber? What is going to happen to the web site? In the last few days, I spent some time updating several pages, including the release notes for 1.2.4 and 1.2.5, the list of mirrors (web and ftp) and the pages describing how to install the GIMP. Do you mean that you want to remove the current web site without any discussion and without any planning? The last discussion on the gimp-web list was in April (except for two messages that I CCed to the list in May, but that was not a discussion). What is happening now, all of a sudden? if you have any ideas, perhaps you should pipe up with them. What does this mean? -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: red-eye-removal (was: Debugging?)
I just had a look at the two plug-ins for fun of it and they doing part of the problem differently, which means that the perl program looks more complicated than necessarry. The scheme plugin uses the plug-in plug-in-colors-channel-mixer to do the actual color mixing, whereas the perl plug-in accesses the pixels itself. Accessing pixels always gets dirty, because of the tile based approach of gimp. Actually, I think that Marc Lehmann's use of PDL for the job is very elegant. But I'm sure that it can be confusing to have to learn another huge sublanguage (which PDL is). So if you want to compare syntax, please compare the same approach in the different languages. I'm curious, does the python plug-in allow you to access the pixels? Regards, Dov On Mon, Jun 16, 2003 at 02:04:52AM -0400, Carol Spears wrote: On 2003-06-15 at 2031.16 -0700, Jeff Trefftzs typed this: Debugging: you might try firing up the script-fu console in the GIMP and testing code snippets there. I've found this to work fairly well. My main problem is getting my head back into lisp space ... Eeek! Jeff, just say no! all three versions of gimp i have used, 1.0 1.2 and 1.3 have a nifty python plug-in complete with browser and console as well. today i read two plug-ins for red-eye removal. the script-fu just looked like gibberish: http://cs.uhh.hawaii.edu/~jeschke/photography/articles/gimp/RedEye2/red-eye.scm this one. this was the saddest thing i ever read. i never want to read something this sad again. please. it is not the authors fault. it is not the fault of the person who ported gimp to it. nor the gtk guy that did it. not the original authors of this scripting language either. i don't know why it is so sad. you have to stop making me try to read this. mercy! http://fmg-www.cs.ucla.edu/fmg-members/geoff/digicam/redeye i would like to read it written in python. it is direct and the modular part is starting to make sense to me. it makes me angry (okay frustrated) not sad. that is better. please someone write this in python quick so we can compare before i forget! carol -- The sooner you fall behind, the more time you have to catch up. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer -- ___ ___ / o \ o \ Dov Grobgeld ( o o ) o | The Weizmann Institute of Science, Israel \ o /o o / Where the tree of wisdom carries oranges | | | | _| |_ _| |_ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Debugging?
On Mon, 16 Jun 2003 02:04:52 -0400, Carol Spears [EMAIL PROTECTED] wrote: today i read two plug-ins for red-eye removal. the script-fu just looked like gibberish: http://cs.uhh.hawaii.edu/~jeschke/photography/articles/gimp/RedEye2/red-eye.scm this one. this was the saddest thing i ever read. i never want to read something this sad again. please. Could you elaborate on what's sad about the above mentioned script? And on why you think people shouldn't write such scripts? Best regards, -- That's the whole problem with science. You're got Adam Sjøgren a bunch of empiricists trying to describe things [EMAIL PROTECTED] of unimaginable wonder. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Debugging?
Hi, Douglas Lewan [EMAIL PROTECTED] writes: Where's the right place to get documentation for GIMP primitives? I've been hunting through the C-code. There is a complete API reference of libgimp installed with the GIMP. Have a look at $prefix/share/doc/gtk-doc/html/libgimp. If you install this reference next to the glib and gtk+ documentation, you get a full cross-referenced API documentation. You should take a look at http://developer.gimp.org/ which has the API docs for GIMP-1.3 online as well a bunch of other interesting links. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: Debugging?
Hi, Carol Spears [EMAIL PROTECTED] writes: today i read two plug-ins for red-eye removal. the script-fu just looked like gibberish: http://cs.uhh.hawaii.edu/~jeschke/photography/articles/gimp/RedEye2/red-eye.scm The URL is broken and you posted the corrected version to gimp-user... A working URL is here: http://cs.uhh.hawaii.edu/~jeschke/photography/articles/gimp/RedEye2/red-eye.scm this one. this was the saddest thing i ever read. i never want to read something this sad again. please. it is not the authors fault. it is not the fault of the person who ported gimp to it. nor the gtk guy that did it. not the original authors of this scripting language either. i don't know why it is so sad. I don't see anything wrong with this script. Actually I'd be happy if all scripts would be as readable as this one. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Setting Up Wilber
Hi Rapha\353l, On 2003-06-16 at 0907.46 +0200, Rapha?l Quinet typed this: On Sat, 14 Jun 2003 14:33:21 -0400, Carol Spears [EMAIL PROTECTED] wrote: Wilber is the name of the computer housed at berkeley. Looks like we will be planning what will become of Wilber tomorrow. I apologize as this is short notice for something that is long overdue, but there you go. What does that mean? There was no discussion and no announcement about that. Before anything is done, can we have a bit more information (and discussion, if possible) about what is going to happen? one thing that i didn't mean was to ruffle any feathers. sorry. i am going to go crazy if the newish site doesn't get moved. There is a whole bunch of disc space (right now) and if we wait and plan and work through what will be done with it, it will never get done. i asked for ideas and such. at least i tried. for instance, maybe someone would like wilber to mirror gentoo. i don't really know. also, i know so little of the possibilities. three things that i am very very interested in is moving the site, the wiki and i would really like to have a gimp organization blog working. i am trying to write a plug-in for gimp that will produce the pages for it. when a good plan gets sent about, you miss better ways maybe. this is the time to mention anything you ever wished for from wilber, i guess. then some discussion about your wishes can happen. there are a few sites that need a contributor.gimp.org, imo. there are probably some i have missed. no one really gave me very much to go on, i am passing along everything i got for this. Sorry about the weekend notice also, probably i followed the WrongMethod like they did to notify poor Arthur Dent of his homes demise in the first of the hitchiker books. Yes, sending an unexpected announcement during the week-end is probably not the best way to communicate with those who are usually not on the 'net at that time. well, as typical, we just got things started. it was very difficult to keep me on task. i did some nominal cleaning to mmmaybe. the gimp-help from gimp-1.2 needs to be put into http://mmmaybe.gimp.org/docs/gimp-docs/ and the developer doc need to be put here: http://mmmaybe.gimp.org/docs/dev-docs/. truthfully, by the time i got them to build, i forgot what i was doing. i might have offended some along the way also. one person cannot remember everything. but this is gimp stuff, there is plenty of time, but the sooner the better. Please send your ideas or needs to this list or any other. But what is planned exactly? It is difficult to send any ideas or needs if there is no information about what is going to happen, why and when... Lets call this 24 hour notice. This is definitely too short, especially since there was no early warning nor discussion on any of the mailing lists (AFAIK). okay, how about 2 weeks notice then. or i can start with a plan on how we plan to divide up wilber carol On Mon, 16 Jun 2003 02:41:02 -0400, Carol Spears [EMAIL PROTECTED] wrote: we are moving things around on wilber. if you have a directory there, perhaps you should back things up. I won't be able to back up anything before Wednesday due to lack of time and disk space, so I hope that nothing is going to happen today. Anyway, what is going to happen to Wilber? What is going to happen to the web site? In the last few days, I spent some time updating several pages, including the release notes for 1.2.4 and 1.2.5, the list of mirrors (web and ftp) and the pages describing how to install the GIMP. Do you mean that you want to remove the current web site without any discussion and without any planning? The last discussion on the gimp-web list was in April (except for two messages that I CCed to the list in May, but that was not a discussion). What is happening now, all of a sudden? if you have any ideas, perhaps you should pipe up with them. What does this mean? -Rapha?l ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer -- The sooner you fall behind, the more time you have to catch up. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: red-eye-removal (was: Debugging?)
On 2003-06-16 at 1043.03 +0300, Dov Grobgeld typed this: I just had a look at the two plug-ins for fun of it and they doing part of the problem differently, which means that the perl program looks more complicated than necessarry. The scheme plugin uses the plug-in plug-in-colors-channel-mixer to do the actual color mixing, whereas the perl plug-in accesses the pixels itself. Accessing pixels always gets dirty, because of the tile based approach of gimp. Actually, I think that Marc Lehmann's use of PDL for the job is very elegant. But I'm sure that it can be confusing to have to learn another huge sublanguage (which PDL is). the perl plug-ins were/are wonderful. i use the heck out of some of them. i ask only not to have to *read* them anymore. something about that language makes this plug-in a sad read. i hope i did not say not to write them. it is the reading part that i cannot endure. i have done everything that is humanly possible to get perl ported to gimp-1.3 and the plug-ins as well. okay, short of begging a scary hero. it is not my fault that it was easier to find people to rewrite them in other script. how about making a splash screen contest so i could show the splash that me and bit and cameron made? i can't read it. and when i can, it can be chilling. So if you want to compare syntax, please compare the same approach in the different languages. I'm curious, does the python plug-in allow you to access the pixels? Dov, i have no idea. i just know that i am able to use the little pieces. it doesn't allow my imagination to run away with me. i can start working on a plug-in (armed with a lot of little pieces located in two directories on my computer), get distracted, go back to it in a few weeks and still be able to figure out what was going on. okay, in truth, i got stuck at the same place with both scripting languages on my cross-stitch plug-in. the point where the xpm gets read in and handled. when i get the chance, i think i can actually handle this with python, eventually and with a lot of help; but. i don't think i will ever be able to sort through it with perl. and i am truly humbled by those who can. good heavens, please don't stop writing perl! carol On Mon, Jun 16, 2003 at 02:04:52AM -0400, Carol Spears wrote: On 2003-06-15 at 2031.16 -0700, Jeff Trefftzs typed this: Debugging: you might try firing up the script-fu console in the GIMP and testing code snippets there. I've found this to work fairly well. My main problem is getting my head back into lisp space ... Eeek! Jeff, just say no! all three versions of gimp i have used, 1.0 1.2 and 1.3 have a nifty python plug-in complete with browser and console as well. today i read two plug-ins for red-eye removal. the script-fu just looked like gibberish: http://cs.uhh.hawaii.edu/~jeschke/photography/articles/gimp/RedEye2/red-eye.scm this one. this was the saddest thing i ever read. i never want to read something this sad again. please. it is not the authors fault. it is not the fault of the person who ported gimp to it. nor the gtk guy that did it. not the original authors of this scripting language either. i don't know why it is so sad. you have to stop making me try to read this. mercy! http://fmg-www.cs.ucla.edu/fmg-members/geoff/digicam/redeye i would like to read it written in python. it is direct and the modular part is starting to make sense to me. it makes me angry (okay frustrated) not sad. that is better. please someone write this in python quick so we can compare before i forget! carol -- The sooner you fall behind, the more time you have to catch up. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer -- ___ ___ / o \ o \ Dov Grobgeld ( o o ) o | The Weizmann Institute of Science, Israel \ o /o o / Where the tree of wisdom carries oranges | | | | _| |_ _| |_ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer -- The sooner you fall behind, the more time you have to catch up. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] there is hope for gimp-perl-1.3 (was:red-eye-removal)
http://fmg-www.cs.ucla.edu/fmg-members/geoff/digicam/redeye Woaw, a PDL plug-in not written by me! Oh my god, I can't believe it happened ;) On Mon, Jun 16, 2003 at 09:54:42AM -0400, Carol Spears [EMAIL PROTECTED] wrote: perl ported to gimp-1.3 and the plug-ins as well. One thing of interest is that I am currently working my way through the Gtk2 module(s) available for perl. Apart from some things I'd really like to have changed and settled to make use of it, this was the major obstacle to a gimp-perl-1.3. Ok, that was a lie, the major obstacle was my lack of time, but now I don't have any other good excuses anymore. It might still take months, but at least I'd like to let you know that I am working on gimp-perl again, even if it's only getting used to the Gtk2 internals. (Gtk2 looks quite good already, btw..) -- -==- | ==-- _ | ---==---(_)__ __ __ 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
[Gimp-developer] Re: there is hope for gimp-perl-1.3
It seems that porting gimp-perl to 1.3 is about trivial, well, at least getting it to compile and run most scripts. The version in CVS compiles and runs, but the scripts using gtk fail (so better not install it or be prepared to skio a few plug-ins when running gimp-1.3). In any case, although the perl-server and yinyang work fine, the 5-minute-port features: - a probably very high dependency on gimpcompat... if not the header file, then the symbols at least have the old names. - it still uses gtk1. porting the Gimp::Fu part itself should be easy, but gimp-perl uses some self-written classes, which is not yet supported the way I want it (sic!). Anyway, it was an experiment, but it shows that the job is doable. On Mon, Jun 16, 2003 at 11:31:16PM +0300, Dov Grobgeld [EMAIL PROTECTED] wrote: Woaw, a PDL plug-in not written by me! Oh my god, I can't believe it Yep, though the author missed the whole point of PDL by looping over x and y. Yeah, shame on me, I only noticed it *after* sending the mail. Ok, that's typical. Instead of the loop the following code would have done the same thing much faster. How about pacthing it and sending it to me for inclusion? *g* Actually, I ported all the non-gui stuff already, Great, I did it, too :() Ok, if you got gtk+ working, please send me what you did ;) straight forward. I then started looking at perl-gtk-xs. What got me stuck is the fact that you created the various widgets by inheritance and perl-gtk-xs still doesn't support inheriting gtk widgets on the perl level. Well, it does support it, sort of strangely-not-at-all-but-actually-it-does. I'd be happy to send you the stuff that I have, but I really don't think that you need it. well.. gimp-1.3 is surprisingly similar to 1.2 (ehy was everybody scaring me off? oh, nobody did.. hmm..). In any case, I only did a rough get-it-compiling again. I hope you got a bit further, so yes, send it to me. -- -==- | ==-- _ | ---==---(_)__ __ __ 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] Re: there is hope for gimp-perl-1.3
Hi, Joao S. O. Bueno [EMAIL PROTECTED] writes: you have to enable the dinamic shortcutting im File-preferences-interface-keyboard shortcuts hmm...what about coming up with it turnned on as the default? If the idea is to make the things im GIMP more visible, why to hide this one? Because it interferes badly with mnemonics, especially if these are used in the menus and we only just started to add them all over the place. This is also the reason why they are disabled by default in all GTK2 apps. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
