[Gimp-developer] License question
Hi everyone, first of all, I'm not sure if this should go here or to -users, but I think it's more appropriate here. I recently came across http://www.ftgimp.com/, which seems to sell an enhanced version of the GIMP (called FT Gimp) for 19.95 to 29.95 USD. Looking around the site, I haven't found any pointers to the fact that it is based on the GIMP (outside of a button at the bottom of the main page that links to http://www.gimp.org/), and neither is there a mention that GIMP is licensed under the GPL. In fact, the site includes a copyright notice that says: FTGimp: Copyright (C) 2002-2003 FlamingText.com. All rights reserved. No reproduction allowed without permission. I can't help but wonder about this whole thing; it smells fishy to me, but I'm not a licensing expert (nor a GIMP expert :)), so I'd be happy to hear your comments. Thanks. -- 2:13PM up 27 days, 14:36, 2 users, load averages: 0.37, 0.27, 0.15 ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] License question
On Tue, Jun 10, 2003 at 02:19:00PM +0200, [EMAIL PROTECTED] wrote: I recently came across http://www.ftgimp.com/, which seems to sell an enhanced version of the GIMP (called FT Gimp) for 19.95 to 29.95 USD. which is fine, of course, except that I don't see any enhancements ;) based on the GIMP (outside of a button at the bottom of the main page that links to http://www.gimp.org/) Well, a button is more than the minimum requirement... FTGimp: Copyright (C) 2002-2003 FlamingText.com. All rights reserved. No reproduction allowed without permission. That might indeed provoke the wrong impression to some people. However, I do interpret this as meaning the site copyright, not the program, which is ok. To find out wether something really is fishy you'd need to look at what you get and wether all the requirements set by the GPL are fulfilled ;) (Personally I'd say it's a rip-off, nothing else ;) -- -==- | ==-- _ | ---==---(_)__ __ __ 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] Slow preview on highres images]
On Wed, Jun 04, 2003 at 05:25:14PM +0200, Feczak Szabolcs wrote: AFAIK, there are no plans to do such an improvement. Considered that we still lack some funding for our developers conference this summer, perhaps we could be persuaded to give it a try. Ok, what do you need to be more persuaded ? pls reply -- _(_)_ (_. o_)F3CZ0 (_,) http://feczo.koli.kando.hu ()__ // // ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Slow preview on highres images]
Hi, Feczak Szabolcs [EMAIL PROTECTED] writes: AFAIK, there are no plans to do such an improvement. Considered that we still lack some funding for our developers conference this summer, perhaps we could be persuaded to give it a try. Ok, what do you need to be more persuaded ? First of all, sorry for not getting back to you earlier. You raised a very difficult question. To understand the difficulties, you need to know that we are very close to a major release and that we are more or less feature-frozen. More or less means that there are a few outstanding features that have long been planned to go in and that people are already working on. These features are supposed to go into the next release. Everything else is postponed for after the release. What you are asking for is a major change. It requires to introduce a new framework to the core that provides scaled-down previews of all drawables. A lot of operations like for example transformations would benefit from such a framework so we definitely want to introduce it at some point. However I feel that it is too much of a change right now. It would delay the release and we are already behind our time schedule. So basically, what we need to be more persuaded is time. To some extent, time can be bought. You could for example offer money to GIMP developers in order to allow them to work full-time on this feature. That would not necessarily persuade me and Mitch as the maintainers to let the feature go in before the next release. But if someone would come up with a well-designed and working patch, how could we not accept it? We haven't yet decided how we want to proceed after the release. This is something we will discuss at the GIMP Developers Conference this summer. As I've said, we are still looking for sponsors for this conference. Most developers are not able to pay for their travel costs, so we are dependant on funding. Of course we would appreciate if you'd decide to help us with the conference but I can not promise you any features let alone a time schedule for features. Your funding would certainly help GIMP development and we would be happy to mention your company's name as a conference sponsor. Your money would certainly help to improve GIMP but I cannot sell any features to you. Especially not at this point of development. I'd be happy if you nevertheless decided to help us with the conference. We already got some fundings from the FSF but we are still lacking about 5000 EUR. That's not much for a larger company and any donations would help. So if you, or anyone else reading this, is willing and able to help, please let us know. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Slow preview on highres images]
On Tue, Jun 10, 2003 at 05:02:22PM +0200, Sven Neumann wrote: First of all, sorry for not getting back to you earlier. ok, thanks better later than never :) I can better understand your situation by now. Im just wondering how could this avoid your attention during the core code development, since this is a fundamental flaw I think. In my imagination it looks like during testing you have choosen images only with small amount of pixels or something like that, or maybe in the beginning the aim was to satisfy only a lower quality deamand for web graphics, not the professional digital imaging (which obiviously was not so popular in the early stage of gimp development). Im just guessing it is not against anyone, Im just curious .. you might tell me the real history if gimp from that aspect. That's not much for a larger company and any donations would help. So if you, or anyone else reading this, is willing and able to help, please let us know. Well, saidly we are not out of the larger companies. Our organization is really small, it is a photo shop indeed. So I guess we stuck to Photoshop and windows till the case solved. We will kindly support you from our profit if we can benefit from your software, but at this point this is not much, maybe a 100Eu or sg. like that. -- _(_)_ (_. o_)F3CZ0 (_,) http://feczo.koli.kando.hu ()__ // // ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] C plugin writer wannabe(more like newbie) has questions...
Hi all, I am now moving from script-fu/perl-fu scripting and entering the world of C plugin writing for GIMP. Only reason I am doing this is because I need to get information about pixels on the drawable(quite a significant number of pixels) I have read the good tutorial Essentials Of a Plug-in by Kevin Turner, and I have a few things that I just want to ask about plug-in writing in general. a) Where do I find plug-ins with the C code instead of the executable ones in the plugin directory? I like learning by reading other source codes and could anyone tell me which one is well commented so that I get what's going on? b) I have read the online documentation on libgimp http://gimp-plug-ins.sourceforge.net/doc/libgimp/html/ Unfortunately, I find it hard to use because not everything in there is documented, as in I have no idea what some of the functions do(although most function names are pretty well defined) and I have no idea what sort of parameters it wants me to pass in. Can anyone tell me if there is a source of help that will explain the functions in detail? c) Basically, I just want to get information in a pixel? Thing is, if i use this function: voidgimp_pixel_rgn_get_pixel(GimpPixelRgn *pr, guchar *buf, gint x, gint y); Only thing I don't understand is what is the datatype guchar, and how much memory do we allocate to the buf pointer? And in this buf pointer, what information is actually being returned? Basically, I just need to know what color the pixel is. Will that information be returned? There you go..newbie with tons of questions. I hope you understood what I was trying to ask because I have 0 experience in writing gimp plugins. Thanks all in advance! Kenny ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] C plugin writer wannabe(more like newbie) hasquestions...
Hi, Kenny Law [EMAIL PROTECTED] writes: a) Where do I find plug-ins with the C code instead of the executable ones in the plugin directory? I like learning by reading other source codes. There are more than hundred plug-ins included in the GIMP tarball. I suggest you start looking there. b) I have read the online documentation on libgimp http://gimp-plug-ins.sourceforge.net/doc/libgimp/html/ This documentation, or actually a more uptodate version of it, is also included in the source tarball. Have a look at the devel-docs directory. Unfortunately, I find it hard to use because not everything in there is documented, as in I have no idea what some of the functions do (although most function names are pretty well defined) and I have no idea what sort of parameters it wants me to pass in. If you installed the GIMP API reference next to the GLib and GTK+ API references, you could click on most data types and get to the relevant documentation that way. Here's an online version of the GIMP-1.3 API reference which is properly cross-linked: http://developer.gimp.org/api/1.3/ However you will need some more docs than the API reference can give you. Simon Budig wrote an excellent paper for last year's Guadec: http://www.home.unix-ag.org/simon/gimp/guadec2002/gimp-plugin/html/ Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Slow preview on highres images]
Hi, Le mar 10/06/2003 à 17:02, Sven Neumann a écrit : I'd be happy if you nevertheless decided to help us with the conference. We already got some fundings from the FSF but we are still lacking about 5000 EUR. That's not much for a larger company and any donations would help. So if you, or anyone else reading this, is willing and able to help, please let us know. Why can't you launch a « Gimp Fund » through paypal, like the Blender foundation did ? I think that the Gimp has much more visibility than Blender did, and would have no problems raising money. Actually, it may even help to boost the development. Thanks, -- Dam ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] ANNOUNCE: GIMP 1.3.15
Hi GIMPers, there's a new development snapshot of The GIMP for you to play with. Grab a copy from ftp://ftp.gimp.org/pub/gimp/v1.3/v1.3.15/ or from one of the mirrors listed at http://gimp.org/download.html. I suggest you also upgrade to Pango 1.2.3 and GTK+ 2.2.2 which have just been released since there are some important bug-fixes in these releases which also affect The GIMP. Here's a short summary of changes. For a more complete coverage, please consult the ChangeLog: Overview of Changes in GIMP 1.3.15 == - Removed color correction tools from toolbox again [Sven] - Factored out color-picking code into a GimpColorTool class [Sven] - Updates to the W32 build system [Tor Lillqvist, Hans Breuer] - Removed the need for special casing for some platforms [Yosh, Sven] - Added item rotation (90, 180, 270 degrees) [Sven, Mitch] - Load old paths as new vector objects [Mitch] - Apply transformations to linked items [Mitch] - Generalized item transformations [Mitch] - Improved session managment [Mitch] - Speed up fonts query [Yosh] - Backed out pluggable tools [Sven] - Lots of bug fixes Other contributors: Branko Collin, Pedro Gimeno, Dave Neary, Raphael Quinet, Maurits Rijk, Adam D. Moss, Jakub Steiner Happy GIMPing ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
