GNOME Bugzilla – Bug 166935
Wish to be able to cut and paste guides (one, a selection, or all)
Last modified: 2018-05-24 11:25:07 UTC
The ability to copy guides between images would help when comparing them, and when altering a set of related images
Seens reasonable, and it could be done with a couple script-fus - a "copy guides" would attach the guides info to a GIMP parasite, and be completed by a paste guides script. Any other ideas or suggestions?
I get the impression from using GIMP 2.2.3 that quite a lot of stuff is being pushed out to ScriptFu; is that a good thing or not?
What would be bad about it? It allows users to easily implement missing features and to share them with other users. All that w/o cluttering the user interface for those who don't need the feature.
IMHO the only problem about using script-fu for core features is the unfirndship of scheme to human reading, and higher level tasks. I'd be much better with python scripts, but most of the core developers either don't care or keep treating python-fu as a "toy" and script fu as the holy grail of scripting languages. So...all hail Scheme. :-) But back on topic - I had been thinking putting both scripts under the Image ->guides menu, one being a "guides copy" and a "guides paste". I thought about amking them with no dialogs - just like ordinary copy & paste, and, if pasting in an image with a different size than the original, to change the guides location proportionally. Or would it be better to make absolute positioning of the guides, on pasting? Or maybe a dialog on the paste script just asking whether to paste the guides with absolute or proportional coordinates?
WRT sven's question, I would expect that the more features could be written in the base language rather than interpreted at runtime, the faster and more efficient overall The GIMP will be. WRT Joao's thoughts, I would add a configuration option, Absolute, Proportional or Ask and default to Ask. WRT the off-topic language evangelism, d'ya think anybody would be offended if I did a Ruby binding for The GIMP? (-: If none exists already :-)
Why would anyone possibly be offended? The more languages, the better. Go ahead and do a COBOL binding as well if you want. :)
http://sourceforge.net/projects/ruby-gnome/ seems to have a Ruby binding for GIMP. However this project is obsolete and replaced by http://sourceforge.net/projects/ruby-gnome2/ which doesn't have a GIMP binding anymore.
OK, It seems that if I'm to Rubify The GIMP, I should start by seeing how hard it is to jam ruby-gnome into ruby-gnome2, pass the rubber mallet. Providentially, I might be able to cross-pollinate this with a magazine article and do it for fun _and_ profit. I'll keep y'all posted if I can do this.
Hammurabi, I beg to report... downloaded ruby-gnome2-all-0.12.0 and built it (ruby extconf.rb; make; su; make install) on Mandrake 10.1 with all-but-one results: ----- SUCCEEDED: glib gdkpixbuf atk gtk gconf gstreamer libart rsvg gnomecanvas gnomevfs FAILED: pango ----- Done. For completness' sake, I'll have a quick look at making ruby-pango happy before having a whack at a GIMP binding.
Ha, lookie dere! Mandrake already 10.1 has packages for an older version of this. /ME wanders off to Mandrake Cooker, for a source RPM, might as well start with all required dependencies in place. Cooker has the latest version.
Hmmm, it's getting messy. It requires a later pango, which in turn needs later bits of GNOME, which will devolve into hundreds of megabytes of downloads and days of recompiling. I have a laptop to reinstall sometime in the next week, so I'll do that from Cooker and try my luck then.
Hm, if the ruby binding is going to need GNOME - which seems to be the case - it probably won't spread very far. This should be changed. But shouldn't the creation of a Ruby binding be discussed somewhere else - the developers list, for example?
Well, Leon is wrong here. Pango doesn't need bits of GNOME. GIMP already uses Pango, so that shouldn't become a problem.
To be more specific, Mandrake's pango src.rpm was asking for a later version of the Gtk+ libraries, which then cascaded to other things, including GNOME, which depended on Gtk+.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/126.