dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #25850
Re: Introduce a new dependency (QT)?
-
To:
Joachim Berdal Haga <jobh@xxxxxxxxx>
-
From:
Anders Logg <logg@xxxxxxxxx>
-
Date:
Wed, 29 Aug 2012 11:36:20 +0200
-
Cc:
dolfin-dev <dolfin@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAPKc5=_Tb6L2qD3rQLFXiDoG-6qRR_9zeErm75Oo2erM9uFf7A@mail.gmail.com>
-
User-agent:
Mutt/1.5.21 (2010-09-15)
On Wed, Aug 29, 2012 at 11:20:19AM +0200, Joachim Berdal Haga wrote:
> On 29 August 2012 11:11, Garth N. Wells <gnw20@xxxxxxxxx> wrote:
> > On 29 August 2012 09:42, Joachim Berdal Haga <jobh@xxxxxxxxx> wrote:
> >> I would like to switch the window handling and event loop to QT,
> >> because it's much more flexible and mature (stable) than VTK's. An
> >> example of things that are hard to get working right with the VTK
> >> window handling is to close a single plotting window.
> >>
> >> This will introduce a new dependency for plotting (in addition to
> >> VTK). It will be optional, and if it's not configured then it's only
> >> plotting that is disabled.
> >>
> >> Any protests?
> >>
> >
> > I'd rather not have it as a dependency. I don't really want a major
> > dependency for lightweight plotting. I think we should bear in mind
> > that we have ParaView, MayaVi, etc for making 'real' plots, so the
> > DOLFIN plotting should remain as simple as possible.
>
> I agree with keeping it simple. The reason I want to introduce it is
> not to introduce anything complex, but to gain more robust window
> handling / event loop. However: Opposition noted -- would option 2
> (basic support for VTK-only) be acceptable to you?
I don't see why QT would be a problem. Isn't the VTK dependency just
as heavy? Or are there systems where VTK is easily available but QT is
not?
--
Anders
Follow ups
References