Aha! Excellent, that works. Thank you David, I'll have another try now.

Edit:
Just as a footnote:
Script-Fu does provide some platform-specific literals to construct pathnames, including:
gimp-directory = "/home/<user>/.gimp-2.8" (Linux) or "\Users\<user>\.gimp-2.8" (Windows)
DIR-SEPARATOR = "/" (Linux) or "\" (Windows)

So the same effect can be achieved thus:

We have the technology to re-build him it...







@Graechan
I've tested this on Linux but not Windows ..it should work okay, but...
Please give it a good testing and then, if and when you're happy, make an official release on GimpScripts.
(Change my "hack3" designation to your Rel 1.5 or whatever.)

Unzip and copy both files to your personal scripts folder.

Edit:
I have now tested this on Windows 7 x64 and it seems to work okay.. over to you Graechan.

That's strange!
Has anybody else tested this latest version - if so, did it work? (I notice that it's been downloaded several times, presumably by people other than Graechan).

@Graechan:
please try starting Gimp from console and see what messages come out when you try running the script for eg. "Hallucinogenic".

It runs OK on my Linux gimp 2.8.14 running Gmic 1.6.3.1.

Okay, thank you Kimba.

The initial declaration (at line 86 in the latest script):

sets up the path-string which will be passed to the G'MIC plugin and thence the G'MIC interpreter.

[The "@{-path_gimp}" tells the G'MIC interpreter to use the setting in it's environment variable "path_gimp" as the start of the pathname; that should be automatically set to "C:\Users\<user>\.gimp-2.8" on a Windows system.]

As I said above, please try starting Gimp from console and see what messages come out when you try running the script for eg. "Hallucinogenic".

This is the error returned when running

Why would there be a problem with portables? So long as there is a "scripts" folder in the gimp-directory it should work - even if the gimp-directory is something outlandish like "Z:\some\path\via\Timbuktoo\.gimp-oujamaflip" so long as the G'MIC environment variable "path_gimp" is set to that path (which it must be for G'MIC to work at all) and there is a "scripts" folder in that directory, then it should work.

As to the matter of script managers installing to sub-folders, I don't really see a way around that at the moment.

That would be a folder called "gmic-presets" in your main gimp-directory (ie. .gimp-2.8).
I can't see that really helps either with scripts managers installing to sub-folders or with portables.

Do I need the presets file and if so, where does the presets file go? I have Windows 7. 64 Bit.

Tested out the script presets these are the ones that didn't appear or give an error:
Hallucinogenic
In the Bushes
Flowers

Both the .scm and the .gmic file must go in your user scripts folder - NOT the system-wide scripts folder
ie.
On Windows: C:\Users\<user>\.gimp-2.8\scripts
On Linux: /home/<user>/.gimp-2.8/scripts

For me on my PC, all of the presets now work through the GMIC Logos script. Thanks Jontait2.

How so? It sounds like you're thinking of treating the .scm and .gmic as separate entities to be handled by installation managers. But if they are treated as separate entities, they can still both be installed to the normal scripts folder (surely?).


Including the presets in the script itself is a pretty horrible solution - I did have a look at that when David first suggested using a .gmic file, but there are problems:
- the entire set of presets would have to be stored in the script as one great long string (approx 60,000 characters) - which may be problematic - or broken-up into manageable units. I'm not sure whether TinyScheme does actually have a maximum string-length, but I have had problems trying to use very long strings before;

<Image> Script-Fu> Logos> Gmic logos

These filters are not available in Gimp-G'MIC itself - even after installing this script you still won't be able to invoke the presets actually used by the script manually from the G'MIC plugin's menu tree - the presets are only loaded temporarily when the script runs, and then immediately forgotten about. The next time you run Gimp G'MIC it will have no "memory" of the presets!