As far as the Wordpress pages are concerned, a script's page can be located in multiple categories and have multiple tags. But there is also the issue of the database, which as it stands now, a script can only be in one database category. I'm giving the user the option to browse either the script pages or the actual scripts database by category.

I know that is kind of confusing so I'll try to explain. If you take a look at the site on the left, you'll see the page categories listed under "Categories" and you'll see database categories listed under "Gimp Scripts".

If you want to browse the individual script pages (which contain the scripts), you can use the links under Categories.

If you want to browse just the scripts, you can use the links under Gimp Scripts.

It is possible to set the site up so that the same categories appear in both the script's database and script's pages. You'd have two sections with the same set of categories, one would be to browse by pages (which contains the script) and one would be to browse by scripts only.

In hindsight, I suppose that one wouldn't even need to browse just the individual scripts, when they could browse the individual pages (which contains the scripts). I figured that giving users the ability to browse just the scripts database would be a nice option.

You points are well taken and similar issues were considered when Gimp Chat was created. Since the domain names are all lower case, (gimpscripts.com, gimpchat.com), capitalization of GIMP didn't seem that important, even though it's technically the correct way to specify the application's name. I tend to use "GIMP" in thread discussions but I sometimes just use "Gimp" or "gimp".

However, I agree with you and there is no reason not to use the accepted designation for the acronym GIMP on gimpscripts.com (or here, for that matter) so I went ahead and made that change.

As far as plug-ins are concerned, scripts aren't technically plug-ins but that didn't seem to stop the GIMP registry from using that designation in their title. I wasn't planning on limiting gimpscripts.com to Python and Scheme scripts, although those will certainly be the main focus of the site.

I'm also not married to "The GIMP Plug-in Repository", either. I basically just came up with that off the top of my head, for the lack of anything better. I'd definitely be open to alternatives so post 'em if you got 'em.

To new users the distintion between script and plugin is no more clear then Chinese Ideograms and i doubt is very useful in general
GIMP confuse even more as example requiring python script be placed in a plugin folder instead then with the scripts

So why give too much importance to the distintion ?
Users want to know what the..thingy is for then if will work with Windows
or with Mac
or with linux

then they wish and need to know

1 How to install
2 where search in the menu for the script/plugin

And...may be better consider python [b]scripts as python plugins (as Gimp and many authors do)[/b] because this will raise the newbe chances to install them in the right place (the same that for compiled C plugin) at the first attempt

To avoid confusion with C plugins we may simplly explain that python plugin don't need to be compiled

@GnuTux

i try to download the electricity script but the file is missed...i miss that script (i had but without animation option ) could you
fix the dl link ?

I do not think it would be possible for me to find a way to disagree more. The reason that add-ons written in Python are placed in the plug-ins folder is because they are plug-ins -- scripts are placed in the scripts folder because they are scripts. Ignoring the distinction between the two does nothing more than invite the inevitable problems that will arise because users are placing Python "scripts" into the scripts folder.

GNUtux, I apologize if my preceding post came across as overly brusque and critical; however, I think that much confusion could be avoided early on if the distinction is made that -- under the terminology adopted by the GIMP project -- Python plug-ins are just that, plug-ins. To conflate them with scripts as Photocomix suggests is begging for years and years of having to handle questions from users about why their Python scripts don't work (haven't we had enough of that?).

Maybe I'm misconstruing, but the problem is not confusing Python plug-ins with C plug-ins, but with distinguishing between Python plug-ins and Script-fu scripts. A script runs on all platforms -- GNU/Linux, Windows, MacOS, Solaris, BSD; any system which runs GIMP. Getting a Python plug-in to run is just as difficult, if not more, than getting a plug-in written in C to run.

If you want to teach someone, you don't tell them what is convenient for them to hear, but the way things are in actuality. If you are going to provide plug-ins at gimpscripts.com -- and by all means do -- at least let the recipients know what they are getting. If that means re-defining terms for which they've already formed preconceived, contrary, notions then doing so is far more beneficial than not defining anything (consider the distinction made by GIMP between 'scaling' and 're-sizing' -- it is not possible for someone to receive instruction until the teacher and the student share the same understanding of the terms).

thanks

I always have trouble finding these things in the menu, but find it I DID!
here's my Aurora effort:

@Saulgoode
you say that you could not disagree more...but why to disagree if we come exactly to the same conclusion ?



Quoting myself



and



and me





so where is the conflict with



I know you didn't like the start of my message ....but why to disagree for the start if at the end the conclusion is exactly the same:
Python plugin should be called plugin not script because are plugin
...and because the distintion will help users put python plugin in the right plugin folder

even if they don't look as a (compiled) plugin but as "a bunch of words" (to quote a commune users remark" Hy the link is broken there is not a plugin there ...i got only a page with a bunch of words ) they are and we should define them plugin

I like the gimpscript site...but I do prefer that links open up in a new window so when I want to go back I don't have to keep clicking the back button but can just close the window. Small thing, I know, but just something I noticed.

Thanks for bringing this to my attention. I'm not sure what happened. The file was there but somehow the filename in the link was incorrect. It could be a bug in the upload routine, which still needs work.
In any event, it's fixed now.


I prefer to open links in a new tab/window, as well. Are you referring to links that navigate within gimpscripts.com or links that take you away from the site?

This thread brings up an interesting discussion as to what constitutes a "script". The term script actually grew out of low level communication routines where code from two systems engaged in a dialogue, much like two actors in a play, thus the term "script" was born. It goes a little something like this... System A communicates with system B requesting a dialogue. System B may respond or may wait for another response, depending on the last response from System A. System A waits for System B to respond. System B responds and waits for System A to respond. The dialogue continues until both parties agree the conversation is over, usually with a "handshake". Close curtains and take a bow.

A more modern/evolved definition of a "script" is code (or a system) that engages in a dialogue with another system in an external/independent manner and can be added or removed without disabling the main system. In the case of GIMP, a interpreted Scheme or Python program (or even a compiled Python or C binary) fits the modern definition of a "script". GIMP-Python is referenced in the documentation as a "scripting" extension for GIMP.

I actually see both sides of this issue. As PC noted, the end user doesn't care about distinctions that we might happen to make, but as Saul mentioned, it's important to avoid confusion on how to install the various scripts and plug-ins the end user might encounter.

End users just assume that .py scripts and binaries are installed the same way they've installed Scheme scripts, by just copying into the /scripts folder. And to add to the confusion for the end user, both Scheme and Python scripts are also referred to as "plug-ins" all though the GIMP documentation and wiki.

Considering the GIMP convention that .scm scripts be placed in the /scripts folder and .py scripts and compiled binaries be placed in the /plug-ins folder, it does make sense to refer to them as "scripts" and "plug-ins", respectively, so as to mitigate confusion by the end user when installing, even though my view of what constitutes a "script" is broader than what Saul, or someone else, considers to be a "script".

We already have threads here on GIMP Chat that explain how to install the various scripts and plug-ins that a user might encounter, so I can just link to them from the GIMP Scripts site.

As a rule, I don't think I will accept uploaded binaries on GIMP scripts, so as to avoid malware and viruses, but I would consider hosting certain binaries from trusted sources.

What about changing the site tagline to "GIMP Scripts and Plug-ins", which would cover all the bases.

That makes sense, "GIMP Scripts and Plug-ins" is perfect.

Bump

@GnuTux i just noticed that the "Top Scripts" links to the right side only allow to automatically dl the script
I will prefer instead link directed to the script descrition...may be me but i want to know first what a script does and for what version of gimp is, then maybe i would download it

PC when i click the link it takes me to Tux's website.

No, PC is right, some of those scripts downloaded (not all) when I clicked on the links at the top. Some may have direct links to the downloads.

My initial thinking was that the "Top Scripts" on the right side would be a direct download and the navigation links on the right would allow you to browse before downloading. However, I agree with you on this. I've now configured the "Top Scripts" list to redirect to the script's page.

Thanks for your input!!


The scripts ticker at the top of Gimp Chat will take you to that script's page on gimpscripts.com. PC was referring to the "Top Scripts" list on the right side column of gimpscripts.com, which I've now configured to redirect to the script's page, rather than directly download the script. I think I've got 'em all.

I'd like to give a shoutout to RobA, Fencepost, SaulGoode, Ofnuts, Paynekj and Graechan for giving me permission to mirror some of their scripts on gimpscripts.com. They have also graciously agreed to post a few scripting related articles on occasion. Thanks again to everyone who has contributed to the website.

luv the site! you spoil me, i feel like a kid in a toy store.

This thread was long dead, and I apologize for resurrecting it, but it seemed the right thing to do all things considered.

The site lacks one feature in my opinion. A full listing, preferably alphabetized.

Like many GIMPers, I like to try new things, and that includes scripts and plugins. But when I go looking for them I am not usually looking for something specific. Using the registry as an example here, I just go in and pull up the alpha-list, and skim through to see what catches my eye.

I don't know if others do this or not, but I presume I cannot be the only one in the world who does.

Give it a thought next time you are updating, or maintaining the site.

Can you provide an example of how an alphabetical listing has been used in a large forum setting?

After the basic structure of a forum is in place the members control the placement of content by category, title and position (date/time). A moderator only controls content when a topic is obviously in the wrong category or removes unacceptable posts. Other than browsing by category list Gimp Chat offers basic search (like all forums), an excellent advanced search, multiple (5) additional ways of viewing content. View unanswered posts | View active topics | View unread posts | View new posts | View your posts, plus the Tutorials Index.

Odinbc Misunderstanding I think. I was refering to gimpscripts.com. And the format I was thinking of is: http://registry.gimp.org/glossary

My bad.
Have you tried the Gimp Script tag cloud?