X-Received: by 10.66.235.36 with SMTP id uj4mr13022875pac.9.1379436710492; Tue, 17 Sep 2013 09:51:50 -0700 (PDT) X-Received: by 10.50.35.228 with SMTP id l4mr860951igj.15.1379436710243; Tue, 17 Sep 2013 09:51:50 -0700 (PDT) Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder02.blueworldhosting.com!news.ripco.com!rahul.net!wasp.rahul.net!rahul.net!news.kjsl.com!usenet.stanford.edu!y3no29880379pbx.0!news-out.google.com!rn2ni87842pbc.1!nntp.google.com!d5no315413qap.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.python Date: Tue, 17 Sep 2013 09:51:50 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=59.95.1.38; posting-account=mBpa7woAAAAGLEWUUKpmbxm-Quu5D8ui NNTP-Posting-Host: 59.95.1.38 References: <1a8b14b3-85f3-4515-ba43-9b40e1a89f1d@googlegroups.com> <63de767b-1df3-4981-b86e-dbf8fa10c9e0@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Python GUI? From: rusi Injection-Date: Tue, 17 Sep 2013 16:51:50 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: csiph.com comp.lang.python:54323 On Tuesday, September 17, 2013 9:49:28 PM UTC+5:30, Benjamin Kaplan wrote: > On Tue, Sep 17, 2013 at 7:55 AM, rusi wrote: > > > On Thursday, September 12, 2013 10:21:49 PM UTC+5:30, Benjamin Kaplan wrote: > > > > >> The main difference between wx and qt is that qt looks native on every platform > >> while wx *is* native on every platform (it uses native controls wherever > >> possible). This means that wx integrates into the OS better, but your also more > >> likely to need OS-specific tweaks in wx, at least from my experience from a few > >> years ago. > > > > For someone who is GUI-challenged, can you please expand on that a bit? > > -- > > Sure. Every platform provides its own GUI library (Cocoa on Mac OS X, > Win32 on Windows). Other programs that want to hook into yours, such > as screen readers, are familiar with the platform's native GUI > elements- it knows what a Win32 combo box is, and it knows how to read > the text inside it. > > > The other way to make a GUI is to take a blank canvas and draw on it > yourself. This is more flexible and provides a more consistent > experience across platforms, but unless you specifically go out of > your way to provide hooks for other programs to jump in, all they see > is a bunch of pixels on the screen. In addition, drawing your own > stuff won't necessarily give you the "normal for the operating system" > behavior on other things, like tab behavior. It's possible for > non-native GUI environments to mimic this behavior (and QT does a > pretty good job of this), but there's always going to be little things > that seem a bit off. Thanks for the explanation. However I am not able to square it up: You seem to be saying that QT draws on a blank canvas rather than calling out to the OS library. You also seem to be saying that QT (for the most part) Does the Right Thing for each platform.