kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #32155
Re: COMPONENT_TREE performance
-
To:
Jon Evans <jon@xxxxxxxxxxxxx>, Chris Pavlina <pavlina.chris@xxxxxxxxx>
-
From:
Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx>
-
Date:
Mon, 4 Dec 2017 19:06:10 +0100
-
Authentication-results:
spf=pass (sender IP is 188.184.36.46) smtp.mailfrom=cern.ch; lists.launchpad.net; dkim=none (message not signed) header.d=none;lists.launchpad.net; dmarc=bestguesspass action=none header.from=cern.ch;
-
Cc:
KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CA+qGbCBV9EdOyEn2MxG6-4Y=fqFMKp3_kg6OKApB7HmmOZ_McA@mail.gmail.com>
-
Spamdiagnosticmetadata:
NSPM
-
Spamdiagnosticoutput:
1:99
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
On 04/12/17 18:59, Jon Evans wrote:
> I've got some experience with Qt and would be willing to help out with
> investigating this at some point. My only experience with wx is with
> kicad, and it seems to have many more problems than Qt...
> On the other hand, I disagree with the suggestion that Electron would be
> a good path for KiCad, every single Electron program I have used has
> terrible performance.
What I meant is using electron exclusively for the GUI (same as Qt), to
ease the design of a modern and customizable interface. All internals,
canvases, tools would be still C++. AFAIK most Electron apps are
entirely written in HTML/JS, which may be the reason for sluggish
performance.
Anyway, we'll have to stick to wx for the reasonable future.
Tom
>
> -Jon
>
> On Mon, Dec 4, 2017 at 12:55 PM, Chris Pavlina <pavlina.chris@xxxxxxxxx
> <mailto:pavlina.chris@xxxxxxxxx>> wrote:
>
> On Mon, Dec 04, 2017 at 05:53:12PM +0000, Tomasz Wlostowski wrote:
> > On 04/12/17 18:48, Chris Pavlina wrote:
> > > Hey, just a comment because I see people are wrestling with
> > > COMPONENT_TREE performance as I did when writing it. TEST ON MACOS. The
> > > performance of the widget there has a really different profile from on
> > > other systems. I had to do things in really unobvious ways to make it
> > > perform reasonably there.
> > >
> >
> > I've noticed spending more and more time fixing wxWidgets bugs instead
> > of Kicad bugs. Maybe we should have a serious look at Qt or Electron
> > (Webkit/JS-based UI) as a possible future alternative for wx...
>
> YES. I try not to bring it up too much because I know the lead devs
> aren't fond of the idea of changing the GUI toolkit, but I strongly
> believe we could benefit from that. Obviously it can't really happen
> until we ditch wxDC.
>
> >
> > Tom (fighting with wxWidgets thread safety under Windows...)
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> <https://launchpad.net/~kicad-developers>
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers
> <https://launchpad.net/~kicad-developers>
> More help : https://help.launchpad.net/ListHelp
> <https://help.launchpad.net/ListHelp>
>
>
References