mirror of https://github.com/GNOME/gimp.git
72092fbdbc
The line art imaginary segments/splines are not added when they create too small zones, unless when these are just too small ("unsignificant"). Why the original algorithm keeps such micro-zones is because there may be such zones created when several splines or segments are leaving from a same key point (and we don't necessarily won't to forbid this). Also we had cases when using very spiky brushes (for the line art) would create many zones, and such micro-zones would appear just too often (whereas with very smooth lines, they are much rarer, if not totally absent most of the time). Also it is to be noted that the original paper would call these "unsignificant" indeed, but these are definitely significant for the artists. Therefore having to "fix" the filling afterwards (with a brush for instance) kind of defeat the whole purpose of this tool. I already had code which would special-case (fill) 1-pixel zones in the end, but bigger micro zones could appear (up to 4 pixels in the current code, but this could change). Also I don't want to use the "Remove Holes" (gimp:flood) operation as I want to make sure I remove only micro-holes created by the line art closure code (not micro-holes from original line arts in particular). This code takes care of this issue by filling the micro-holes with imaginary line art pixels, which may later be potentially bucket filled when water-filling the line art. |
||
---|---|---|
.gitlab | ||
app | ||
app-tools | ||
build | ||
cursors | ||
data | ||
desktop | ||
devel-docs | ||
docs | ||
etc | ||
icons | ||
libgimp | ||
libgimpbase | ||
libgimpcolor | ||
libgimpconfig | ||
libgimpmath | ||
libgimpmodule | ||
libgimpthumb | ||
libgimpwidgets | ||
m4macros | ||
menus | ||
modules | ||
pdb | ||
plug-ins | ||
po | ||
po-libgimp | ||
po-plug-ins | ||
po-python | ||
po-script-fu | ||
po-tags | ||
po-tips | ||
po-windows-installer | ||
themes | ||
tools | ||
.dir-locals.el | ||
.gitignore | ||
.kateconfig | ||
AUTHORS | ||
COPYING | ||
ChangeLog.pre-1-0 | ||
ChangeLog.pre-1-2 | ||
ChangeLog.pre-2-0 | ||
ChangeLog.pre-2-2 | ||
ChangeLog.pre-2-4 | ||
ChangeLog.pre-2-6 | ||
ChangeLog.pre-git | ||
HACKING | ||
INSTALL.in | ||
LICENSE | ||
MAINTAINERS | ||
Makefile.am | ||
NEWS | ||
NEWS.pre-2-0 | ||
NEWS.pre-2-2 | ||
NEWS.pre-2-4 | ||
NEWS.pre-2-6 | ||
NEWS.pre-2-8 | ||
NEWS.pre-2-10 | ||
README | ||
README.i18n | ||
acinclude.m4 | ||
authors.dtd | ||
authors.xml | ||
authors.xsl | ||
authors4gimp-web.xsl | ||
autogen.sh | ||
config.h.win32 | ||
configure.ac | ||
gimp-zip.in | ||
gimp.doap | ||
gimp.pc.in | ||
gimpthumb.pc.in | ||
gimpui.pc.in |
README
------------------------------ GNU Image Manipulation Program 2.99 Development Branch ------------------------------ This is an unstable development release, an intermediate state on the way to the next stable release: GIMP 3. GIMP 2.99 may or may not do what you expect. Save your work early and often. If you want a stable version, please use GIMP 2.10 instead. If you think you found a bug in this version, please make sure that it hasn't been reported earlier and that it is not just new stuff that is still being worked on and obviously not quite finished yet. If you want to hack on GIMP, please read the file HACKING. For detailed installation instructions, see the file INSTALL. 1. Web Resources ================ GIMP's home page is at: https://www.gimp.org/ Please be sure to visit this site for information, documentation, tutorials, news, etc. All things GIMP-ish are available from there. The automated plug-in registry is located at: https://registry.gimp.org/ There you can get the latest versions of plug-ins, using a convenient forms-based interface. The latest version of GIMP can be found at: https://www.gimp.org/downloads/ 2. Mailing Lists ================ We have several mailing lists dedicated to GIMP user and development discussion. There is more info at https://www.gimp.org/mail_lists.html Links to several archives of the mailing lists are included in that page. Gimp-user-list is a mailing list dedicated to user problems, hints and tips, discussion of cool effects, etc. Gimp-developer-list is oriented to GIMP core and plug-in developers. Gimp-gui-list is for discussing about GIMP interface to improve user experience. Most people will only want to be subscribed to gimp-user-list. If you want to help develop GIMP, the gimp-developer mailing list is a good starting point; if you want to help with GUI design, the gimp-gui list is where you want to subscribe. 3. IRC ====== And finally, for the real junkies, there is an IRC channel devoted to GIMP. On GIMPNet (a private free software oriented network) there is #gimp. Many of the developers hang out there. Some of the GIMPNet servers are: irc.gimp.org:6667 irc.us.gimp.org:6667 irc.eu.gimp.org:6667 4. Customizing ============== The look of GIMP's interface can be customized like any other GTK+ app by editing files in `${XDG_CONFIG_HOME}/gtk-3.0/` (settings.ini and gtk.css in particular) or by using "themes" (ready-made customizations). Additionally, GIMP reads `${XDG_CONFIG_HOME}/GIMP/2.99/gimp.css` so you can have settings that only apply to GIMP. Included is a set of keybindings similar to those in Adobe Photoshop. You can find them in the ps-menurc file. To use them, copy this file to `${XDG_CONFIG_HOME}/GIMP/2.99/menurc`. You can also manually change the keybindings to any of your choice by editing: `${XDG_CONFIG_HOME}/GIMP/2.99/menurc`. Have fun, Spencer Kimball Peter Mattis Federico Mena Manish Singh Sven Neumann Michael Natterer Dave Neary Martin Nordholts