Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [geda-user] Non-modal Dialogs
From: Edward Hennessy <ehennes AT sbcglobal DOT net>
In-Reply-To: <1374513797.3124.12.camel@AMD64X2.fritz.box>
Date: Mon, 22 Jul 2013 16:23:07 -0700
Cc: geda-dev AT delorie DOT com
Content-Transfer-Encoding: 7bit
Message-Id: <8830B86E-FCAF-4290-A41D-3C837CB667FA@sbcglobal.net>
References: <2174C2C2-6FAF-4544-A4C0-5FDBD564A6FB AT sbcglobal DOT net> <1374513797 DOT 3124 DOT 12 DOT camel AT AMD64X2 DOT fritz DOT box>
To: geda-user AT delorie DOT com
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk


On Jul 22, 2013, at 10:23 AM, Stefan Salewski <mail AT ssalewski DOT de> wrote:
> 
> An interesting question.
> 
> I think my idea last year was:
> 
> We have only one property dialog window or area, which can be visible or
> not. (I prefer an area for my peted clone, instead of overlapping
> windows, but that is a matter of taste.) If the user clicks on an
> element (symbol, text, net...) the property display update its content
> when it is open/visible -- some values may be displayed always like
> color, other like font or footprint only for some elements. A double
> click on an element may open that property display. Updating elements by
> other means (scripts, menu...) should simple gray out that property
> display, or maybe ask that display to update after all is done. It makes
> no sense to update that property display hundred times when a script
> changes textsize for all refdes.
> 

This would be the end goal. I don't have enough time to convert all the
dialog boxes over to the property dialog. It would help me if we could
go that direction in smaller steps.

What should the underlying property change notification system be? Would
developers be ok with gobject and signals?

Cheers,
Ed