[Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Alexander Rabtchevich
Hello

I compiled current git and found gimp-drawable-transform-scale became 
deprecated although it works. The proposed replacement doesn't take 
scaling algorithm  as a parameter. Is it a way to a user to select 
scaling algorithm anymore?

With respect,
Alexander Rabtchevich
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Michael Natterer
On Fri, 2011-02-11 at 11:31 +0200, Alexander Rabtchevich wrote:
 Hello
 
 I compiled current git and found gimp-drawable-transform-scale became 
 deprecated although it works. The proposed replacement doesn't take 
 scaling algorithm  as a parameter. Is it a way to a user to select 
 scaling algorithm anymore?

It's all documented.

regards,
--mitch


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Alexander Rabtchevich
Michael Natterer wrote:
 On Fri, 2011-02-11 at 11:31 +0200, Alexander Rabtchevich wrote:
 Hello

 I compiled current git and found gimp-drawable-transform-scale became
 deprecated although it works. The proposed replacement doesn't take
 scaling algorithm  as a parameter. Is it a way to a user to select
 scaling algorithm anymore?
 It's all documented.

 regards,
 --mitch


Sorry, but procedure browser only says:
This procedure scales the specified item. If a selection exists and the 
item is a drawable, the portion of the drawable which lies under the 
selection is cut from the drawable and made into a floating selection 
which is then scaled by the specified amount. The return value is the ID 
of the scaled item. If there was no selection or the item is not a 
drawable, this will be equal to the item ID supplied as input. 
Otherwise, this will be the newly created and scaled drawable.

With respect,
Alexander Rabtchevich
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Michael Natterer
On Fri, 2011-02-11 at 13:26 +0200, Alexander Rabtchevich wrote:
 Michael Natterer wrote:
  On Fri, 2011-02-11 at 11:31 +0200, Alexander Rabtchevich wrote:
  Hello
 
  I compiled current git and found gimp-drawable-transform-scale became
  deprecated although it works. The proposed replacement doesn't take
  scaling algorithm  as a parameter. Is it a way to a user to select
  scaling algorithm anymore?
  It's all documented.
 
  regards,
  --mitch
 
 
 Sorry, but procedure browser only says:
 This procedure scales the specified item. If a selection exists and the 
 item is a drawable, the portion of the drawable which lies under the 
 selection is cut from the drawable and made into a floating selection 
 which is then scaled by the specified amount. The return value is the ID 
 of the scaled item. If there was no selection or the item is not a 
 drawable, this will be equal to the item ID supplied as input. 
 Otherwise, this will be the newly created and scaled drawable.

I apologize, you are right. I apparently only added links to
the new context functions from the new selection API.

It's the new context API, e.g. gimp_context_set_interpolation().
Will add the docs after work today.

sorry,
--mitch


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Ofnuts

On 02/11/2011 01:02 PM, Alexander Rabtchevich wrote:
 I apologize, you are right. I apparently only added links to
 the new context functions from the new selection API.

 It's the new context API, e.g. gimp_context_set_interpolation().
 Will add the docs after work today.

Hmmm. What proportion of existing plug-ins working in 2.6 will have to 
be rewritten for 2.8? In my neck of the IT woods, within the same 
version backward compatibility is implied... And if a rewrite is 
necessary we will have to support both versions for quite some time 
(some people fall in love with some plug-ins and won't upgrade Gimp 
until there is a new version  of their beloved plug-in). And do it again 
when 3.0 shows up...



___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Joao S. O. Bueno
On Fri, Feb 11, 2011 at 11:13 AM, Ofnuts ofn...@laposte.net wrote:

 On 02/11/2011 01:02 PM, Alexander Rabtchevich wrote:
 I apologize, you are right. I apparently only added links to
 the new context functions from the new selection API.

 It's the new context API, e.g. gimp_context_set_interpolation().
 Will add the docs after work today.

 Hmmm. What proportion of existing plug-ins working in 2.6 will have to
 be rewritten for 2.8? In my neck of the IT woods, within the same
 version backward compatibility is implied... And if a rewrite is
 necessary we will have to support both versions for quite some time
 (some people fall in love with some plug-ins and won't upgrade Gimp
 until there is a new version  of their beloved plug-in). And do it again
 when 3.0 shows up...


Most existing plug-ins will just work in gimp 2.8 - at least in
non-layer group using images (and
most plug-ins don't care about more than the current layer/drawable,
so these will work anyway, just
not on the group, but on individual layers).

The fact that some procedures are marked as  deprecated does not
mean they will
stop working in gimp-2.8: they are still there. New plug-ins are
however expected not to use
these calls (an expectation that is strongly enforced by the fact that
the deprecated procedures have their
documentation replaced by a stub)

When the time comes to GIMP 3.0, that is another history - - chanigng
in the major version number
also means it is time to break backwards compatibility, and remove
deprecated functions. But that is not the
case for 2.8.

   js
  --




 ___
 Gimp-developer mailing list
 Gimp-developer@lists.XCF.Berkeley.EDU
 https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Øyvind Kolås
On Fri, Feb 11, 2011 at 1:13 PM, Ofnuts ofn...@laposte.net wrote:

 On 02/11/2011 01:02 PM, Alexander Rabtchevich wrote:
 I apologize, you are right. I apparently only added links to
 the new context functions from the new selection API.

 It's the new context API, e.g. gimp_context_set_interpolation().
 Will add the docs after work today.

 Hmmm. What proportion of existing plug-ins working in 2.6 will have to
 be rewritten for 2.8? In my neck of the IT woods, within the same
 version backward compatibility is implied... And if a rewrite is
 necessary we will have to support both versions for quite some time
 (some people fall in love with some plug-ins and won't upgrade Gimp
 until there is a new version  of their beloved plug-in). And do it again
 when 3.0 shows up...

But the rewriting needed for 3.0, porting to be GEGL ops, can be done
already now, and I would strongly encourage GIMP to make use of GEGL
ops more on an equal footing to GIMP plug-ins (and not be hidden in an
own menu under the GEGL tool like it is now) so that freshly developed
plug-ins can be done as GEGL ops already now and be more future proof.

/Øyvind K.
-- 
«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                     http://gegl.org/contribute.html
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Michael Natterer
On Fri, 2011-02-11 at 14:02 +0200, Alexander Rabtchevich wrote:
 No needs to apologize, it's a work in progress
 
 Another question here - is there a plugin conversion guide somewhere? I 
 tried to run wavelet-sharpen plugin, compiled for 2.7, but it fails with 
 2 messages:
 Could not execute plug-in wavelet-sharpen
 (/opt/gimp-2.7/lib/gimp/2.0/plug-ins/wavelet-sharpen)
 because it uses an obsolete version of the plug-in protocol.

All plugins are binary-compatible within the 2.x series,
the error you are seeing is because your plugin still
links to an old libgimp version installed somewhere,
and libgimp and the gimp app can only work together
within one protocol version.

Make sure your plugins find the right libgimp and
everything will be fine.

ciao,
--mitch


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Michael Natterer
On Fri, 2011-02-11 at 14:02 +0200, Alexander Rabtchevich wrote:
 No needs to apologize, it's a work in progress
 
 Another question here - is there a plugin conversion guide somewhere?

And no, the new API is still in flux, but there will be
an undeprecation guide for 2.8

ciao,
--mitch


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Joao S. O. Bueno
On Fri, Feb 11, 2011 at 12:41 PM, Øyvind Kolås pip...@gimp.org wrote:
 On Fri, Feb 11, 2011 at 1:13 PM, Ofnuts ofn...@laposte.net wrote:

 On 02/11/2011 01:02 PM, Alexander Rabtchevich wrote:
 I apologize, you are right. I apparently only added links to
 the new context functions from the new selection API.

 It's the new context API, e.g. gimp_context_set_interpolation().
 Will add the docs after work today.

 Hmmm. What proportion of existing plug-ins working in 2.6 will have to
 be rewritten for 2.8? In my neck of the IT woods, within the same
 version backward compatibility is implied... And if a rewrite is
 necessary we will have to support both versions for quite some time
 (some people fall in love with some plug-ins and won't upgrade Gimp
 until there is a new version  of their beloved plug-in). And do it again
 when 3.0 shows up...

 But the rewriting needed for 3.0, porting to be GEGL ops, can be done
 already now, and I would strongly encourage GIMP to make use of GEGL
 ops more on an equal footing to GIMP plug-ins (and not be hidden in an
 own menu under the GEGL tool like it is now) so that freshly developed
 plug-ins can be done as GEGL ops already now and be more future proof.


For example, people usually marvel at the GEGL c2g filter - and it is
completly hidden
under tools-GEGL operations.

Maybe it could be somewhat more exposed as an option in
Colors-desaturate, or filters-artistic?

  js
 --


 /Øyvind K.
 --
 «The future is already here. It's just not very evenly distributed»
                                                  -- William Gibson
 http://pippin.gimp.org/                     http://gegl.org/contribute.html
 ___
 Gimp-developer mailing list
 Gimp-developer@lists.XCF.Berkeley.EDU
 https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-item-transform-scale vs gimp-drawable-transform-scale

2011-02-11 Thread Alexander Rabtchevich
Thank you, making a script with export helped to solve it.

Michael Natterer wrote:
 On Fri, 2011-02-11 at 14:02 +0200, Alexander Rabtchevich wrote:
 No needs to apologize, it's a work in progress

 Another question here - is there a plugin conversion guide somewhere? I
 tried to run wavelet-sharpen plugin, compiled for 2.7, but it fails with
 2 messages:
 Could not execute plug-in wavelet-sharpen
 (/opt/gimp-2.7/lib/gimp/2.0/plug-ins/wavelet-sharpen)
 because it uses an obsolete version of the plug-in protocol.
 All plugins are binary-compatible within the 2.x series,
 the error you are seeing is because your plugin still
 links to an old libgimp version installed somewhere,
 and libgimp and the gimp app can only work together
 within one protocol version.

 Make sure your plugins find the right libgimp and
 everything will be fine.

 ciao,
 --mitch


With respect,
Alexander Rabtchevich
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer