Re: [Gimp-developer] Feature Request for 1.3
[EMAIL PROTECTED] writes: Hello Gimp Devel. First off, I started playing with GIMP 1.3 last night and it is awsome. The 1.4 stable series is going to be amazing. Thanks ;) I wanted to take this oppertunity, early in the devel work on 1.3 to restate an old nagging feature request of mine: The only feature I miss when I use GIMP is that of Photoshop's brush cursors. In Photoshop, when you choose a 12pixel brush, your cursor becomes a 12pixel sphere (or whatever shape of the brush) to illistrate where your paint is going to drop. This is, IMHO, a very very useful image editing tool. I'd requested this type of ability in the 1.1 and 1.2 development stage but was asked to wait for 1.3. I do alot of image cleanup and when editing an image border (say, painting out a background) its really helpful to know exactly which pixels are going to be changed. This has been requested several times, has been an issue on irc and everybody seems to agree that we want this feature. Why don't you go ahead and add it as an enhancment bug to http://bugzilla.gnome.org with 1.4 as target milestone? Just to make sure it won't get lost... ciao, --Mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Help file index RFC
Hi Syngin, syngin [EMAIL PROTECTED] writes: The time has come to determine an index system for the new help package. The entire help system will be changing (as previously determined) and initial discussions with Sven have leaned toward an XML index and precompiled HTML help files. The role of the index will be to eliminate hard coded file links inside The GIMP's mighty core which will in turn lead to greater i18n flexibility. We have now reached a point in discussions where other's are encouraged to comment on how this might be achieved. Everything that's needed from the gimp-help module side is an index file which contains an identifier -- document_index mapping for the chosen target format (e.g. HTML). The GIMP core itself will not need to know at all about this index file, as the core will only reference the identifiers. I suggest a naming scheme with a prefix identifying the help domain (e.g. gimp-rect-select-tool, gimp-file-new-dialog, gimp-foobar). The help browser will read the index file, which, for the HTML case, might be as simple as: --- gimp-rect-select-tool tools/rect-select.html gimp-file-new-dialog dialogs/file-new.html gimp-foobarfoo/bar.html --- This way we remove all HTML links from the core and are able to use any target format like PDF. The browser gets passed the help identifier together with the help domain (which will be NULL for all pages shipped with the gimp-help module). The help domain is used for 3rd party plug-ins where it's the file system path to the plug-in's help stuff. To be flexible enough for future extensions or help formats, I suggest the installed help files to follow a standard hierarchy. What about: help_root/html/ help_root/html/C/ help_root/html/C/INDEX help_root/html/C/... help_root/html/de_DE/ help_root/html/de_DE/INDEX help_root/html/de_DE/... help_root/pdf/ help_root/pdf/C/ help_root/pdf/C/INDEX help_root/pdf/C/... help_root/pdf/de_DE/ help_root/pdf/de_DE/INDEX help_root/pdf/de_DE/... so the HTML help plug-in will know that it needs to look at help_domain/html/locale/INDEX the PDF help plug-in will open the help_domain/pdf/locale/INDEX index file. IIRC, this roughly what we discussed on #gimp a few months ago, feel free to comment or eek... ciao, --Mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Feature Request for 1.3
[EMAIL PROTECTED] (Raphael Quinet) writes: On 08 Jan 2002, Michael Natterer [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] writes: The only feature I miss when I use GIMP is that of Photoshop's brush cursors. In Photoshop, when you choose a 12pixel brush, your cursor becomes a 12pixel sphere (or whatever shape of the brush) to illistrate where your paint is going to drop. This is, IMHO, a very very useful image editing tool. I'd requested this type of ability in the 1.1 and 1.2 development stage but was asked to wait for 1.3. I do alot of image cleanup and when editing an image border (say, painting out a background) its really helpful to know exactly which pixels are going to be changed. This has been requested several times, has been an issue on irc and everybody seems to agree that we want this feature. Why don't you go ahead and add it as an enhancment bug to http://bugzilla.gnome.org with 1.4 as target milestone? Just to make sure it won't get lost... There is already a bug report about this feature, so there is no need to submit a new one: http://bugzilla.gnome.org/show_bug.cgi?id=32498 Its current title is Pointer should reflect toolsize and it already has the target milestone 1.3.x. I am going change the title of this bug report so that it includes at least the word brush (easier to find). Thanks, I searched bugzilla because I was sure it was there but didn't find it ... :) --M ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] PDB entries for Bezier Select and Intelligent Scissors
I have searched in vain for PDB entries for both the Bezier Select and the Intelligent Scissors. Checking the source reveals that there are, indeed, no such entries. Is this intentional? If not, could someone with a whole lot more experience in hacking the GIMP itself make the proper entries? I'm using GIMP-1.2.2 on Linux (RH-6.1) GIMP installed from the tarball. Thanks, -- --Jeff Jeff Trefftzs [EMAIL PROTECTED] http://www.tcsn.net/trefftzsHome Page http://gug.sunsite.dk/gallery.php?artist=68 Gimp Gallery http://trefftzs.topcities.com/home.html Photo galleries ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
