Hello all,

I just finished the text-box tutorial in the gimp docs so I am fresh off the boat. I'm a java programmer by day, so my thoughts went to understanding what methods were available for debugging the buggy scripts I'm bound to write. So I saw gimp-message in the procedure browser and thought I would just throw it in the script, which would also answer if the message halted script running or not. But I got

Error: ( : 1) eval: unbound variable: gimp-messsage

Then I made the following procedure and registered it

(define (script-fu-text-test)
(let*
(
(msg "The message")
)
(gimp-messsage msg)
)
)

Got the same error. I opened the script-fu console and entered
(gimp-message "Test")

and I got
(#t)

I typed
(gimp-message)

and got
Error: ( : 1) Invalid number of arguments for gimp-message (expected 1 but received 0)

So the console clearly knows of a procedure called gimp-message. As to the #t output, not sure what to make of that. But primarily, what have I done wrong in my script such that it cannot be evaluated.

Any help is appreciated!

Fixed! Thanks to trandoductin for noticing the triple 's'

imanoob

yeah coming from java you have auto complete so you don't make such mistake and it highlights it if you're wrong...

So excited to see another script coder joining gimpchat.

Oh, Boy!! Does this mean more toys for Christmas?

Seriously you should be using Python, not script-fu.

LOL

It's true it's true.
I could probably live without scheme script-fu but i don't know if i could live without python-fu

What, in a nutshell, would you say are the advantages with Python for plugins? I've used Python years ago, but I'm not familiar with gimp's bindings, or really scheme's not quite yet.

- Python is a much simpler language to learn
- Python code is usually shorter
- In Gimp, everything that can be done in Scheme can also be done with Python
- Python can do plenty of things that you can't do in Scheme
- Python code can use plenty of useful libraries that come standard, and if necessary import non-standard ones

And what i really like about about it is once you have the menu registered with parameters (after having to reload GIMP) but the trade off is if you make any changes to your code that does the actual work, you don't have to refresh anything... so you can go nuts (no pun intended) after registered successful.

EDIT: Oh yeah, and you can return things from sub-functions, I don't think scheme script fu allows you to return anything.

Thanks. I appreciate the feedback. Whereas scheme seemed like a nifty puzzle at first I am getting tired of the forests of parentheses. And constraining flow control options.

I thought scheme acted like somewhat like a unix script and just the last thing declared/stated in a function was the return value. I know part of the gimp doc scripting tutorial I went through had as a last exercise making the menu bound function call return a value so it could be called from another script.

I guess you're right, bittramp, last variable declared is returned to the caller (Saulgoode can tell it better)

edit: found something which confirms that assumption
viewtopic.php?f=8&t=11533&hilit=saturation

Tiny scheme in Gimp is. Little brother of (fullgrown) Lisp as e.g. Common Lisp, which van do rather all.
Now the joke: L(ots of) I(rritating) S(ingel) P(aretheses)

really? I guess when i tried it i was never successful at returning so i gave up.

Yes, but, as you say, little brother, who can barely walk alone, and you can't use the full-grown brother instead.