procyberian/gimp
2
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/gimp.git synced 2025-07-03 17:33:25 +00:00
Code Issues 1 Projects 1 Releases Packages Wiki Activity Actions
gimp/extensions/goat-exercises/goat-exercise-c.c

286 lines
9.5 KiB
C
Raw Normal View History

libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
/*
* Goat exercise plug-in by Øyvind Kolås, pippin@gimp.org
*/
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
/*
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
* This program is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 3 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
Change the license URL from http://www.gnu.org/licenses/ to https://
2018-07-11 23:27:07 +02:00
* along with this program. If not, see <https://www.gnu.org/licenses/>.
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
*/
#include "config.h"
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
libgimp: add gimp_plug_in_extension_enable() and _extension_process() Start copying all the actual wire communication to GimpPlugIn, and move the legacy versions to gimplegacy.c. This implies having the entire protocol code twice, but without any if(PLUG_IN) { plug_in_stuff(); } else { legacy_stuff(); } At the moment it is a wild mixture of old and new, but when finished the wire code in gimplegacy.c will be entirely separate from the wire code in GimpPlugIn, which will make it easy to g_assert() that only one API is used by a plug-in.
2019-08-02 11:06:48 +02:00
#define GIMP_DISABLE_COMPAR_CRUFT
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
#include <libgimp/gimp.h>
plug-ins: register an icon for goat-exercise
2019-07-30 19:25:06 +02:00
#include <libgimp/gimpui.h>
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
#include "libgimp/stdplugins-intl.h"
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
plug-ins: rename the C goat exercise to goat-exercise-c. Makes for consistent naming of the different demo code we have there.
2019-08-09 15:41:42 +02:00
#define PLUG_IN_BINARY "goat-exercise-c"
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
#define PLUG_IN_SOURCE PLUG_IN_BINARY ".c"
plug-ins: rename the C goat exercise to goat-exercise-c. Makes for consistent naming of the different demo code we have there.
2019-08-09 15:41:42 +02:00
#define PLUG_IN_PROC "plug-in-goat-exercise-c"
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
#define PLUG_IN_ROLE "goat-exercise-c"
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
extensions: update the remote URI for the up-to-date source code. When moving the Goat Exercise plug-ins as extensions, I forgot to update the remote URI which is opened when clicking the "Source" button.
2020-10-17 19:42:11 +02:00
#define GOAT_URI "https://gitlab.gnome.org/GNOME/gimp/blob/master/extensions/goat-exercises/goat-exercise-c.c"
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
typedef struct _Goat Goat;
typedef struct _GoatClass GoatClass;
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
struct _Goat
{
plug-ins: rename the C goat exercise to goat-exercise-c. Makes for consistent naming of the different demo code we have there.
2019-08-09 15:41:42 +02:00
GimpPlugIn parent_instance;
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
};
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
struct _GoatClass
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
{
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
GimpPlugInClass parent_class;
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
};
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
/* Declare local functions.
*/
#define GOAT_TYPE (goat_get_type ())
#define GOAT (obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), GOAT_TYPE, Goat))
GType goat_get_type (void) G_GNUC_CONST;
libgimp: change the return values of GimpPlugIn::init_procedures() and ::query_procedures() to a GList* of strings.
2019-08-02 19:10:13 +02:00
static GList * goat_query_procedures (GimpPlugIn *plug_in);
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
static GimpProcedure * goat_create_procedure (GimpPlugIn *plug_in,
const gchar *name);
static GimpValueArray * goat_run (GimpProcedure *procedure,
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
GimpRunMode run_mode,
plug-ins: C goat-exercise now ported to new GimpImage/GimpDrawable. You'll notice that with the new class when used together with the new GimpPlugIn API, it is not needed to allocate/destroy anymore the GimpImage/GimpDrawable. These can be directly the parameters.
2019-08-13 18:01:03 +02:00
GimpImage *image,
extensions: update the 5 goat-exercise extensions to multi-drawable API.
2021-04-06 01:55:52 +02:00
GimpDrawable **drawables,
plug-ins: port goat-exercise to gimp_image_procedure_new2() Not yet porting to GimpProcedureDialog because there's no settings to import/export, so it would add several unnecessary buttons.
2023-07-27 18:37:23 +00:00
GimpProcedureConfig *config,
libgimp: add run_data and run_data_destroy parameters to procedure_new() so bindings work properly. Change plug-ins accordingly.
2019-08-01 22:45:49 +02:00
gpointer run_data);
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
G_DEFINE_TYPE (Goat, goat, GIMP_TYPE_PLUG_IN)
GIMP_MAIN (GOAT_TYPE)
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
static void
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
goat_class_init (GoatClass *klass)
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
{
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
GimpPlugInClass *plug_in_class = GIMP_PLUG_IN_CLASS (klass);
plug_in_class->query_procedures = goat_query_procedures;
plug_in_class->create_procedure = goat_create_procedure;
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
}
static void
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
goat_init (Goat *goat)
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
{
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
}
libgimp: change the return values of GimpPlugIn::init_procedures() and ::query_procedures() to a GList* of strings.
2019-08-02 19:10:13 +02:00
static GList *
libgimp, plug-ins: remove n_procedures from (init|query)_procedures(). The way currently implemented plug-ins are, they are already NULL-terminating the returned arrays. Since a procedure name cannot be NULL itself by definition, defining the array length by a terminal NULL is enough. There is no need to also add a n_procedures parameters which is just one more possible bug source, even more as we were already expecting the NULL termination by using g_strfreev() to free the memory. Anyway a length parameter does not bring any advantage since a plug-in can still "lie" about its array size (just as it can forget to NULL-terminate it) and when this happens, the plug-in will segfault. That's it, it's just a plug-in programming error. Last but not least, some binding seem to have issues with returned array setting an (out) parameter as the length. In pygobject at least, the length parameter doesn't disappear and we end up with this ugly signature: > In [3]: Gimp.PlugIn.do_query_procedures.__doc__ > Out[3]: 'query_procedures(self) -> list, n_procedures:int' See bug report pygobject#352. To avoid this, we should either set both the array and the length as (out) parameters or just set the returned array as NULL-terminated (which is the solution I chose).
2019-08-02 13:36:11 +02:00
goat_query_procedures (GimpPlugIn *plug_in)
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
{
libgimp: change the return values of GimpPlugIn::init_procedures() and ::query_procedures() to a GList* of strings.
2019-08-02 19:10:13 +02:00
return g_list_append (NULL, g_strdup (PLUG_IN_PROC));
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
}
static GimpProcedure *
goat_create_procedure (GimpPlugIn *plug_in,
const gchar *name)
{
GimpProcedure *procedure = NULL;
if (! strcmp (name, PLUG_IN_PROC))
{
libgimp, plug-ins, extensions: gimp_image_procedure_new2() renamed gimp_image_procedure_new().
2023-10-01 18:23:57 +02:00
procedure = gimp_image_procedure_new (plug_in, name,
GIMP_PDB_PROC_TYPE_PLUGIN,
goat_run, NULL, NULL);
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
gimp_procedure_set_image_types (procedure, "*");
extensions: update the 5 goat-exercise extensions to multi-drawable API.
2021-04-06 01:55:52 +02:00
gimp_procedure_set_sensitivity_mask (procedure,
GIMP_PROCEDURE_SENSITIVE_DRAWABLE);
libgimp: reorder functions and members of GimpProcedure to make more sense, as long as the file has little git history.
2019-08-05 23:01:25 +02:00
extensions, plug-ins: fixing CamelCase on the "Plug-In Examples" items. First of all: sorry to all translators who started working on these new strings! We use CamelCase for our titles, and in particular "Plug-In" is capitalized with 'I'. Furthermore, let's use understandable titles like "Plug-In Example in C" and not just "In C", because while the short title works OK in the menu, it makes for very broken action names in non-contextual parts of the software, such as the action search. Note that we in fact have a concept of short label for actions since commit 89772351c9. I added support for it to GEGL actions (cf. commit 6dc5f6792e), and to a few core actions (e.g. commit ea1205f094). Unfortunately I don't think I added an API yet for short label in plug-ins. Maybe I'll add it soon. But for now, if we have to have a single label, it should be long, so that it works in every situation. P.S.: not sure if it's useful to keep documentation strings just repeating the title, but for now, let's leave them.
2024-08-10 23:20:10 +02:00
gimp_procedure_set_menu_label (procedure, _("Plug-In Example in _C"));
plug-ins: port many plug-ins from GimpProcedure to GimpImageProcedure Also move the call to set_icon_name() after set_menu_label(), all ported plug-ins should look the same so we are a good example for copy and paste ;)
2019-08-18 13:45:58 +02:00
gimp_procedure_set_icon_name (procedure, GIMP_ICON_GEGL);
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
gimp_procedure_add_menu_path (procedure,
extensions, plug-ins: fixing CamelCase on the "Plug-In Examples" items. First of all: sorry to all translators who started working on these new strings! We use CamelCase for our titles, and in particular "Plug-In" is capitalized with 'I'. Furthermore, let's use understandable titles like "Plug-In Example in C" and not just "In C", because while the short title works OK in the menu, it makes for very broken action names in non-contextual parts of the software, such as the action search. Note that we in fact have a concept of short label for actions since commit 89772351c9. I added support for it to GEGL actions (cf. commit 6dc5f6792e), and to a few core actions (e.g. commit ea1205f094). Unfortunately I don't think I added an API yet for short label in plug-ins. Maybe I'll add it soon. But for now, if we have to have a single label, it should be long, so that it works in every situation. P.S.: not sure if it's useful to keep documentation strings just repeating the title, but for now, let's leave them.
2024-08-10 23:20:10 +02:00
"<Image>/Filters/Development/Plug-In Examples/");
libgimp: add gimp_procedure_set_menu_label() and _set_documentation() which replace _set_strings(). Add more docs.
2019-08-02 00:56:00 +02:00
gimp_procedure_set_documentation (procedure,
GUI: Rename menu Filters>Development>Goat exercises => Plug-in Examples The old menu label was confusing to users. Remove translatable strings having joke "goat" so translators not confused. Move the goat plugins to the menu. The items under the menu should all be example plugins. The menu is in a release. Test plugins should not be in this menu. Test plugins should not ship in a stable release. !!! Note that 2.10 does not ship with example plugins. If we don't want 3.0 to ship stable build with example plugins, then the meson.build for goat-exercises needs to change and the menu removed entirely in menus/image-menu.ui.in.in.
2024-04-22 15:32:34 -04:00
_("Plug-in example in C"),
_("Plug-in example in C"),
libgimp: add gimp_procedure_set_menu_label() and _set_documentation() which replace _set_strings(). Add more docs.
2019-08-02 00:56:00 +02:00
PLUG_IN_PROC);
libgimp: add gimp_procedure_set_attribution() Also rename "author" to "authors" and add some docs.
2019-08-02 00:35:17 +02:00
gimp_procedure_set_attribution (procedure,
"Øyvind Kolås <pippin@gimp.org>",
"Øyvind Kolås <pippin@gimp.org>",
menus, plug-ins: move script development related plug-ins in a... "Development" submenu. Also get rid of the "Languages" placeholder.
2019-08-07 20:38:53 +02:00
"21 march 2012");
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
}
return procedure;
}
static GimpValueArray *
goat_run (GimpProcedure *procedure,
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
GimpRunMode run_mode,
plug-ins: C goat-exercise now ported to new GimpImage/GimpDrawable. You'll notice that with the new class when used together with the new GimpPlugIn API, it is not needed to allocate/destroy anymore the GimpImage/GimpDrawable. These can be directly the parameters.
2019-08-13 18:01:03 +02:00
GimpImage *image,
extensions: update the 5 goat-exercise extensions to multi-drawable API.
2021-04-06 01:55:52 +02:00
GimpDrawable **drawables,
plug-ins: port goat-exercise to gimp_image_procedure_new2() Not yet porting to GimpProcedureDialog because there's no settings to import/export, so it would add several unnecessary buttons.
2023-07-27 18:37:23 +00:00
GimpProcedureConfig *config,
libgimp: add run_data and run_data_destroy parameters to procedure_new() so bindings work properly. Change plug-ins accordingly.
2019-08-01 22:45:49 +02:00
gpointer run_data)
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
{
extensions: update the 5 goat-exercise extensions to multi-drawable API.
2021-04-06 01:55:52 +02:00
GimpDrawable *drawable;
GimpPDBStatusType status = GIMP_PDB_SUCCESS;
gint x, y, width, height;
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
extensions, libgimp, plug-ins: remove n_drawables arg from GimpImageProcedure's… … run() function. This is more consistent with recent changes in PDB, and now the drawables argument is NULL-terminated.
2024-10-28 12:16:13 +01:00
if (gimp_core_object_array_get_length ((GObject **) drawables) != 1)
extensions: update the 5 goat-exercise extensions to multi-drawable API.
2021-04-06 01:55:52 +02:00
{
GError *error = NULL;
g_set_error (&error, GIMP_PLUG_IN_ERROR, 0,
_("Procedure '%s' only works with one drawable."),
PLUG_IN_PROC);
return gimp_procedure_new_return_values (procedure,
GIMP_PDB_CALLING_ERROR,
error);
}
else
{
drawable = drawables[0];
}
Fix various typos Found via `codespell` (v1.17.0.dev0)
2019-09-21 17:10:46 +00:00
/* In interactive mode, display a dialog to advertise the exercise. */
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
if (run_mode == GIMP_RUN_INTERACTIVE)
{
GtkTextBuffer *buffer;
GtkWidget *dialog;
GtkWidget *box;
GtkWidget *widget;
GtkWidget *scrolled;
GFile *file;
GFileInputStream *input;
gchar *head_text;
gchar *path;
GdkGeometry geometry;
gchar source_text[4096];
gssize read;
gint response;
libgimp, plug-ins: remove the "preview" parameter from gimp_ui_init() It's dead since a looong time.
2019-09-20 19:39:00 +02:00
gimp_ui_init (PLUG_IN_BINARY);
extensions, plug-ins: fixing CamelCase on the "Plug-In Examples" items. First of all: sorry to all translators who started working on these new strings! We use CamelCase for our titles, and in particular "Plug-In" is capitalized with 'I'. Furthermore, let's use understandable titles like "Plug-In Example in C" and not just "In C", because while the short title works OK in the menu, it makes for very broken action names in non-contextual parts of the software, such as the action search. Note that we in fact have a concept of short label for actions since commit 89772351c9. I added support for it to GEGL actions (cf. commit 6dc5f6792e), and to a few core actions (e.g. commit ea1205f094). Unfortunately I don't think I added an API yet for short label in plug-ins. Maybe I'll add it soon. But for now, if we have to have a single label, it should be long, so that it works in every situation. P.S.: not sure if it's useful to keep documentation strings just repeating the title, but for now, let's leave them.
2024-08-10 23:20:10 +02:00
dialog = gimp_dialog_new (_("Plug-In Example in C"), PLUG_IN_ROLE,
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
NULL, GTK_DIALOG_USE_HEADER_BAR,
gimp_standard_help_func, PLUG_IN_PROC,
_("_Cancel"), GTK_RESPONSE_CANCEL,
_("_Source"), GTK_RESPONSE_APPLY,
_("_Run"), GTK_RESPONSE_OK,
NULL);
geometry.min_aspect = 0.5;
geometry.max_aspect = 1.0;
gtk_window_set_geometry_hints (GTK_WINDOW (dialog), NULL,
&geometry, GDK_HINT_ASPECT);
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
box = gtk_box_new (GTK_ORIENTATION_VERTICAL, 12);
gtk_container_set_border_width (GTK_CONTAINER (box), 12);
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
gtk_container_add (GTK_CONTAINER (gtk_dialog_get_content_area (GTK_DIALOG (dialog))),
box);
gtk_widget_show (box);
head_text = g_strdup_printf (_("This plug-in is an exercise in '%s' "
plug-ins: rename the C goat exercise to goat-exercise-c. Makes for consistent naming of the different demo code we have there.
2019-08-09 15:41:42 +02:00
"to demo plug-in creation.\n"
"Check out the last version "
"of the source code online by "
"clicking the \"Source\" button."),
"C");
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
widget = gtk_label_new (head_text);
g_free (head_text);
gtk_box_pack_start (GTK_BOX (box), widget, FALSE, FALSE, 1);
gtk_widget_show (widget);
scrolled = gtk_scrolled_window_new (NULL, NULL);
gtk_box_pack_start (GTK_BOX (box), scrolled, TRUE, TRUE, 1);
gtk_widget_set_vexpand (GTK_WIDGET (scrolled), TRUE);
gtk_widget_show (scrolled);
plug-ins, extension: goat-exercises becomes a GIMP extension. This is an extension containing a few demo plug-ins. This is good to demonstrate the extension format. It will also allow to disable these plug-ins (if at some point, one doesn't want to show these demo plug-ins anymore). And finally it deals with the fact that our plug-in code is stupid, as it just tries to find the first executable with the same name (minus extension) as the plug-in folder. This doesn't go well on Windows, where the permission system is non-existent. So our code just ends up trying to run the first file with a similar name in a plug-in folder. As the C goat-exercise contains both an exe and the C source (and the system probably returns files in alphabetic order), GIMP under Windows tries to run the C source instead of the executable (this obviously doesn't go well). We could try to do more complex logics, like not aborting if the first file run fails and try the next one in the plug-in folder. Or maybe just rename the C file to another name. But any of these is just in the end the proof that our plug-in discovery right now is just bogus. The extension system is explicit, not based on randomly trying out files. Plug-ins entry points are explicitly listed in the metadata manifest.
2020-10-08 13:58:19 +02:00
path = g_build_filename (gimp_plug_in_directory (), "extensions",
"org.gimp.extension.goat-exercises", PLUG_IN_SOURCE,
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
NULL);
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
file = g_file_new_for_path (path);
g_free (path);
widget = gtk_text_view_new ();
gtk_text_view_set_wrap_mode (GTK_TEXT_VIEW (widget), GTK_WRAP_WORD);
gtk_text_view_set_editable (GTK_TEXT_VIEW (widget), FALSE);
buffer = gtk_text_view_get_buffer (GTK_TEXT_VIEW (widget));
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
input = g_file_read (file, NULL, NULL);
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
while ((read = g_input_stream_read (G_INPUT_STREAM (input),
source_text, 4096, NULL, NULL)) &&
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
read != -1)
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
{
gtk_text_buffer_insert_at_cursor (buffer, source_text, read);
}
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
g_object_unref (file);
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
gtk_container_add (GTK_CONTAINER (scrolled), widget);
gtk_widget_show (widget);
while ((response = gimp_dialog_run (GIMP_DIALOG (dialog))))
{
if (response == GTK_RESPONSE_OK)
{
gtk_widget_destroy (dialog);
break;
}
else if (response == GTK_RESPONSE_APPLY)
{
/* Show the code. */
g_app_info_launch_default_for_uri (GOAT_URI, NULL, NULL);
continue;
}
else /* CANCEL, CLOSE, DELETE_EVENT */
{
gtk_widget_destroy (dialog);
plug-ins: port goat-exercise-c to GimpFileProcedure and fix loading of the plug-in source code into the text view. Also, ancountering a zero-sized selection is not an error, but simply a successful nop.
2019-08-18 13:14:27 +02:00
return gimp_procedure_new_return_values (procedure,
GIMP_PDB_CANCEL,
NULL);
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
}
}
}
plug-ins: C goat-exercise now ported to new GimpImage/GimpDrawable. You'll notice that with the new class when used together with the new GimpPlugIn API, it is not needed to allocate/destroy anymore the GimpImage/GimpDrawable. These can be directly the parameters.
2019-08-13 18:01:03 +02:00
if (gimp_drawable_mask_intersect (drawable, &x, &y, &width, &height))
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
{
GeglBuffer *buffer;
GeglBuffer *shadow_buffer;
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
gegl_init (NULL, NULL);
plug-ins: C goat-exercise now ported to new GimpImage/GimpDrawable. You'll notice that with the new class when used together with the new GimpPlugIn API, it is not needed to allocate/destroy anymore the GimpImage/GimpDrawable. These can be directly the parameters.
2019-08-13 18:01:03 +02:00
buffer = gimp_drawable_get_buffer (drawable);
shadow_buffer = gimp_drawable_get_shadow_buffer (drawable);
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
gegl_render_op (buffer, shadow_buffer, "gegl:invert", NULL);
g_object_unref (shadow_buffer); /* flushes the shadow tiles */
g_object_unref (buffer);
plug-ins: C goat-exercise now ported to new GimpImage/GimpDrawable. You'll notice that with the new class when used together with the new GimpPlugIn API, it is not needed to allocate/destroy anymore the GimpImage/GimpDrawable. These can be directly the parameters.
2019-08-13 18:01:03 +02:00
gimp_drawable_merge_shadow (drawable, TRUE);
gimp_drawable_update (drawable, x, y, width, height);
plug-ins: clean up goat-exercise.c so it is a better example
2012-03-22 13:04:50 +01:00
gimp_displays_flush ();
plug-ins: goat-exercise improved to show a dialog. This just adds a dialog before running the actual processing of data. - it also shows what the run-mode is for; - the purpose of the plug-in becomes explicit (plug-in creation documentation); - it shows some GTK+ code too. - last but not least, the code is actually shown for people to study, with a button to access the last version of the code on gitlab. This makes the plug-in a lot more useful and understandable this way. Other exercise plug-ins in other languages will have to do the same thing.
2019-08-07 16:13:49 +02:00
gegl_exit ();
}
app, libgimp, libgimpbase: plug-in and PDB protocol refactoring part two - Change the wire protocol's GPProcInstall to transmit the entire information needed for constructing all GParamSpecs we use, don't use GimpPDBArgType in GPProcInstall but an enum private to the wire protocol plus the GParamSpec's GType name. Bump the wire protocol version. - Add gimpgpparamspecs.[ch] in both app/plug-in/ and libgimp/ which take care of converting between GPParamDef and GParamSpec. They share code as far as possible. - Change pluginrc writing and parsing to re-use GPParamDef and the utility functions from gimpgpparamspecs. - Remove gimp_pdb_compat_param_spec() from app/pdb/gimp-pdb-compat.[ch], the entire core uses proper GParamSpecs from the wire protocol now, the whole file will follow down the drain once we use a GValue representation on the wire too. - In gimp_plug_in_handle_proc_install(), change the "run-mode" parameter to a GParamSpecEnum(GIMP_TYPE_RUN_MODE) (if it is not already an enum). and change all places in app/ to treat it as an enum value. - plug-ins: fix cml-explorer to register correctly, a typo in "run-mode" was never noticed until now. - Add gimpgpcompat.[ch] in libgimp to deal with all the transforms between old-style wire communication and using GParamSpec and GValue, it contains some functions that are subject to change or even removal in the next steps. - Change the libgimp GimpProcedure and GimpPlugIn in many ways to be able to actually install procedures the new way. - plug-ins: change goat-exercise to completely use the new GimpPlugIn and GimpProcedure API, look here to see how plug-ins will look in the future, of course subject to change until this is finished. - Next: changing GPParam to transmit all information about a GValue.
2019-07-27 16:37:55 +02:00
return gimp_procedure_new_return_values (procedure, status, NULL);
libgimp: add a GeglBuffer backend for plug-ins Also added an API to get GeglBuffers for drawables, you choose whether you get.
2012-03-22 00:10:43 +00:00
}
Reference in a new issue Copy permalink