User login
Syndicate
Guillotine into Layers
Short description:,
The Guillotine-into-Layers plug-in is a variation on the Guillotine plug-in by Adam D. Moss. It is intended to address a shortcoming of the original: Too many windows opened! There is, however, a trade-off.
Advantages:
The Guillotine-into-Layers plug-in slices the original image along guides just as does the standard Guillotine plug-in; however, instead of spawning many new images - which clutter the desktop and bog down the processor, this plug-in makes only one new image with multiple layers - one layer for each rectangular region. The user can then selectively copy a single layer from this new image, and paste it as a new image, giving the user greater control. Furthermore, the new image is named with the *.xcf file suffix. That way, if the user needs to stop processing the layers of the new image before s/he is done, then s/he can simply save the new image in the GIMP's native format - which preserves multiple layers.
The trade-off:
When the original Guillotine plug-in slices an image, each new image has the same number of layers as the original, each copied from the same rectangular region. On the other hand, the Guillotine-into-Layers plug-in performs a copy-visible-layers action over each region to produce a new layer for the resulting image - implicitly merging the original layers.
Update 2009-11-8:
The second package - v.0.1.1 - contains an executable compiled for Windows platform and French translations - both from samj. See:
http://registry.gimp.org/node/19886#comment-5923
Update 2011-03-02:
The third package - v.0.1.2 - includes German translations from Avarra64. Otherwise, it is identical to the previous package. Vielen Dank, Avarra!
Note: Internationalization 2011-03-02:
If you are attempting to install this package in a language other than English (French or German as of now), I just discovered that I left out a key piece of information...
In the C header file "src/plugin-intl.h", line 40 reads:
#define LOCALEDIR "/usr/share/locale"
The macro LOCALEDIR is is supposed to be the directory where your system stores all available translated texts for all installed applications. I am using Slackware Linux, for which this macro is accurate. You might need to edit this line in order for your installation to be successful. (The file is read-only by default, so in this case, you'll have to change its permissions.)
| Attachment | Size |
|---|---|
| guillotine-into-layers-0.1.tar.gz | 21.96 KB |
| guillotine-into-layers-0.1.1.tar.gz | 26.75 KB |
| guillotine-into-layers-0.1.2.tar.gz | 27.44 KB |
| guillotine-into-layers-0.1.2.zip | 35.39 KB |
Comments
Windows binary Gimp 64 bits Guillotine into Layers
Bonjour,
http://aljacom.com/~gimp/guillotine-into-layers-0.1-64bits.zip
38 840 bytes
Deutsche Beschreibung Guillotine - German description Guillotine
A German description for Guillotine-into-Layers you will find here:
http://www.gimp-atelier.org/forum/viewtopic.php?p=8056#p8056
Eine deutsche Beschreibung von Guillotine-into-Layers findet ihr hier:
http://www.gimp-atelier.org/forum/viewtopic.php?p=8056#p8056
Loves from Germany
Avarra
Not working...
I do not know why, but the plugin is not working for me. When I use guillotine, it still uses the built-in method, and there isn't any other guillotine option available. I use Gimp2.7.0 on WinXP SP2, and installed this plugin the same way and into the same folder as all my other plugins.
Any suggestions?
Compile error on Ubuntu 9.10 with GIMP 2.6.8
I tried compiling it with make, sudo make install and got these errors
make -C po
make[1]: Entering directory `/home/antonio/Desktop/guillotine-into-layers-0.1/po'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/antonio/Desktop/guillotine-into-layers-0.1/po'
make -C src
make[1]: gimptool-2.0: Command not found
make[1]: Entering directory `/home/antonio/Desktop/guillotine-into-layers-0.1/src'
cc -O3 -Wall -c -o guillotine_into_layers.o guillotine_into_layers.c
guillotine_into_layers.c:28:26: error: libgimp/gimp.h: No such file or directory
guillotine_into_layers.c:29:18: error: glib.h: No such file or directory
guillotine_into_layers.c:39: warning: type defaults to ‘int’ in declaration of ‘gchar’
guillotine_into_layers.c:39: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
guillotine_into_layers.c:46: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘guillotine_into_layers’
guillotine_into_layers.c:51: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘PLUG_IN_INFO’
guillotine_into_layers.c:63: warning: return type defaults to ‘int’
guillotine_into_layers.c: In function ‘MAIN’:
guillotine_into_layers.c:65: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
guillotine_into_layers.c:94: warning: type defaults to ‘int’ in declaration of ‘gchar’
guillotine_into_layers.c:94: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
guillotine_into_layers.c:160: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘position_compare_func’
guillotine_into_layers.c:167: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘guillotine_into_layers’
guillotine_into_layers.c:435: error: expected ‘{’ at end of input
make[1]: *** [guillotine_into_layers.o] Error 1
make[1]: Leaving directory `/home/antonio/Desktop/guillotine-into-layers-0.1/src'
make: *** [src] Error 2
antonio@computerfood:~/Desktop/guillotine-into-layers-0.1$ sudo make install
[sudo] password for antonio:
make -C po install
make[1]: Entering directory `/home/antonio/Desktop/guillotine-into-layers-0.1/po'
for L in ; \
do install -v -m 0644 $L.mo "/usr/share/locale/$L/LC_MESSAGES/"gimp-plugin-guillotine-into-layers".mo"; \
done
make[1]: Leaving directory `/home/antonio/Desktop/guillotine-into-layers-0.1/po'
make -C src install
make[1]: gimptool-2.0: Command not found
make[1]: Entering directory `/home/antonio/Desktop/guillotine-into-layers-0.1/src'
cc -O3 -Wall -c -o guillotine_into_layers.o guillotine_into_layers.c
guillotine_into_layers.c:28:26: error: libgimp/gimp.h: No such file or directory
guillotine_into_layers.c:29:18: error: glib.h: No such file or directory
guillotine_into_layers.c:39: warning: type defaults to ‘int’ in declaration of ‘gchar’
guillotine_into_layers.c:39: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
guillotine_into_layers.c:46: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘guillotine_into_layers’
guillotine_into_layers.c:51: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘PLUG_IN_INFO’
guillotine_into_layers.c:63: warning: return type defaults to ‘int’
guillotine_into_layers.c: In function ‘MAIN’:
guillotine_into_layers.c:65: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
guillotine_into_layers.c:94: warning: type defaults to ‘int’ in declaration of ‘gchar’
guillotine_into_layers.c:94: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
guillotine_into_layers.c:160: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘position_compare_func’
guillotine_into_layers.c:167: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘guillotine_into_layers’
guillotine_into_layers.c:435: error: expected ‘{’ at end of input
make[1]: *** [guillotine_into_layers.o] Error 1
make[1]: Leaving directory `/home/antonio/Desktop/guillotine-into-layers-0.1/src'
make: *** [install] Error 2
Solved!
I downloaded libgimp2.0-dev and it now compiles on Ubuntu 9.10
Windows binaries
http://www.aljacom.com/~gimp/guillotine_into_layers-0.1.zip
Tested with Gimp 2.6.7 Vista
Windows binaries
Merci beaucoup!
Thank you very much!
Comment cela fonctionne-t-il ?
How does it work for you?
Apportez une traduction a la Francais (fr.po) s'il vous plait?
Could you please provide a French translation file (fr.po)?
Apportez le code pour la compilation pour Windows (Makefile?) s'il vous plait?
Could you please provide the compiler code (Makefile?) for installing this plug-in on a Windows platform?
Cordialement... yours,
Randall
Post-scriptum:
Je ne parle/lis/ecris Francais bien pas. Je possede US-clavier.
Windows binaries
it works for me too
But the package is too confusing for Windows users :
Only the exe and a README.txt (with how to install and link to the code ) are needed
Well even the translation files may be useful but few will know were place them..that should be explained in the README.txt
(but few will read a README.txt if not as last resource )
But the package is too
But the package is too confusing for Windows users :
Only the exe and a README.txt (with how to install and link to the code ) are needed
The package is not only for Windows users, and it's better to include sources.
... and there are Windows
... and there are Windows users who know how things are supposed to work. I appreciate it when people who provide binaries to not limit the packages to the lowest common denominator.
Knowledgeable Windows Users Wanted
Hi, schumaml!
If you contact me with the instructions necessary to compile and install the original guillotine-into-layers on a Windows platform, then I will repackage the plug-in with that information and replace it! I would certainly prefer that over simply providing the pre-compiled binary for the lowest common denominator. After that, when I re-release the package, it will be compressed as a .zip file.
Yours,
Randall
Building instruction (for
Building instruction (for GIMP, but that doesn't really matter) are available at http://wiki.gimp.org.
Currently the wiki is offline, but when it is back you could get the guide from there and include it in the packages.
Thanks
Thanks
does it work for you? it
does it work for you?
it works well.
****
you please provide a French translation file (fr.po)?
#: ../src/guillotine_into_layers.h:37
#: Blurb: Brief description
msgid "Slice visible contents of image along guides into layers of a new image"
msgstr "Découpe les contenus visibles définis par des guides en calques dans une nouvelle image"
#: ../src/guillotine_into_layers.h:38
#: Help Paragraph: Detailed description as it appears in the plug-in browser
msgid ""
"Guillotine-into-Layers is a variation on the standard plug-in Guillotine. "
"This plug-in creates a new image with a number of layers - one for each "
"rectangular region defined by the guides and edges of the original image. "
"The visible contents of each rectangular region are copied, and then pasted "
"as a unique layer of the new image. The new image derives its name from "
"that of the original. It is given the suffix '*.xcf' so that it can be "
"readily saved in a format which preserves multiple layers. The original "
"image is unaffected."
msgstr ""
"Guillotine-into-Layers est une variation du greffon Guillotine. "
"Ce greffon crée une nouvelle image avec calques - un calque pour chaque "
"région rectangulaire définie par les guides sur l'image d'origine. "
"La partie visible de chaque région est copiée et passée "
"comme un calque unique sur la nouvelle image. Le nom de la nouvelle image provient "
"de l'image d'origine. Le suffixe '.xcf' permet "
"de sauvegarder l'image dans un format qui préserve les calques. L'original "
"n'est pas affecté. "
#: ../src/guillotine_into_layers.h:39
#: Author Name:
msgid "Randall Sawyer"
msgstr "Randall Sawyer"
#: ../src/guillotine_into_layers.h:40
#: Copyright Declaration:
msgid "Copyright (C) 2009 Randall Sawyer"
msgstr "Copyright (C) 2009 Randall Sawyer"
#: ../src/guillotine_into_layers.h:42
#: Menu Item Label: Label by which the user chooses this tool
msgid "Guillotine into layers"
msgstr "Guillotine into layers"
#: ../src/guillotine_into_layers.h:44
#: Error message: New image is created, but it is missing layers
msgid "warning: Failed to create at least one expected layer"
msgstr "avertissement: Impossibilité de créer au moins un calque comme prévu"
#: ../src/guillotine_into_layers.h:45
#: Error message: No new image was created
msgid "error: Unable to create new image"
msgstr "erreur : Impossible de créer une nouvelle image"
#: ../src/guillotine_into_layers.h:47
#: Root name for a new image:
msgid "Untitled"
msgstr "Untitled"
#: ../src/guillotine_into_layers.h:48
#: What the plug-in has done with the image:
msgid "sliced_into"
msgstr "sliced_into"
#: ../src/guillotine_into_layers.h:49
#: Plural of noun 'layer':
msgid "layers"
msgstr "layers"
#: ../src/guillotine_into_layers.h:50
#: Singular of noun 'region' - refers to rectangular region:
msgid "Region"
msgstr "Région"
****
you please provide the compiler code (Makefile?) for installing this plug-in on a Windows platform?
It's not necessary on a Windows platform (There is no change in your source code).
French Translation & Windows
Hi!
I have updated this plug-in package: It now contains samj's French translation, the Windows executable, and instructions for installing on a Windows platform. I have made it available as an alternative attachment: 'guillotine-into-layers-0.1.1.tar.gz'. ( See top. )
Merci, samj!
Yours,
Randall
French Translation & Windows
If contain the Windows binary a zip would be a better chose then tar.bz.
In Windows zip could be opened on the fly, with no need of additional software (at least in XP, Vista and 7 ) but not tar.bz
Also will make more clear at first glance wich is the Windows version, ( Win users are familiar with zip, and may believe .tar.bz for source code and linux binary
Even if is easy open tar.bz with something as 7zip
File Compression
Hi, PhotoComiX!
The next time I re-release this package, it will be as a .zip file, per your request. However, not until I get some assistance with compile-and-install instructions for the Windows platform. (See my response to schumaml above.)
Yours,
Randall
File Compression
i saw
to run on win only move the exe exe file in a gimp plugin folder seems needed
(In this case the plugin doesn't require extra libraries )
Obviously a README.txt files is very useful...do not forget the .txt extension or many will report problem to read the file or simply will give up.
Windows users that may need the source code, in my opinion, will have no problem to get it by the link in the Readme.txt files...for the others may be just confusing a extra folder full of exotic files of no any practical use and that not average user may open...something confusing not a advantage
Who want and is able to compile in Windows just need the link for the project and source code...and here a hyperlink may be better then files because will link to the updated version
Many for windows binary just provide a exe without any note, idislike that , a short and clear README.txt with a how to install and use+ link to the project and the source code is always welcome
But confuse Windows users with extra folders, full of files that a average windows users will be never able to open,.if not after a lot of Googling. (as example INSTALL or MAKE and all others files with no extension) is really not needed
For windows the .exe and a clear READ_ME_HOW_INSTALL_USE.txt is all what is needed, more just would confuse
Of course the link for the source code should be not missed in that READ_ME_HOW_INSTALL_USE,txt
Including source
The provider of the package may be providing the source code within the package so that his GPL3 license obligations are fully met at the time the binary is provided. If only the binary is provided, the distributor is required for three years to, upon request, provide the source code to anyone having a copy of the binary.
correct
So if as example the source was uploaded here, on the plugin page , we may suppose that will remain available for at least 3 years ?
The source ode as a fact is even stripped away from the packages of most linux distro, why we should be more rigorous for the Windows versions?
One simple reason: We are no
One simple reason: We are no Linux distro.
Have a look at e.g. Debian, their ability to provide the source reliably code for many years is beyond anything we'll be able to achieve. Take one simple server outage and a busy schedule for Ingo, then the source code is not available.
BTW, are we discussing
BTW, are we discussing samj's binaries package or Randall's?
Nothing wrong in both
Nothing wrong in both binary
My was just a general point : if possible keep it simple and friendly
But then schumaml
i downloaded a lot of windows binary you compiled, from your side or here, and i seldom found included in their zip the source code
(usually were not zipped with a README file with the link )
Yes, I have to change all of
Yes, I have to change all of the binary packages I offer.
Dreadful Binaries
I have provided no binaries of my own. I am a Linux user. samj compiled my source code into a Windows binary without explaining how. [I really don't like that too much. =( ] In my second attachment ( 0.1.1 ), I have included samj's binary as stop-gap convenience for other Windows users.
compile under Windows
Bonjour,
am a Linux user. samj compiled my source code into a Windows binary without explaining how. [I really don't like that too much. =( ]
I compile under Windows (using MinGW / MSYS) the same way as Linux (There is no difference).
Did you really try this with
Did you really try this with all the GIMP versions you listed?
Applicable Versions
No, I only tried it with GIMP 2.6. There is one C function "gimp_edit_copy_visible" which - according to the notation in the API - was implemented beginning with the release of GIMP 2.2. So, I assumed that my plug-in code would work with all versions of GIMP since that one. If I am mistaken, then please let me know, and I will update this posting.
Yours,
Randall