Re: [Gimp-developer] Tools
On Wed, 2007-03-14 at 20:52 +0100, Michael Natterer wrote: On Wed, 2007-03-14 at 12:47 -0700, Federico Alcantara wrote: Hi I am interested in knowning if Gimp is written in C/C++, and which tools are needed to compile, debug, and test it? What about downloading it and checking yourself? IMHO, refraining from posts like this could greatly improve the atmosphere of this list. It is really up to you to help somebody with answering his question or not to help, but this answer only hurts and helps nothing. ciao, Alpar ciao, --mitch ___ 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] Tools
Alpár Jüttner wrote: On Wed, 2007-03-14 at 20:52 +0100, Michael Natterer wrote: On Wed, 2007-03-14 at 12:47 -0700, Federico Alcantara wrote: Hi I am interested in knowning if Gimp is written in C/C++, and which tools are needed to compile, debug, and test it? What about downloading it and checking yourself? IMHO, refraining from posts like this could greatly improve the atmosphere of this list. Looks like a reasonable answer to me, given the nature of the question. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Tools
Hi I am interested in knowning if Gimp is written in C/C++, and which tools are needed to compile, debug, and test it? Federico Alcantara Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tools
From: Federico Alcantara [EMAIL PROTECTED] I am interested in knowning if Gimp is written in C/C++, and which tools are needed to compile, debug, and test it? You can find a brief overview at http://wiki.gimp.org/gimp/SummerOfCode and a lot more detailed information at http://developer.gimp.org -- Bill __ __ __ __ Sent via the CNPRC Email system at primate.ucdavis.edu ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tools vs. Plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 17 January 2002 17:44, Dave Neary wrote: Please, please, please try to get this right. When discussing GIMP, it is NEVER Gimp. It is NEVER plugin. GIMP has plug-ins. Surely The GIMP (or the GIMP) has plug-ins? :-) Must be THE GIMP then. I mean what other significant GIMPs are there? Lourens (greetings from the Dvorak-peninsula) - -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RxfCvmNyqZHWDvURAsGuAKC5CJnd4G6rfPrSQGqEQ3ZWM7XcjACfV573 pboOM68s7JSFjYntT3ck8D8= =MasW -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Tools vs. Plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, With people talking on this list about plugin distribution and management again recently, I figured it'd be nice to have some document which is worked out a bit more than the ideas that have been thrown up so far. So I've started to make such a preliminary design for a plugin distribution system, however, I'm a bit stuck due to lack of knowledge on Gimp internals. So, to be somewhate less vague and more specific: What's the difference between a tool and a plugin, on the technical side? Is there any difference at all or is it all in the GUI? Lourens - -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RH12vmNyqZHWDvURAl5zAKC2YvmfUcVt1Zo1TmpcNhMb92LPwwCdHVcB OgsZ6ONwR+PEgTsjjGI7aJ4= =qkDl -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tools vs. Plugins
Hi, Lourens Veen [EMAIL PROTECTED] writes: With people talking on this list about plugin distribution and management again recently, I figured it'd be nice to have some document which is worked out a bit more than the ideas that have been thrown up so far. So I've started to make such a preliminary design for a plugin distribution system, however, I'm a bit stuck due to lack of knowledge on Gimp internals. if I'm informed correctly someone is already working on a plug-in manager but I'd like him to speak up here on himself. So, to be somewhate less vague and more specific: What's the difference between a tool and a plugin, on the technical side? Is there any difference at all or is it all in the GUI? at least with the current design there is tremendous difference: a tool is just a function in the gimp core while a plug-in is a separate process. A tool can do just everything, a plug-in is limited to the libgimp API. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tools vs. Plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 15 January 2002 20:39, Sven Neumann wrote: Hi, snip if I'm informed correctly someone is already working on a plug-in manager but I'd like him to speak up here on himself. If you're reading this, yes, please do so. That'll save me another 10k of text :). So, to be somewhate less vague and more specific: What's the difference between a tool and a plugin, on the technical side? Is there any difference at all or is it all in the GUI? at least with the current design there is tremendous difference: a tool is just a function in the gimp core while a plug-in is a separate process. A tool can do just everything, a plug-in is limited to the libgimp API. Ah, right. So distributing tools through the plug-in manager is nonsense then. Thanks. Lourens PS: no need to CC, I'm on the list - -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RIqOvmNyqZHWDvURAlJzAKCIAzXLYOqXeGUJY8Pe03DcNhJO5gCglN71 Sv5EsYnVVozUt76RWV48JSY= =K9jL -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tools vs. Plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 15 January 2002 21:14, you wrote: Hi, snip I said with the current design. A plug-in manager should definitely be designed to also work for pluggable tools (Bex, how would I spell this correctly?) which is something we definitely want to have in the future. This brings the question back up: how is a plug-in different from a plugable tool? I'd say, a tool allows the user to do image manipulation directly on the image window. It needs a different (not yet existant) API to be able to do this. I agree. For me a tool is something that can be dragged across the image and leave a trail of changes, to put it very inprecisely. Oh, and my guess is plugable. Another nice question is: how is a script different from a plug-in? I tend to call perl scripts scripts while other people call them plug-ins. Anyway, a plug-in manager should be able to handle scripts as well. Let me quote from my unfinished and as-yet unpublished doc: To be able to design a plug-in distribution system, we need to know exactly what a plug-in is first. Currently, a plug-in in The GIMP is a small program, written in C, which is compiled at install time and loaded at GIMP startup. However, there are a number of other objects that are functionally similar, and from an end-user perspective could be regarded as identical. These are Tools, and Perl-fu and Script-fu scripts. I think it's silly that these technical differences are even visible in the GUI. I'm all for just sorting things based on function, not on their technical background. An exception would be tools, but then this too should be independent of technical implementation. I think it's strange that Colors-Curves is a tool, since it doesn't fit the above definition. It is, for technical reasons, but the end-user shouldn't need to concern herself with that. Lourens - -- GPG public key: http://home.student.utwente.nl/l.e.veen/lourens.key -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RJEbvmNyqZHWDvURAuNvAJ9GzNLEaH5j2FzZahr3Wjv1trMPZgCdHnqL x6dajEIsnOzXroZspth4Xuk= =6Yvo -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Tools vs. Plugins
On 15 Jan 2002, Sven Neumann wrote: if I'm informed correctly someone is already working on a plug-in manager but I'd like him to speak up here on himself. I said I would be interested working on something like that but I probably don't have the skills or knowledge of GIMP to do it all myself. Chris -- rm -rf /bin/laden ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
