Main menu
If you'd like to upload plug-ins, please create an account below. You do not need one for download. Enjoy :-)
User login
Syndicate
You are here
Make gradient from panoramics photographs
July 7, 2009 - 12:33 — Giuseppe
| Attachment | Size |
|---|---|
 make-gradient.zip | 1.78 KB |
With this script is easy to create gradients that they simulate a sunset or a natural landscape. You take a photo panoramic, it selects a thin vertical strip and it rotates it in counter-clockwise direction. You read the maximum width of the image and insert it (width / 2) like number of segments in the dialog box of the plugin.
Examples of images created with the plugin
On the left original photo, to right the gradient.
Tutorial
Author web site: xoomer.virgilio.it/lwcon/gimp/python/make-gradient.htm
Code License:
GIMP Version:
Scripting Engine:
- Log in to post comments
Comments
This script can't work !
Maybe by mistake was zipped and uploaded a wrong file
Anyway as it is now this script can't work except to register itself in a menu and display errors if used
see also http://www.gimptalk.com/forum/problem-with-python-fu-script-t45473.html
It works if you create an advanced gradient file...
What you have to do:
Open the gradient dialog and create a new gradient, name it whatever you want and save.
Then when opening the Py gradient plug-in, browse to that gradient file and select it, then set your color parameters and activate the plug-in.
Refresh your gradients dialog and presto, there will be the new gradient file.
I edited my subject line as it was misleading. The above explanation is just one method of getting it to work. Sorry for initial goof.
Ahhh
So basically the script need to overwrite the active gradient ?
And i suppose gives all those errors if the active gradient file has "read only " permission or is in a read only folder?
Compliment to have guessed its logic and to have found a workaround to use it...even without overwriting files not created for the purpose
(apparently the plugin doesn't need the file to overwrite be a gradient file, if is a image overwrite the image, and then crash for the rest of the gimp session )
anyway in my vision a script should NEVER delete or overwrite files without asking confirm
I'm trying to find that solution
You hit the nail on the head, PC. It's refusing to budge on read only folders. Wondering what the big difference between XP and Vista is on this very issue. As of now I have no clue.
should be no much difference
i believe ,in theory "read only" should prevent editing and so overwriting.
But Vista is more mean and severe on the matter, while Xp may allow more easily to overwrite "read only" files
Confusing
Wow. That seems counter-intuitive, having to create a gradient in order to create a gradient!
There are calls in the PDB to create a gradient, given a gradient name. Would that not be a more user-friendly?
-Rob A>
If I knew more about Python, I'd make the changes
Yes, I agree, but it was just "one" way it allowed me to use it. I wasn't suggesting that its how it suppose to work, just offering a method.
It's probably a simple change in syntax in Python for Windows that is blocking Vista machines from creating a file, as it throws a permissions error. I am reading up on it. It worked on my XP machine without any problems.
there are better alternative
as this script http://registry.gimp.org/node/15847 that does the same in a much more intuitive way ... and with no risks to overwrite files
(..and there is a similar script to sample a gradient along a path)
But this python script fired my curiosity because for about 18 hours nobody, including volunteers with some practice of Python scripting , was able to make it work