mirror of https://github.com/GNOME/gimp.git
1a9c470b82
The way we were creating a GimpData identifier was simply wrong, because it was based on the assumption that the source file uniquely identifies a GimpData (cf. gimp_tagged_get_identifier() which clearly says that the returned string must uniquely identify this data). The very simple counter-examples for why this is a mistake to consider a data file to be a good unique identifier are collection files. For instance, TTC files (TrueType Collection) contain multiple fonts. Instead I am adding the concept of "collection" with the assumption that **within a given collection**, data names are unique (I do hope this to be and stay true). So I add gimp_data_get_identifiers() and gimp_data_identify() to get identifiers and check for identity. The collection will use the old implementation of gimp_data_get_identifier() because it is quite nice to have paths relative to data and config directories (it allows some cases of data relocation without losing data identification). The new implementation to compute a GimpTagged identifier on the other hand will construct a string from the quality of being internal or not, the data name and its collection. |
||
---|---|---|
.gitlab | ||
app | ||
app-tools | ||
build | ||
cursors | ||
data | ||
desktop | ||
devel-docs | ||
docs | ||
etc | ||
extensions | ||
icons | ||
libgimp | ||
libgimpbase | ||
libgimpcolor | ||
libgimpconfig | ||
libgimpmath | ||
libgimpmodule | ||
libgimpthumb | ||
libgimpwidgets | ||
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 | ||
.clang-format | ||
.dir-locals.el | ||
.gitignore | ||
.gitlab-ci.yml | ||
.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 | ||
INSTALL.in | ||
LICENSE | ||
MAINTAINERS | ||
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 | ||
authors.dtd | ||
authors.xml | ||
authors.xsl | ||
authors4gimp-web.xsl | ||
gimp.doap | ||
gimp.pc.in | ||
gimpthumb.pc.in | ||
gimpui.pc.in | ||
meson.build | ||
meson.make | ||
meson_dist_script.sh | ||
meson_options.txt |
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.0. 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 devel-docs/README.md. 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 latest version of GIMP can be found at: https://www.gimp.org/downloads/ 2. Contributing =============== GIMP source code can be found at: https://gitlab.gnome.org/GNOME/gimp/ Resources for contributors: https://developer.gimp.org/ In particular, you may want to look in the "Core Development" section. Some articles of particular interest for newcomers could be: * Setting up your developer environment: https://developer.gimp.org/core/setup/ * GIMP Coding Style: https://developer.gimp.org/core/coding_style/ * Submit your first patch: https://developer.gimp.org/core/submit-patch/ 3. Discussion Channels ====================== We have several discussion channels dedicated to GIMP user and development discussion. There is more info at: https://www.gimp.org/discuss.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. Other discussion channels can be listed on this page when they are moderated by a team member, such as forums. Finally, for the real junkies, there are IRC channels 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. You can also manually change the keybindings to any of your choice by editing: `${XDG_CONFIG_HOME}/GIMP/2.99/shortcutsrc`. Have fun, Spencer Kimball Peter Mattis Federico Mena Manish Singh Sven Neumann Michael Natterer Dave Neary Martin Nordholts Jehan