[Gimp-developer] (no subject)
Hello GIMP team, I've been using Gimp 2.8 and only recently (for some reason) upgraded to 2.10. I am really impressed with all the upgrades. Particularly I've been toying around with the symmetry tool. I am working on a tile based 2D game and I was hoping you could point me in the right direction for an plug-in, or a mod with a particular effect. If you can't help I hope my idea may be an inspiration for further development. With the development of this 2D game I have been copying tiles and placing them around other tiles to see how well they blend together. I have done this to make certain there aren't scattered artifacts touching or forming lines on the borders. Instead I wish that if my cursor hovered over a tile, as described by the grid function, it would repeat the tile either horizontally, vertically or both depending on how I would define a cell elsewhere. For example if I'm working on a south facing hill it would actively duplicate "projections" to either side so I can see how changes affect how the tiles would look together. Alternatively drawing on a west facing wall could repeat vertically. While tiling both vertical and horizontal would be useful for flat surfaces. As is, the tiling function of the symmetry tool can have it's tiles fit to size properly but it makes permanent changes to neighborimg cells. If stroke limits are set to anything but 0 they only repeat to the right and downwards. If the "projections" don't find themselves in the next update I would hope at least the stroke limits could be toggled to work both up AND down, as well as left AND right. Thank you for your time and attention. I am grateful for GIMP and all that it has done for me. I am excited to hear back from you. Respectfully, UltraSilver2. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] (no subject)
On Tue, Aug 27, 2019 at 11:34 AM Bekzod Kobilov via gimp-developer-list wrote: > > Hi GIMP Team, > > I am going through the documentation of GIMP to find out if any software > components or sub-components (libraries, source codes, any extensions) from > third parties are used in GIMP? Or are all of the source code solely > written by developer team? I have looked for the type of diagram that gives > an overview of GIMP's software architechture in GIMP documentation, but i > could not find one. Thanks in advance. $ apt-cache show gimp | grep Depends Depends: libgimp2.0 (>= 2.10.8), libgimp2.0 (<= 2.10.8-z), gimp-data (>= 2.10.8), gimp-data (<= 2.10.8-z), libgdk-pixbuf2.0-0 (>= 2.30.8), xdg-utils, libaa1 (>= 1.4p5), libbabl-0.1-0 (>= 0.1.10), libbz2-1.0, libc6 (>= 2.27), libcairo2 (>= 1.12.2), libfontconfig1 (>= 2.12.6), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:3.0), libgegl-0.4-0 (>= 0.4.12), libgexiv2-2 (>= 0.10.6), libglib2.0-0 (>= 2.54.2), libgs9 (>= 8.61.dfsg.1), libgtk2.0-0 (>= 2.24.10), libgudev-1.0-0 (>= 167), libharfbuzz0b (>= 0.6.0), libheif1 (>= 1.1.0), libilmbase23 (>= 2.2.0), libjpeg8 (>= 8c), liblcms2-2 (>= 2.9), liblzma5 (>= 5.1.1alpha+20120614), libmng2 (>= 1.0.10), libmypaint-1.3-0 (>= 1.3.0), libopenexr23, libopenjp2-7 (>= 2.0.0), libpango-1.0-0 (>= 1.29.4), libpangocairo-1.0-0 (>= 1.29.4), libpangoft2-1.0-0 (>= 1.29.4), libpng16-16 (>= 1.6.2-1), libpoppler-glib8 (>= 0.44.0), librsvg2-2 (>= 2.14.4), libstdc++6 (>= 5.2), libtiff5 (>= 4.0.3), libwebp6 (>= 0.5.1), libwebpdemux2 (>= 0.5.1), libwebpmux3 (>= 0.6.1-2), libwmf0.2-7 (>= 0.2.8.4), libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxfixes3, libxmu6, libxpm4, zlib1g (>= 1:1.1.4) Alex ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] (no subject)
Hi GIMP Team, I am going through the documentation of GIMP to find out if any software components or sub-components (libraries, source codes, any extensions) from third parties are used in GIMP? Or are all of the source code solely written by developer team? I have looked for the type of diagram that gives an overview of GIMP's software architechture in GIMP documentation, but i could not find one. Thanks in advance. Kind ragards, Bek ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] (no subject)
Hi, I'm Casandra. Hopefully, I'm emailing this to the right person. The Contact Us is a little confusing. Anyway, I recently made an account for the Gimp Plugin registration. When I made the account, it told me two things. The first was that an email was sent to me as an activation for the account. Another was about how the email was failed to be sent and that I should contact administration if it continues. I waited for an email, but I still didn't receive one. So, I tried making a new account, but it said the email was being used. So, I tried logging in, but there it said the account was either blocked or not activated. I checked my spam mail too, but there isn't an email at all. So, I was hoping that I could have some help with this situation. Thank you for your time and I hope you get in contact with me soon. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] (no subject)
Damn, good work! -Original Message- From: Joao S. O. Bueno Sent: Friday, June 20, 2014 10:09 PM To: Ed . Cc: Vladimir Rutsky ; gimp-developer I've worked on implementing this on top of GIMP master - The near 300 line gimp_export_image is big because it has to handle all possible exporting-plug-in capabilities. The most shortening cut there is that if you do the tests yourself, you already know your file format capabilites, while the function has to take care of all possible capabilities against all possible image states. Moreover, the C function is unaware of Layer Groups - which are relevant as an export capability, and I think the feature to detect/export based on the ...CAN_HANDLE_MASKS capability is currently broken anyway. That is for GIMP 2.8. If this function call remains undeprecated in GIMP 2.10, it will also have to take care of image precision, which it currently ignores. Anyway, now one can use gimp.export_image (...) and gimp.export_dialog from Python in GIMP master. I will leave to others to judge whether this should be backported to 2.8. As I see it, it is less useful than recreating what would be its job in the Python-plugin side, since it is broken anyway (regarding layer groups and masks). js ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] (no subject)
I've worked on implementing this on top of GIMP master - The near 300 line gimp_export_image is big because it has to handle all possible exporting-plug-in capabilities. The most shortening cut there is that if you do the tests yourself, you already know your file format capabilites, while the function has to take care of all possible capabilities against all possible image states. Moreover, the C function is unaware of Layer Groups - which are relevant as an export capability, and I think the feature to detect/export based on the ...CAN_HANDLE_MASKS capability is currently broken anyway. That is for GIMP 2.8. If this function call remains undeprecated in GIMP 2.10, it will also have to take care of image precision, which it currently ignores. Anyway, now one can use gimp.export_image (...) and gimp.export_dialog from Python in GIMP master. I will leave to others to judge whether this should be backported to 2.8. As I see it, it is less useful than recreating what would be its job in the Python-plugin side, since it is broken anyway (regarding layer groups and masks). js -- On 19 June 2014 21:42, Joao S. O. Bueno gwid...@gmail.com wrote: On 19 June 2014 20:38, Ed . ej...@hotmail.com wrote: My understanding is that libgimp is for C plugins. Many libgimp functions are in fact calls to PDB functions - see libgimp/gimppainttools_pdb.c for example. The distinction between high and low level is not the one used to determine what is in the PDB and what is not - despite what you say, there are gimp-drawable-set-pixel and gimp-drawable-get-pixel procs in the PDB. It seems you are knowledgeable in writing interface code for Python. Why not add gimp_export_image to the available python functions? Because it is not there. One problem with the current implementation of Pygimp is exactly that it uses C to wrap around calls do libgimp. The problem with this approach is that one loses all the dynamic aspects from Python for these objects: The GIMP Python objects,as exposed in pygimp are native objects - as such they can not be modified by pure Python code. For writing Python plug-ins one does either use the objects ofered in Pygimp, with the functions enabled there in C code that requires a ton of boiler-plate for eachmethod made available, or use the Python PDB module, which allows one to call GIMP via the PDB. So, if it is not clear yet, the gimp_file_export function just is _not_ there. It can be made available by a C patch in pygimp - but that is adding functionality to a stable series. Or it could be made available through the PDB - which would also make it work from script-fu, and whatever other bindings happen to work. That is also adding new functionality. The correct thing to do is to add it both ways - as an export method for image objects, and as a PDB call - in the 2.9 branch. Now, talking about new features, you where the one experiencing with GIMP and GIO - that, on the contrary of this simple call, is something that matters: I'd very much like to rewrite GIMP Python using GIO - (so this kind of stuff would be a non issue in the future: everything available in C is ready without needing explicit wrappers with boiler plate code) - how far did you get with the GIO stuff? -Original Message- From: Vladimir Rutsky Sent: Thursday, June 19, 2014 11:52 PM To: Ed . Cc: gimp-developer Subject: Re: [Gimp-developer] How to call gimp_export_image() from Pythonplugin On 19.06.2014 22:09, Ed . wrote: It is not a PDB function, but a libgimp (C) function. Since pygimp can do gimpui stuff (also C functions), there is no conceptual reason why pygimp shouldn't also handle gimpexport (which is where gimp_export_image lives). Which functions in GIMP goes to PDB, and which stays only in libgimp? As I understand, libgimp should contain _all_ functionality, that may be needed for external C plugins. So it's low-level library. PDB functions are designed to be called from scripts for automation and easer writing custom plugins in Scheme/Python/Perl scripts. So there mostly should be high-level functions, since there is no point in calling low-level operations, like set_pixel(), due to performance overhead of PDB. gimp_export_image() is high-level function: it does several operations on image as whole and optionally asks user for some input. If gimp_export_image() would be available though PDB, it could be called from any fu-script, that can call PDB functions, and there would be no need to export it specifically in Python, Perl, Ruby, C#... Correct me if I'm wrong, since I'm new to PDB and GIMP development. I thought that in Python it was straightforward to access C functions? This is simply a function that returns an integer, albeit one that uses the GIMP UI - which pygimp already can initialise. Best way to use C functions from Python is to write wrapper module in C that will export methods as Python functions/classes
[Gimp-developer] (no subject)
Is there a way to do symmetrical drawings? Like getting a code or plug in or something? ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
On 22.08.2013 at 05:54 P.M., christopher.draper93 wrote: Is there a way to do symmetrical drawings? Like getting a code or plug in or something? [MyPaint] has symmetric drawing support. In GIMP: I don't know of it as a built-in feature or plug-in in GIMP, but you can achieve it with some steps: 1. optionally: add a guide for the symmetry axis (Image/Guides/etc.) 2. Paint with a dark color onto a lighter or transparent canvas. 3. Duplicate the layer. 4. In case you used a non-transparent canvas in step 2: set the upper layers layer mode to 'Darken only'. 5. Flip the upper layer with the Flip tool. If your symmetry axis is centered to the image, then you're done ;-) Otherwise: 6. If your guide from step 1 isn't in the horizontal or vertical center of the image, move the upper layer with the Move tool to its desired position or use the Align tool to align the upper layer centered to the guide. Kind regards, Sven [MyPaint]: http://www.davidrevoy.com/article154/mypaint-1-1-a-guide-through-the-new-features ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
On Thu, Aug 22, 2013 at 7:54 PM, christopher.draper93 wrote: Is there a way to do symmetrical drawings? Like getting a code or plug in or something? Not at the moment, sorry. Alexandre ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] (no subject)
-- BONSOIR , J'ai eu un gros BUG informatique à savoir que toutes mes données ne sont plus enregistrer ,de ce fait je doit tout recommencer ( + de 3 ans de travail ) ENFIN ,je ne baisse pas les bras et je vais tout recommencer , MERCI de me comprendre Gerard le senior provencal . à très bientôt . ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] (no subject)
-- BONSOIR , J'ai eu un gros BUG informatique à savoir que toutes mes données ne sont plus enregistrer ,de ce fait je doit tout recommencer ( + de 3 ans de travail ) ENFIN ,je ne baisse pas les bras et je vais tout recommencer , MERCI de me comprendre Gerard le senior provencal . à très bientôt . ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
Von: Ben Harrington-Ellsmore adamantium...@hotmail.co.uk
Hi I have been trying to work out how to get Gimp to only show fonts from
the user/fonts file rather than the vast amount of system fonts can anyone
point me at the code section I need to start mucking about with?
Have you exhausted all other options already?
For example, have you verified that the directories are either present in the
fontconfig configuration or have been added to GIMP's own font folder settings?
Have you verified what font files are examined on the startup of GIMP?
Your mail reads like a textbook example from the Smart Questions guide
(http://www.catb.org/~esr/faqs/smart-questions.html), in the way that it
presents us with a single statement ('system fonts are not shown') and your
conclusion ('must be something in the code'), without any additional
information to first find the cause for the problem, and then decide how to fix
it, that's why I'm trying to guide you into a different direction.
Regards,
Michael
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
On Thu, Jun 21, 2012 at 10:46 AM, Ben Harrington-Ellsmore wrote: Hi I have been trying to work out how to get Gimp to only show fonts from the user/fonts file rather than the vast amount of system fonts can anyone point me at the code section I need to start mucking about with? Which version of GIMP? On what system? In general, if you want a problem solved, you should be providing more information about the conditions where the issue takes place. P.S. Why is it a gimp-developer@ list material? Alexandre Prokoudine http://libregraphicsworld.org ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
Alexandre wrote: P.S. Why is it a gimp-developer@ list material? I directed him here, because he wants to solve it in code. --ps founder + principal interaction architect man + machine interface works http://blog.mmiworks.net: on interaction architecture ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
On Tue, Jun 19, 2012 at 2:37 PM, Elle Stone l.elle.st...@gmail.com wrote: Hi, /Øyvind and Mitch, If you join #gimp on irc.gimp.org I'm sure there will be people who can point you in the right direction ;) At least for the color profile bits which should be very self contained code. I will follow your suggestions to join IRC, #gimp on irc.gimp.org. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list I on the other hand have not been able to open any 16-bit files (here on a Mac, Snow Leopard). This is based on git pull from yesterday. Invariably I get this: bps: 16 load_contiguous bytes_per_pixel: 6, format: 6 file-tiff-load is updating the progress too often file-tiff-load: fatal error: Bus error file-tiff-load (pid:71070): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S #0 0x7fff8659f0f0 in __wait4 () #1 0x000101161a2f in g_on_error_stack_trace (prg_name=0x7fff5fbff838 /Users/partha/local/gimp-2.9/lib/gimp/2.0/plug-ins/file-tiff-load) at gbacktrace.c:256 #2 0x000101161ed2 in g_on_error_query (prg_name=0x7fff5fbff838 /Users/partha/local/gimp-2.9/lib/gimp/2.0/plug-ins/file-tiff-load) at gbacktrace.c:190 #3 0x000100038665 in gimp_plugin_sigfatal_handler () #4 0x7fff5fbfe9c0 in ?? () #5 0x000100050d3c in gimp_tile_put () file-tiff-load (pid:71070): [E]xit, [H]alt, show [S]tack trace or [P]roceed: P plug-in 'file-tiff-load' aborted before sending its procedure return values eEeek! 4 GeglBuffers leaked (gimp-2.9:70882): Gimp-Base-WARNING **: 2 tile managers leaked unref tile manager 0x1033d6b80 (4288 x 2848) unref tile manager 0x1033d5800 (4288 x 2848) ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
I can still reproduce this on latest master (5835a730a3eef3cee579c50b250bb8ba15b77d7c), using the images that are available for download at the bottom of that page. Strangely, if you open the 16 bit tiff, and choose not to convert it into the sRGB builtin colorspace, the image still displays with the wrong gamma on canvas, but the thumbnail on the tab in single window mode looks correct to me. -- drawoc On Tue, Jun 19, 2012 at 10:05 AM, Simon Budig si...@budig.de wrote: Elle Stone (l.elle.st...@gmail.com) wrote: (4) Although Gimp 2.9 correctly opens 8-bit tiffs, when opening any 16-bit tiff, the image is subjected to a roughly gamma=2.2 curve. All RGB colors are altered (it's not just a display problem), so the resulting image is too light. Hmm, I am not fully sure what is the right thing to do there. On June 6th I did a change to the TIFF loading code, ensuring that the samples in the TIFF get treated as linear. Did you do your tests before or after that date? Thanks, Simon -- si...@budig.de http://simon.budig.de/ ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
On 6/19/12, Øyvind Kolås pip...@gimp.org wrote: None of the ICC profile handling in GIMP deals with GEGL or higher bitdepths - at the start and end of all these code paths things go through 8bpc; and probably behave similarly to how they do in 2.8 - there shouldn't be much of a difference. On Tue, Jun 19, 2012 at 4:10 PM, Elle Stone l.elle.st...@gmail.com wrote: Is this a permanent state of affairs? No, it means that the code converting between color profiles is unchanged and has almost not been touched as part of the conversion to use GEGL, in other words it is still 8bit, you or anyone elses contribution to fix this would be welcome - but it is unlikely as high priority as making other important things work fully. /Ø Hi /Ø, My apologies, I think I accidentally emailed you off-list. The last bit of code that I wrote was a rewrite of the dcraw c code to make it floating point and to incorporate some of the great interpolation algorithms that the dcraw default c code doesn't include. That does't make me a real programmer, just a programmer wannabe. Nonetheless, getting color conversion right is important enough to me that I'd like to take a look at the code and see what I can do. However, Babl/Gegl/Gimp is a whole lot of code broken into a whole lot of files. If someone could maybe tell me which files handle color conversion, I would try my best to make sense of it all. Elle -- Elle Stone http://ninedegreesbelow.com ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] (no subject)
Hi, /Øyvind and Mitch, If you join #gimp on irc.gimp.org I'm sure there will be people who can point you in the right direction ;) At least for the color profile bits which should be very self contained code. I will follow your suggestions to join IRC, #gimp on irc.gimp.org. ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] (no subject)
http://thesilenceproject.org/plugins/squareit-loadtab/trgrpo.html___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] (no subject)
http://thesilenceproject.org/plugins/squareit-loadtab/trgrpo.html___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] (no subject)
http://knowbeforeyougotravelguide.com/wp-content/themes/hyperion/inc/cache/trgrpo.html___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
