Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
On 26 Feb, Kelly Lynn Martin wrote: > It will also force us to develop tools for the separate compilation of > plugins and develop a plugin interface that is versionable The first one is definitely a need but "a plugin interface that is versionable"? We do have versioned libraries ensuring that plugins always use the right libgimp version and a wireprotocol which checks whether a plugin is using the same protocol version as the GIMP. -- Servus, Daniel
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
Oops, just had to move the documentation, the correct link is now: http://sven.gimp.org/1.1/docs/libgimp/ Salut, Sven
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
Hi, > On Sat, Feb 26, 2000 at 02:37:02AM +0100, Sven Neumann wrote: > > (1) Add an online version of the Libgimp documentation to your website. > > You might even want to help us to improve it further. The whole > > purpose of generating this documents was to help plugin developers. > > Hmm. It appears as if I am going to have to spend a bit more time > studying up on gtkdoc before it will be willing to build the devel-docs > for me, but I will look in to this. Please report back if you have any unsolveable problems. For now you may want to link to http://sven.gimp.org/1.1/libgimp/ but note that the info is only updated manually when I find the time to do so. Salut, Sven
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
On Sat, Feb 26, 2000 at 02:37:02AM +0100, Sven Neumann wrote: > (1) Add an online version of the Libgimp documentation to your website. > You might even want to help us to improve it further. The whole > purpose of generating this documents was to help plugin developers. Hmm. It appears as if I am going to have to spend a bit more time studying up on gtkdoc before it will be willing to build the devel-docs for me, but I will look in to this. -- Kevin Turner <[EMAIL PROTECTED]> | OpenPGP encryption welcome here
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
On Fri, 25 Feb 2000 19:00:28 -0500, Robert L Krawitz <[EMAIL PROTECTED]> said: >I think it's great that plugin development is "fragmenting" in this >fashion. It isn't going to weaken the Gimp; it's going to increase >the pool of people who want to write plugins for it, which is all to >the good. It will also force us to develop tools for the separate compilation of plugins and develop a plugin interface that is versionable Kelly
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
From: Sven Neumann <[EMAIL PROTECTED]> Date: Sat, 26 Feb 2000 02:37:02 +0100 just do make my position clear: I was not critizing your decision. My feeling was just that we could have built a similar framework on available resources with substantial interest and a little effort. As long as it helps Gimp development I'm all for it. (That's why I pointed Dirk to your project). Possibly, but is it worth the effort? VA Linux Systems is backing SourceForge with some fairly serious hardware (see https://sourceforge.net/docs/site/hardware.php) and staffing resources; they have 5 people managing the site. They have a dozen machines that I'd guesstimate are about $50K-$100K of hardware (RAID boxes and fast tape drives aren't cheap), and they've put a lot of programming effort behind it. They're basically running a small scale data center operation. I have yet to see any sign of downtime on the entire system. I'd argue if anything that it would be worthwhile for the Gimp to move *its* operation to SourceForge, just to save on the system administration and backup headaches. It's always possible to mirror the CVS repository and other important stuff elsewhere (I'm taking a snapshot of gimp-print's repository every night as insurance myself). -- Robert Krawitz <[EMAIL PROTECTED]> http://www.tiac.net/users/rlk/ Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for The Gimp Print -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
Hi, just do make my position clear: I was not critizing your decision. My feeling was just that we could have built a similar framework on available resources with substantial interest and a little effort. As long as it helps Gimp development I'm all for it. (That's why I pointed Dirk to your project). BTW: I think you should try to interact more with the core. This is in interest of both parties. Here are a few suggestions, that IMO will help to improve the situation for all of us: (1) Add an online version of the Libgimp documentation to your website. You might even want to help us to improve it further. The whole purpose of generating this documents was to help plugin developers. (2) Try to help us improving the documentation shipped with Gimp. For example I found an interesting document about plug-in i18n on your site . This is something we should add least mention in our documentation as a link. I plan to move some of the files in the docs directory into devel-docs and I'd love to get some updates / corrections / links from ypur part as this documentation is primary targeted to plugin developers. Salut, Sven PS: About that document at http://gimp-plug-ins.sourceforge.net/doc/i18n.html: I stronly encouryge you to ask plugin developers to call their textdomain gimp- instead of only . I even thought about forcing that naming convention when implementing "The i18n solution", but I guess it should work if we nicely ask people to use it. And you will want to add an explanation of the proper usage of gimp_plugin_add_domain() as soon as we have worked out the remaining issues.
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
Date: Fri, 25 Feb 2000 15:42:49 -0800 From: Kevin Turner <[EMAIL PROTECTED]> On Fri, Feb 25, 2000 at 05:06:43PM +0100, Sven Neumann wrote: > There is a gimp-plugins project at SourceForge which you might be > interested in, since they can provide you with web, ftp and cvs resources: > >http://gimp-plug-ins.sourceforge.net/ > > PS: I don't know why people decided to use the SourceForge resources > since we have all we need at gimp.org and cvs.gnome.org. But it > turned out that people prefer SourceForge. Seems to be hip ATM. Basically because gimp.org resources were not percieved as readily available, at least in comparison to SourceForge screaming "here, take it, please!" We wanted to be able to pass out CVS and web write access to an as yet undetermined number of people without disturbing the core. Since plug-in development has a different centre that core development, it did not seem unreasonable to base the community at a seperate site. Which I'd like to second. Putting the print plugin on Sourceforge means that our team can decide who gets what access; we don't need to get anyone else's permission to give someone write access to our repository. It also supports mailing lists (fully automated), a bug tracking system, message boards, and a whole lot else. What's more, having a lot of projects on there means that there's a lot of interplay. For example, last night I noticed an interesting project (someone's working on supporting Lexmark printers) and I invited him to join our project. I think it's great that plugin development is "fragmenting" in this fashion. It isn't going to weaken the Gimp; it's going to increase the pool of people who want to write plugins for it, which is all to the good. -- Robert Krawitz <[EMAIL PROTECTED]> http://www.tiac.net/users/rlk/ Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for The Gimp Print -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton
