[Gimp-developer] File location for plug-in auxiliary files

2001-02-23 Thread Ernst Lippe
The installed version of a plug-in can contain other files than just the executable, e.g. help files and locale files. When the user has root permissions these files can be installed on the standard locations for the system, but where should these files be installed when that is not the case? The

Re: [Gimp-developer] Re: Layers, dialogs and other bits of love on Valentines Day

2001-02-23 Thread Ernst Lippe
Marc Lehmann wrote: I'd like to remind people that corba is not the only way to go, as there is also dco and especially MCOP (which was designed for realtime and multimedia applications). While CORBA might indeed be the best choice, it mustn't be choosen just because it has more letters ;-

Re: [Gimp-developer] [patch] unbelievable speedup for bumpmap...

2001-04-06 Thread Ernst Lippe
The speedup that you see is probably mainly caused by better caching. There is a bug in the tile cache size for the plugin. The cache is under most circumstances too small and this means that every requested tile is not in the cache and must be transmitted from the main gimp process (SLOW).

Re: [Gimp-developer] [patch] Major speedup for whirlpinch plugin

2001-04-06 Thread Ernst Lippe
I think this is yet another tile-cache problem. Georg Acher wrote: On Thu, Apr 05, 2001 at 12:45:52PM -0500, Kelly Martin wrote: Hm, it does not. The issue with whirlpinch is that there's only a weak locality relationship between destionation pixels (which are iterated across the

Re: [Gimp-developer] [patch] unbelievable speedup for bumpmap...

2001-04-06 Thread Ernst Lippe
Kelly Martin wrote: If the algorithm is pixel-by-pixel (each output pixel depends only on exactly one input pixel from each region being iterated over, and those regions are all the same size) there is absolutely no excuse not to use the pixel region iterator, which will automagically

[Gimp-developer] Preview requirements

2003-02-26 Thread Ernst Lippe
, Ernst Lippe [EMAIL PROTECTED] Maurits Rijk [EMAIL PROTECTED] Requirements for a GIMP plug-in preview widget == This document gives a possible list of requirements for a preview widget that can be used by GIMP plug-ins. This is the version 1.0

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Ernst Lippe
On 26 Feb 2003 14:24:17 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: There are two possible GUI styles: dragging in the preview and using scrollbars. These could also be combined. Open issue: Scrollbars make the widget visually bigger

Re: [Gimp-developer] Preview requirements

2003-02-27 Thread Ernst Lippe
On Thu, 27 Feb 2003 00:49:50 +0100 Branko Collin [EMAIL PROTECTED] wrote: Sometimes, a rendering algorithm is very slow. I know this all too well. A user should be able to switch off the automatic rendering of a preview. I don't think this is part of the preview widget. It calls the plug-in

Re: [Gimp-developer] Preview requirements

2003-02-28 Thread Ernst Lippe
On 26 Feb 2003 17:29:37 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: The point is the following. In the current implementation the preview widget consists of the following components from top to bottom: the image, the progress bar and the zoom

Re: [Gimp-developer] Preview requirements

2003-03-02 Thread Ernst Lippe
On 01 Mar 2003 17:39:56 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: A set of previews that you want to synchronize is an example of a constraint based system where you want to solve a set of constraints among multiple objects. The naive

Re: [Gimp-developer] Preview requirements

2003-03-02 Thread Ernst Lippe
On Sat, 01 Mar 2003 12:46:57 +0100 Michael Natterer [EMAIL PROTECTED] wrote: Ernst Lippe [EMAIL PROTECTED] writes: On 26 Feb 2003 17:29:37 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: The point is the following. In the current

Re: [Gimp-developer] caching considerations in gegl

2003-03-12 Thread Ernst Lippe
On Tue, 11 Mar 2003 19:05:03 +0100 Raphaƫl Quinet [EMAIL PROTECTED] wrote: On Tue, 11 Mar 2003 18:20:34 +0100, Ernst Lippe [EMAIL PROTECTED] wrote: So don't do that, then! ;-) Nobody should rely on unspecified behavior. But how should an end-user know that this is unspecied behavior? I

Re: [Gimp-developer] Re: caching considerations in gegl

2003-03-12 Thread Ernst Lippe
-multiplied alpha: loss of precision. When you're using a single byte per color that could be a serious problem. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

[Gimp-developer] New version of the preview requirements

2003-03-19 Thread Ernst Lippe
that supports all the requirements in the list (writing requirements after you've implemented a system is a perfect way to satisfy all system requirements). At the moment we are still working on it, but we hope to publish the API real soon now. greetings, Ernst Lippe [EMAIL PROTECTED] Requirements

Re: [Gimp-developer] New version of the preview requirements

2003-03-19 Thread Ernst Lippe
On 19 Mar 2003 18:47:11 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: At the moment we have an implementation that supports all the requirements in the list (writing requirements after you've implemented a system is a perfect way to satisfy

[Gimp-developer] Plug-in preview API proposal

2003-03-31 Thread Ernst Lippe
is left of it after the discussion) for the final documentation I also welcome minor comments such as spelling mistakes, grammar corrections, coding errors and such. greetings, Ernst Lippe [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED

Re: [Gimp-developer] Plug-in preview API proposal

2003-03-31 Thread Ernst Lippe
On Mon, 31 Mar 2003 19:58:29 +0200 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: As promised here is my API proposal for a plug-in preview widget. You can find it at http://refocus.sourceforge.net/preview. Please examine it critically, this should

Re: [Gimp-developer] Plug-in preview API proposal

2003-03-31 Thread Ernst Lippe
shows a small part of the image at its real size. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Plug-in preview API proposal

2003-03-31 Thread Ernst Lippe
On Mon, 31 Mar 2003 20:17:51 +0200 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: As promised here is my API proposal for a plug-in preview widget. You can find it at http://refocus.sourceforge.net/preview. In the section Design in Calling the render

Re: [Gimp-developer] Plug-in preview API proposal

2003-03-31 Thread Ernst Lippe
On Mon, 31 Mar 2003 22:50:00 +0200 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: P.S. Of course the most logical solution is to change the name of the core widget. My widget is derived from Shawn Amundson's GimpPreview widget that was written in 1998

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-01 Thread Ernst Lippe
On Tue, 01 Apr 2003 13:59:21 +0200 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: The only way to avoid this overhead is to make interface more complicated, analogous to the GimpPixelRegions, there should be an _init interface that the preview uses

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-01 Thread Ernst Lippe
is a preliminary version of the final results. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-02 Thread Ernst Lippe
in and use a large preview it can be much bigger than the original image. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-02 Thread Ernst Lippe
Even though I fully agree that the only serious problem in my API proposal is the name of the widget, I'd really like to get more input from more people about my API proposal. Especially, I would like to hear remarks from other plug-in developers, because they are after all the intended audience

[Gimp-developer] Preview widget name

2003-04-02 Thread Ernst Lippe
My Webster's lists prevue as a synonym for preview (to me this appears to be the original French root of the word). Does GimpPrevue sound very weird for native English speakers? greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-02 Thread Ernst Lippe
On Thu, 03 Apr 2003 02:15:42 +0200 David Necas (Yeti) [EMAIL PROTECTED] wrote: On Thu, Apr 03, 2003 at 01:15:31AM +0200, Ernst Lippe wrote: P.S. I just modified my preview so that the re-entrancy problem has been eliminated. Excuse me, but which reentrancy problem has been eliminated

Re: [Gimp-developer] Preview widget name

2003-04-02 Thread Ernst Lippe
On Wed, 02 Apr 2003 16:05:52 -0800 Jeshua Lacock [EMAIL PROTECTED] wrote: On Wednesday, April 2, 2003, at 03:41 PM, Kevin Myers wrote: Personally I don't think that it sounds too bad at all, especially considering the lack of other decent alternatives suggested so far... Hello Kevin,

Re: [Gimp-developer] Preview widget name

2003-04-03 Thread Ernst Lippe
On Thu, 03 Apr 2003 02:00:22 +0200 Branko Collin [EMAIL PROTECTED] wrote: What do the two different GimpPreviews do? If they are so alike, why are there two different versions? Please explain it to me as if I did not understand programming at all (which I don't, so it will be very easy for

Re: [Gimp-developer] Preview widget name

2003-04-03 Thread Ernst Lippe
On Fri, 04 Apr 2003 00:05:47 +0200 Branko Collin [EMAIL PROTECTED] wrote: Perhaps you two are using different meanings for 'amateur': one being 'unpaid', the other 'low-quality'. Of course, in the old days, amateur meant 'noble', 'high-quality', because an amateur was something who did

[Gimp-developer] The first official release of the new GimpPreviewwidget

2003-06-11 Thread Ernst Lippe
, I would like to encourage everyone, especially all plug-in developers, to examine it critically. At the moment there is no installed user-base and it should be fairly easy to change things. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL

Re: [Gimp-developer] The first official release of the newGimpPreview widget

2003-06-11 Thread Ernst Lippe
On Wed, 11 Jun 2003 13:45:20 +0100 Adam D. Moss [EMAIL PROTECTED] wrote: Ernst Lippe wrote: After an intolerable long wait, I just released the first official version of the new GimpPreview plug-in widget. You can find it at http://refocus.sourceforge.net/preview;. I've given

Re: [Gimp-developer] Re: Blur filter

2003-06-21 Thread Ernst Lippe
is a bit too convoluted, but I think that it contains some important points. Feel free to ask when you have any problems. greetings, Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: Blur filter

2003-06-25 Thread Ernst Lippe
in the corresponding Fourier coeficients of the blurred image B. So even very small changes in B will have a great impact on the least square solution I=D(B). In practice this means that in general you don't want to use the true least square solution because it is highly unstable. greetings, Ernst Lippe

Re: [Gimp-developer] Re: [CinePaint-dev] GIMP/CinePaint fileincompatibility

2003-07-09 Thread Ernst Lippe
appreciate it when they can easily exchange data between the two programs. (I know this is probably not quite the right moment to suggest this) greetings, Ernst Lippe (PS. Robin I would apreciate it if you could forward this message to the cinepaint-developers list. I think

Re: [Gimp-developer] the user installer

2003-07-09 Thread Ernst Lippe
copies of the binaries to other without telling them that it is GPL-ed and giving them access to the sources. I am not a great fan of licenses either, but from a legal point it is really important to inform all users about their license. greetings, Ernst Lippe

Re: [Gimp-developer] Re: Tentative 2.2 feature list

2004-02-17 Thread Ernst Lippe
that the preliminary version of the preview tried to prevent recursive updates and that the names did not start with GIMP. As far as I can tell these points have been fixed in the first official release. Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http

Re: [Gimp-developer] Re: Tentative 2.2 feature list

2004-02-18 Thread Ernst Lippe
On Wed, 18 Feb 2004 10:18:58 +0100 Dave Neary [EMAIL PROTECTED] wrote: Hi, Ernst Lippe wrote: Sven Neumann [EMAIL PROTECTED] wrote: http://refocus.sourceforge.net/preview/gimppreview.html The major points in the discussion were that some people did not like the way

Re: [Gimp-developer] Re: Tentative 2.2 feature list

2004-02-18 Thread Ernst Lippe
On Wed, 18 Feb 2004 13:51:40 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: http://refocus.sourceforge.net/preview/gimppreview.html The major points in the discussion were that some people did not like the way that the preliminary version

[Gimp-developer] Re: GIMP preview widget (was tentative 2.2 feature list)

2004-02-19 Thread Ernst Lippe
On Wed, 18 Feb 2004 15:18:49 +0100 Dave Neary [EMAIL PROTECTED] wrote: Hi Ernst, Ernst Lippe wrote: Dave Neary [EMAIL PROTECTED] wrote: As a matter of interest, do you do any optimisation based on the current viewport in the preview? Do you generate a viewport-sized (+ margin, say

Re: [Gimp-developer] Re: Tentative 2.2 feature list

2004-02-19 Thread Ernst Lippe
On Wed, 18 Feb 2004 16:19:06 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: No, the preview itself does not generate any temporary drawables. However there is a utility function for the plug-in to generate such temporary drawables, when it finds

Re: [Gimp-developer] Re: GIMP preview widget (was tentative 2.2 feature list)

2004-02-24 Thread Ernst Lippe
On Thu, 19 Feb 2004 16:45:45 +0100 Dave Neary [EMAIL PROTECTED] wrote: Hi, Ernst Lippe wrote: Dave Neary [EMAIL PROTECTED] wrote: 1) if the original drawable is zoomed out, do a messy scale of the original to give the new drawable (accuracy isn't *hugely* important in general

Re: [Gimp-developer] Re: Tentative 2.2 feature list

2004-02-25 Thread Ernst Lippe
On Thu, 19 Feb 2004 16:00:08 +0100 Sven Neumann [EMAIL PROTECTED] wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: The decision if the plug-in needs the temporary drawable is made by its designer and it is certainly not forced by the preview. It is perfectly possible to draw a row

Re: [Gimp-developer] Gimp2 plugin porting problems

2004-05-03 Thread Ernst Lippe
afraid that I don't have the time right now to suggest a good solution (anyhow I don't have Gimp-2 installed, so I can't test any modifications). Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo

Re: [Gimp-developer] plug-in preview widget (another try)

2004-05-25 Thread Ernst Lippe
believe that slow algorithms are an important use case for the design of a preview. Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] plug-in preview widget (another try)

2004-05-25 Thread Ernst Lippe
often. So having a larger buffer makes the design of the plug-in more complicated (how should it determine the right size for this buffer), it will cause a performance hit on many normal preview operations. Ernst Lippe ___ Gimp-developer mailing list

Re: [Gimp-developer] plug-in preview widget (another try)

2004-05-25 Thread Ernst Lippe
experience this happens very frequently. Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] plug-in preview widget (another try)

2004-05-25 Thread Ernst Lippe
On Tuesday 25 May 2004 14:57, Sven Neumann wrote: Hi, Ernst Lippe [EMAIL PROTECTED] writes: Do you really propose that the plug-in itself handles all the GUI interactions for scrolling, zooming and resizing and that it also is responsible for recording the current position and scale

Re: [Gimp-developer] plug-in preview widget (another try)

2004-05-25 Thread Ernst Lippe
for the user. Ernst Lippe ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer