RobA told time ago that the script should accept relative paths but for me didn't worked

I may have goofed somehow but i tried long with no joy...

To clear the point here a screenshoot of my "ShellOut" folder



ShellOut.py should call xnview.exe that is in a subfolder of the same folder


PM-ShellOut.py is a different version , modified to call a font manager.

that again is in a subfolder of the same folder

the idea is that if the path are relative, i may transfer easily everything without having to edit again all paths
in the py flie

i zipped the 2 script , ShellOut give me a error ,i suppose for the path
PM_ShellOut apparently doesn't work at all ,meaning that doesn't show up in the menu

if may help i may upload the whole folder

Should work.

I just tried this:


and it worked OK. That is the path to mspaint relative to the plugin folde

Try something like "\"XnView\\xnview.exe\""

or maybe "\".\\XnView\\xnview.exe\""

-Rob A>

Thank my ADSL broke when i was editing my message and went back just now, i will try again following your suggestion

i tried both , no joy
not sure if the error message may be useful



i copy here my version of the script anyway i changed only the xnview entry (and i tried only with xmview option )
and the menu location...

And the other script the version you simplified to call a font manager did not even show in the menu

I tought the best way to understand what went wrong was upload a zip with everything:
once unzipped should be sufficent to add from gimp a path from preference to the folder to make it work...or hopefully to see what went wrong


LINK http://www.megaupload.com/?d=O04UKTRZ

I am curious about the FM_Shellout.py script.Would you mind sharing it?
I didn't know that was possible to call out another font manager through Gimp.

It is inside the zip,but didn't work, here may be a error of copy and paste, the script didn't even show up in the gimp menu

originally i asked to call the gimp gimp theme switcher, then i tought was handy to call a font manager

Differ from the original shell out script because no image has or data has to be send and returned back, so is more simple

i just recover the original from the message of RobA i post below (just in case the copy i included in the zip in the first message went somehow mangled

#############################

#!/usr/bin/env python

from gimpfu import *
import shlex
import subprocess
import os, sys

def plugin_main(image, drawable):
# Command line - Change to match where the theme switcher binary is located
command = "\"C:\\Program Files\\GTK2 Themes\\xxxxxxx.exe\""
args = shlex.split(command)

# Invoke external command
pdb.gimp_progress_set_text ("run XnView...")
pdb.gimp_progress_pulse()
child = subprocess.Popen(args, shell=False)
child.communicate()



register(
"python_fu_runprog",
"Run a program",
"Run a program",
"Rob Antonishen",
"Copyright 2011 Rob Antonishen",
"2011",
"<Image>/Edit/GTK Theme Switcher",
"",
[],
plugin_main,
)

main()

############################

but i cannot even see it in the menu

I am not sure what you are trying to do other than call the font manager and XnView through the same folder, but here is what i did.
I added the folder to C directory, and renamed it "shell_out_Font_frenzy"
And added it to Shellout like this


It works as long as you have a layer in your document.

Oh okay i see what you are trying to do now.
Every time i try and add two different call python scripts only one will show up in the menus.Must be something in the script calling the same two values maybe?

The basic thing i was trying to do is make the script working with relative path, so i may use with my portable gimp

I can't use absolute paths because the HD may be C or even D and there is no way to predict the letter of the USB drive
so i can't indicate path as in "\"C:\\Program Files\\Project Dogwaffle Professional\\dogwaffle.exe\""

But if the absolute position may change the relative path will be always the same,

If the content of the folder (see screenshot in first message ) is no changed , whatver that folder will be moved or copied the relative path,that are f for subfolder(s) of the same directory, the same folder were is the script will remain always the same
...so path as "./XnView/ xnview.exe " should work (or //XnView//xnview.exe or
".//XnView//xnview.exe") SHOULD work

BUt in practice they don't work maybe for a my dumb error , anyway i need help to find the error , if in my paths or in the script or ...



ah happens to you ,too

the scripts have 2 different procedure names , and 2 different registry paths so should not conflict
anyway i cannot use neither , one because give me error with relative paths, and the other because do not even show up

Kevin thank, i will correct the bracket, about the name i believe "python_fu_runprog" is unique the other script is called ""python_fu_shellout", and i can't see other with conflicting names

sorry you can't get the zip there is some other place where i may upload that will be no blocked by the firewall ?

anyway from the screenshoot the architetture should be visible
Do the error message i posted refer to a wrong path or was about something else ?

and bigger problem for me which should be the correct relative path?
i still get error with both the path indicatewd by RobA in his reply

PhotoComix

Don't worry about putting your zip file somewhere else, I could get to it when I am at home.

But I think I know why it's not working with relative paths. The problem with relative paths is that they are relative to the current working directory. On Linux that may be the plug-ins directory, but on Windows it's not so simple.

If I start GIMP by double-clicking the executable C:/Program Files/Gimp-2.0/bin/gimp-2.0.exe, then the working directory is C:/Program Files/Gimp-2.0/bin/ and the paths are relative to there.

If I start GIMP from a short-cut, where the Start in field is set to "%USERPROFILE%\My Documents\My Pictures", then that is my working directory and paths are relative to that directory.

You will need to find out where the current working directory is and specify the relative path from there.
To find out the current working directory I added a line to your code before " # Invoke external command":

Code: Select all

  raise NameError(os.getcwd())


Which generates an error:

Code: Select all

NameError: C:\Program Files\GIMP-2.0\bin


Personally I'd opt to change the ShellOut plug-in to remove the paths and do it the same way the Photivo people did - first time prompt the user where the executable is and save the answer in gimprc (see the Gimp to Photivo section of http://photivo.org/photivo/download_and_setup/gimp)

Kevin

You hit the nail in the head !!
That was my first doubt try to use relative path:
relative to WHAT ?

But then i hoped that the most simple and logic , relative 1 of the 2 extremes , in this case relative to ShellOut.py and leading to the app to call so " ./XnView/xnview.exe"
(or "/XnView/xnview.exe" or ".//XnView//xnview.exe but anyway the starting point of the path was the active script that had to use the path )

I had some doubts (as...maybe was Python.exe to execute the script so the path should start from python.exe ?) but i was hoping for the best...i mean what the sense of a relative path if is so hard to guess know , to WHAT is relative ?

I really hope to clear this point and to solve, i am stuck here from a couple a weeks

still lost with the realative path

PC are you trying to run Font Frenzy so Gimp will grab the font you want in Font Frenzy and use it?
Like Dynamic Text?
I like the idea of just being able to see the fonts bigger (that's nice).A much larger preview.
Using Font Frenzy called through the original ShellOut works for better previews of the font you plan to use.
I guess i am not still sure what you are trying to do.

Themes i can understand because those are built for Gimp, and other GTK programs.(Inkscape for instance)
Did you actually get Themes to work yet?I couldn't through this script.Only themes 1.0 works for me.

Sorry i do not understand what you are trying to accomplish.

In GNU/Linux, any path which does not start with slash ("/") is relative. If it starts with a slash then it is absolute, more commonly referred to as "fully qualified". Note that I am referring to the expanded pathname, if your pathname starts with a variable (e.g., $HOME/.gimp-2.6) then it is the pathname that results after the value of $HOME is substituted that determines whether the path is relative or fully qualified.

For GIMP, all relative paths are relative to the working directory at the time GIMP is started. If you are starting GIMP from a desktop icon then this working directory is usually specified as a property of the icon (in Windows, I believe there is a shortcut preference called "Start program in..." or somesuch).

It is possible that the ShellOut plug-in is changing the working directory before searching for the files (but I doubt it).

If that is all you need, just delete the C: -- your path will be fully specified to the particular drive you are on (unless Microsoft has changed things recently).

@Paynekj, why are Xnview and Fontfrenzy in the GIMP plug-ins folder? They are not plug-ins.