Re: [Gimp-developer] Preview requirements

2003-03-04 Thread Ernst Lippe
On 03 Mar 2003 11:54:42 +0100 Michael Natterer <[EMAIL PROTECTED]> wrote: > Again, you should understand how GObject signals work. They operate > purely synchronously. A signal handler cannot be "too slow" because > the only thing your program is doing while emitting the signal is > emitting the s

Re: [Gimp-developer] Preview requirements

2003-03-03 Thread Michael Natterer
Ernst Lippe <[EMAIL PROTECTED]> writes: > 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

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

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

Re: [Gimp-developer] Preview requirements

2003-03-01 Thread Sven Neumann
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 implementation of such a system is > to let each object synchronize with all o

Re: [Gimp-developer] Preview requirements

2003-03-01 Thread Michael Natterer
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 implementation the preview > > > widget consists of the following comp

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

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 p

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Branko Collin
On 26 Feb 2003, at 14:03, Ernst Lippe wrote: > A preview widget for plug-ins is one of these items that has been on > the Gimp todo list for a long time. > > In order to get some feedback from other developers we have compiled a > list of requirements for a preview widget. The list is based on o

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Sven Neumann
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 controls. When scrollbars should be added > the horizontal scrollbar sh

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Ernst Lippe
On Wed, 26 Feb 2003 14:17:21 +0100 Øyvind Kolås <[EMAIL PROTECTED]> wrote: > * Ernst Lippe <[EMAIL PROTECTED]> [030226 14:04]: > > > Non-requirement 1. Preview the rendered results in the original image > > window. > > > > The rendered image should be shown in the original image window. > > >

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 visual

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Sven Neumann
Hi, Øyvind Kolås <[EMAIL PROTECTED]> writes: > * Ernst Lippe <[EMAIL PROTECTED]> [030226 14:04]: > > > Non-requirement 1. Preview the rendered results in the original image > > window. > > > > The rendered image should be shown in the original image window. > > > > Comment: This is one of the

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Sven Neumann
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 and makes its > internal structure more complicated. The alternative of givi

Re: [Gimp-developer] Preview requirements

2003-02-26 Thread Øyvind Kolås
* Ernst Lippe <[EMAIL PROTECTED]> [030226 14:04]: > Non-requirement 1. Preview the rendered results in the original image > window. > > The rendered image should be shown in the original image window. > > Comment: This is one of the suggestions from the GUAD3C meeting. It > does not seem relev

[Gimp-developer] Preview requirements

2003-02-26 Thread Ernst Lippe
A preview widget for plug-ins is one of these items that has been on the Gimp todo list for a long time. In order to get some feedback from other developers we have compiled a list of requirements for a preview widget. The list is based on our own experiences and previous discussions on this mail