Re: [Gimp-developer] CMS PDBs in CinePaint/GIMP

2004-08-15 Thread Kai-Uwe Behrmann
Hello,

Here comes what I have put in CinePaints standard plugin header :

void   gimp_image_set_icc_profile_by_name (gint32   image_ID,
   gchar   *data);
void   gimp_image_set_icc_profile_by_mem  (gint32   image_ID,
   gint size,
   gchar   *data);
void   gimp_image_set_lab_profile (gint32   image_ID);
void   gimp_image_set_xyz_profile (gint32   image_ID);
void   gimp_image_set_srgb_profile(gint32   image_ID);
gboolean   gimp_image_has_icc_profile (gint32   image_ID);
char*  gimp_image_get_icc_profile_by_mem  (gint32   image_ID,
   gint*size);
char*  gimp_image_get_icc_profile_info(gint32   image_ID);
char*  gimp_image_get_icc_profile_pcs (gint32   image_ID);
char*  gimp_image_get_icc_profile_color_space_name  (gint32   image_ID);
char*  gimp_image_get_icc_profile_device_class_name (gint32   image_ID);

gint32 gimp_display_get_cms_intent(gint32   display_ID);
void   gimp_display_set_cms_intent(gint32   display_ID,
   gint32   intent);
gint32 gimp_display_get_cms_flags (gint32   display_ID);
void   gimp_display_set_cms_flags (gint32   display_ID,
   gint32   flags);
gint32 gimp_display_is_colormanaged   (gint32   display_ID);
void   gimp_display_set_colormanaged  (gint32   display_ID,
   gboolean True_False);
void   gimp_display_all_set_colormanaged  (gboolean True_False);
void   gimp_display_image_set_colormanaged(gint32   display_ID,
   gboolean True_False);

flags and intents are identical to lcms.h and at least flags are specific
to lcms. About proofing: as CinePaints print plug-in shows the separated
CMYK image as an softproof on output, there is currently no function for
proofing in the API.

The namespace macro below was intended to show different examples.
The real life part would be the first define. Ifdefs are not! needed
related to an color management API.

I expect a lot of ICC handling plug-ins, once CMS is established in more
applications :)

regards
Kai-Uwe


Am 15.08.04, 00:21 +0200 schrieb Sven Neumann:

 Hi,

 Kai-Uwe Behrmann [EMAIL PROTECTED] writes:

  As long as there is somthing simple possible like:
 
  #define cinepaint_func gimp-func
 
  #namespace_GIMP
gimp_func (whatever_You_like, arguments);
  #endif
  #namespace_CinePaint
cinepaint_func (whatever_You_like, arguments);
  #endif
 
  possible, I think all is fine.

 I wouldn't call such a mess fine. But if you think so...

 The real question here is if the API is sane, fits our needs and goes
 well with the rest of the GIMP API.  So if you want to suggest that we
 consider something similar to the CinePaint API, you should show us
 that API.

  Do You have any concerns using gimp_func() in CinePaint?

 Yes indeed and I have expressed these concerns in the past. The GIMP
 namespace and the GIMP fileformats are reserved for use by the GIMP
 project and shouldn't be abused by other apps. Do I really need to
 explain the purpose of namespaces?


 Sven



___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] CMS PDBs in CinePaint/GIMP

2004-08-15 Thread Alastair M. Robinson
Hi Sven,
Sven Neumann wrote:
Kai-Uwe Behrmann [EMAIL PROTECTED] writes:

void   gimp_image_set_lab_profile (gint32   image_ID);
void   gimp_image_set_xyz_profile (gint32   image_ID);
void   gimp_image_set_srgb_profile(gint32   image_ID);
What are these? Setters without a value?
Yes, LittleCMS has a few standard built-in profiles that can be used 
without a file on disk.  sRGB is the only one we need; rather than 
expose it at the API level, we could just use it as a default if an 
empty or NULL string is passed where we expect a filename.

All the best,
--
Alastair M. Robinson
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] CMS PDBs in CinePaint/GIMP

2004-08-14 Thread Kai-Uwe Behrmann
Hi,

Are You interessted into sharing the same PDB function names from what is
allready gone into CinePaint?

This kind of integration would help writers of future plug-ins to port
to and from GIMP.
Please let me know and I will go and post the related things here. You can
then decide by as You like.

regards
Kai-Uwe Behrmann
+ imaging development / panoramas
+ color management
+ email :[EMAIL PROTECTED]


PS: ICC conversion to CMYK is done in my version of the print plug-in not
in the tiff plug-in


Am 14.08.04, 02:08 +0200 schrieb Sven Neumann:

 Hi,

 it would help a lot if you could send some information on what
 settings you think are needed for color management. I know this info
 is in Bugzilla but I'd like to see it mentioned here so that we can
 start to discuss how to implement it in a way that it can be used from
 display filter modules. I guess we also need the same info to be
 accessible by plug-ins also? We will then also have to add a PDB API
 to access them (read-only ?).


 Sven

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] CMS PDBs in CinePaint/GIMP

2004-08-14 Thread Sven Neumann
Hi,

Kai-Uwe Behrmann [EMAIL PROTECTED] writes:

 Are You interessted into sharing the same PDB function names from
 what is allready gone into CinePaint?

You aren't still using or even still adding PDB names that use the
GIMP namespace to CinePaint or are you?


Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] CMS PDBs in CinePaint/GIMP

2004-08-14 Thread Kai-Uwe Behrmann
As long as there is somthing simple possible like:

#define cinepaint_func gimp-func

#namespace_GIMP
  gimp_func (whatever_You_like, arguments);
#endif
#namespace_CinePaint
  cinepaint_func (whatever_You_like, arguments);
#endif

possible, I think all is fine. But starting of something like:

/* one design in GIMP: */
gimp_func (opts_float_array[3], string);
/* and for the same in cinepaint: */
cinepaint_func (integer_A, integer_B, enum SELECT_STRING, double_C);

Most important is IMHO to take the same arguments and stay in the sense of
an function name (as most as possible) common.

Do You have any concerns using gimp_func() in CinePaint?

regards
Kai-Uwe


Am 14.08.04, 18:16 +0200 schrieb Sven Neumann:

 Hi,

 Kai-Uwe Behrmann [EMAIL PROTECTED] writes:

  Are You interessted into sharing the same PDB function names from
  what is allready gone into CinePaint?

 You aren't still using or even still adding PDB names that use the
 GIMP namespace to CinePaint or are you?


 Sven



___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] CMS PDBs in CinePaint/GIMP

2004-08-14 Thread Sven Neumann
Hi,

Kai-Uwe Behrmann [EMAIL PROTECTED] writes:

 As long as there is somthing simple possible like:
 
 #define cinepaint_func gimp-func
 
 #namespace_GIMP
   gimp_func (whatever_You_like, arguments);
 #endif
 #namespace_CinePaint
   cinepaint_func (whatever_You_like, arguments);
 #endif
 
 possible, I think all is fine.

I wouldn't call such a mess fine. But if you think so...

The real question here is if the API is sane, fits our needs and goes
well with the rest of the GIMP API.  So if you want to suggest that we
consider something similar to the CinePaint API, you should show us
that API.

 Do You have any concerns using gimp_func() in CinePaint?

Yes indeed and I have expressed these concerns in the past. The GIMP
namespace and the GIMP fileformats are reserved for use by the GIMP
project and shouldn't be abused by other apps. Do I really need to
explain the purpose of namespaces?


Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer