Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #75145 > unrolled thread

Exploring Python for next desktop GUI Project

Back to article view | Back to comp.lang.python

Contents

  Exploring Python for next desktop GUI Project Noble Bell <noblebell@gmail.com> - 2014-07-24 08:57 -0700
    Re: Exploring Python for next desktop GUI Project INADA Naoki <songofacandy@gmail.com> - 2014-07-25 01:20 +0900
    Re: Exploring Python for next desktop GUI Project Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-24 11:22 -0500
      Re: Exploring Python for next desktop GUI Project Grant Edwards <invalid@invalid.invalid> - 2014-07-24 16:37 +0000
        Re: Exploring Python for next desktop GUI Project Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-24 13:17 -0500
    Re: Exploring Python for next desktop GUI Project Chris Angelico <rosuav@gmail.com> - 2014-07-25 02:18 +1000
    Re: Exploring Python for next desktop GUI Project Noble Bell <noblebell@gmail.com> - 2014-07-24 09:29 -0700
      Re: Exploring Python for next desktop GUI Project Chris Angelico <rosuav@gmail.com> - 2014-07-25 02:46 +1000
      Re: Exploring Python for next desktop GUI Project Michael Torrie <torriem@gmail.com> - 2014-07-24 15:38 -0600
    Re: Exploring Python for next desktop GUI Project Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-24 19:04 +0200
    Re: Exploring Python for next desktop GUI Project Chris Angelico <rosuav@gmail.com> - 2014-07-25 03:09 +1000
    Re: Exploring Python for next desktop GUI Project Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-24 19:04 +0100
    Re: Exploring Python for next desktop GUI Project Chris Angelico <rosuav@gmail.com> - 2014-07-25 04:15 +1000
    Re: Exploring Python for next desktop GUI Project Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-24 13:33 -0500
      Re: Exploring Python for next desktop GUI Project Grant Edwards <invalid@invalid.invalid> - 2014-07-24 21:17 +0000
    Re: Exploring Python for next desktop GUI Project Chris Angelico <rosuav@gmail.com> - 2014-07-25 04:51 +1000
      Re: Exploring Python for next desktop GUI Project Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-07-25 10:28 +1200
    Re: Exploring Python for next desktop GUI Project Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-07-24 21:02 +0200
      Re: Exploring Python for next desktop GUI Project Grant Edwards <invalid@invalid.invalid> - 2014-07-24 21:24 +0000
    Re: Exploring Python for next desktop GUI Project Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-24 14:10 -0500
    Re: Exploring Python for next desktop GUI Project Glenn Linderman <v+python@g.nevcal.com> - 2014-07-24 12:11 -0700
    Re: Exploring Python for next desktop GUI Project Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-24 13:32 -0600
      Re: Exploring Python for next desktop GUI Project Noble Bell <noblebell@gmail.com> - 2014-07-24 13:10 -0700
        Re: Exploring Python for next desktop GUI Project Rob Gaddi <rgaddi@technologyhighland.invalid> - 2014-07-24 13:46 -0700
    Re: Exploring Python for next desktop GUI Project Zachary Ware <zachary.ware+pylist@gmail.com> - 2014-07-24 15:13 -0500
    Re: Exploring Python for next desktop GUI Project Michael Torrie <torriem@gmail.com> - 2014-07-24 15:24 -0600
    Re: Exploring Python for next desktop GUI Project Michael Torrie <torriem@gmail.com> - 2014-07-24 15:29 -0600
    Re: Exploring Python for next desktop GUI Project Michael Torrie <torriem@gmail.com> - 2014-07-24 15:32 -0600
    Re: Exploring Python for next desktop GUI Project ismeal shanshi <stuffstorehouse2014@gmail.com> - 2014-07-24 14:44 -0700
    Re: Exploring Python for next desktop GUI Project Terry Reedy <tjreedy@udel.edu> - 2014-07-24 19:25 -0400
      Re: Exploring Python for next desktop GUI Project wxjmfauth@gmail.com - 2014-07-26 00:48 -0700
    Re: Exploring Python for next desktop GUI Project Terry Reedy <tjreedy@udel.edu> - 2014-07-24 19:35 -0400
      Re: Exploring Python for next desktop GUI Project Noble Bell <noblebell@gmail.com> - 2014-07-25 06:37 -0700
    Re: Exploring Python for next desktop GUI Project Sturla Molden <sturla.molden@gmail.com> - 2014-07-25 20:04 +0000
    Re: Exploring Python for next desktop GUI Project CM <cmpython@gmail.com> - 2014-07-27 10:53 -0700
      Re: Exploring Python for next desktop GUI Project pecore@pascolo.net - 2014-07-29 00:00 +0200
        Re: Exploring Python for next desktop GUI Project Roy Smith <roy@panix.com> - 2014-07-28 18:01 -0400
          Re: Exploring Python for next desktop GUI Project pecore@pascolo.net - 2014-07-29 21:47 +0200

Page 1 of 2  [1] 2  Next page →

#75145 — Exploring Python for next desktop GUI Project

I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.

My requirements will be:
1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)
2. Python 2 or 3? Which will serve me better in the future?

Thanks in advance.
Noble

[toc] | [next] | [standalone]

#75146

1. PyQt (or PySide)
2. Python 2 will be legacy soon. Use Python 3 for new project.

wxPython is also good option but doesn't support Python 3 for now.
I don't know when wxPhenix (next wxPython supporting Python 3) will be released.

On Fri, Jul 25, 2014 at 12:57 AM, Noble Bell <noblebell@gmail.com> wrote:
> I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.
>
> My requirements will be:
> 1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)
> 2. Python 2 or 3? Which will serve me better in the future?
>
> Thanks in advance.
> Noble
>
> --
> https://mail.python.org/mailman/listinfo/python-list



-- 
INADA Naoki  <songofacandy@gmail.com>

[toc] | [prev] | [next] | [standalone]

#75147

On Thu, Jul 24, 2014 at 10:57 AM, Noble Bell <noblebell@gmail.com> wrote:
> I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.
>
> My requirements will be:
> 1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)

The Python standard library includes the tkinter package, which is an
interface to Tcl/Tk.  The 'ttk' module provides themed/themable
widgets that have the platform-native look by default.  I've
successfully used tkinter for a few projects, and have kept most of my
sanity :).  One of the biggest benefits to tkinter is that, since it
is included with Python, so you don't have to distribute a separate
GUI toolkit.

> 2. Python 2 or 3? Which will serve me better in the future?

Python 3 is the future of Python, but Python 2(.7) is still alive and
kicking.  I would suggest sticking to Python 3 if at all possible, but
revert back to 2.7 (no farther! :) if you have dependencies that you
can't escape that rely on Python 2.  If you're just learning Python,
learn with Python 3 before you start with Python 2, even if you'll
wind up using Python 2.  Python 3 is easier to learn in the first
place, and it's easier to learn the transition from 3->2 than 2->3.

Hope this helps,
-- 
Zach

[toc] | [prev] | [next] | [standalone]

#75150

On 2014-07-24, Zachary Ware <zachary.ware+pylist@gmail.com> wrote:
> On Thu, Jul 24, 2014 at 10:57 AM, Noble Bell <noblebell@gmail.com> wrote:
>> I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.
>>
>> My requirements will be:
>> 1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)
>
> The Python standard library includes the tkinter package, which is an
> interface to Tcl/Tk.

That's not always true for Linux systems.  AFAIK, all Linux installs
include Python (of some version or other), but they don't always
include tcl/tk and tkinter. It's usually easy enough to add them, but
but they're not really part of the "standard library" if they have to
be separately intsalled.

-- 
Grant Edwards               grant.b.edwards        Yow! Uh-oh!!  I'm having
                                  at               TOO MUCH FUN!!
                              gmail.com            

[toc] | [prev] | [next] | [standalone]

#75164

On Thu, Jul 24, 2014 at 11:37 AM, Grant Edwards <invalid@invalid.invalid> wrote:
> On 2014-07-24, Zachary Ware <zachary.ware+pylist@gmail.com> wrote:
>> The Python standard library includes the tkinter package, which is an
>> interface to Tcl/Tk.
>
> That's not always true for Linux systems.  AFAIK, all Linux installs
> include Python (of some version or other), but they don't always
> include tcl/tk and tkinter. It's usually easy enough to add them, but
> but they're not really part of the "standard library" if they have to
> be separately intsalled.

There are several parts of the standard library that have external
dependencies (bz2, lzma, sqlite3, ssl, and tkinter, just off the top
of my head), which distributors may not decide to include.  That
doesn't mean they're not part of the standard library, but they are
optional parts.  Anyway, it may still be easier to declare a
dependency on tkinter than to distribute another toolkit with your
app, it depends entirely on the specific circumstances.

-- 
Zach

[toc] | [prev] | [next] | [standalone]

#75148

On Fri, Jul 25, 2014 at 1:57 AM, Noble Bell <noblebell@gmail.com> wrote:
> I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.
>
> My requirements will be:
> 1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)
> 2. Python 2 or 3? Which will serve me better in the future?
>
> Thanks in advance.

The first one is certainly possible. Pick any of the well-known
toolkits (Tkinter, wxwidgets, GTK, etc), and see how it feels. All of
them are portable across the three platforms you name, so see which
one is most comfortable for you to code in and produces the best
results.

Definitely Python 3. If you don't have anything specifically holding
you to Python 2, take Python 3 and get all the latest features. Most
importantly, you'll never run into troubles with Unicode.

ChrisA

[toc] | [prev] | [next] | [standalone]

#75149

On Thursday, July 24, 2014 10:57:22 AM UTC-5, Noble Bell wrote:
> I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.
> 
> 
> 
> My requirements will be:
> 
> 1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)
> 
> 2. Python 2 or 3? Which will serve me better in the future?
> 
> 
> 
> Thanks in advance.
> 
> Noble

I was leaning toward Python 3 and Tkinter. I suppose the best way to do the GUI with Tkinter is to just roll-up my sleeves and do it via code rather than with the aid of a GUI editor.

Thanks to all of you for your replies. 

[toc] | [prev] | [next] | [standalone]

#75151

On Fri, Jul 25, 2014 at 2:29 AM, Noble Bell <noblebell@gmail.com> wrote:
> I was leaning toward Python 3 and Tkinter. I suppose the best way to do the GUI with Tkinter is to just roll-up my sleeves and do it via code rather than with the aid of a GUI editor.

Yep. In fact, I recommend that for all GUI toolkits; instead of
thinking about your layout in terms of positions of widgets on a
window, think about it in terms of what your toolkit provides you with
- usually that'll be some kind of tree structure of layout objects,
like vertical and horizontal boxes. And if you plan your layout that
way, you may as well just write it directly as code.

ChrisA

[toc] | [prev] | [next] | [standalone]

#75185

On 07/24/2014 10:46 AM, Chris Angelico wrote:
> On Fri, Jul 25, 2014 at 2:29 AM, Noble Bell <noblebell@gmail.com> wrote:
>> I was leaning toward Python 3 and Tkinter. I suppose the best way to do the GUI with Tkinter is to just roll-up my sleeves and do it via code rather than with the aid of a GUI editor.
> 
> Yep. In fact, I recommend that for all GUI toolkits; instead of
> thinking about your layout in terms of positions of widgets on a
> window, think about it in terms of what your toolkit provides you with
> - usually that'll be some kind of tree structure of layout objects,
> like vertical and horizontal boxes. And if you plan your layout that
> way, you may as well just write it directly as code.

As an exercise, yes this is valuable, but not necessary as a matter of
course. But I rarely code guis anymore.  I use Qt Designer for Qt apps,
and Glade-3 for GTK and then load the resulting XML into my app at
runtime.  The GUI designers expose the full layout management
capabilities of the toolkit.  In GTK terms that's generally hboxes or
vboxes with expansion flags.  In Qt it's the same but with "springs" to
consume space to make things grow and shrink appropriately.

[toc] | [prev] | [next] | [standalone]

#75153

[Multipart message — attachments visible in raw view] — view raw

On Jul 24, 2014 6:28 PM, "Zachary Ware" <zachary.ware+pylist@gmail.com>
wrote:
>
> On Thu, Jul 24, 2014 at 10:57 AM, Noble Bell <noblebell@gmail.com> wrote:
> > I am exploring the idea of creating my next desktop GUI project in
Python and would like a little advice from you folks about a couple of
requirements.
> >
> > My requirements will be:
> > 1. Needs to be portable across platforms with native LAF
(Windows,Linux,OSX)
>
> The Python standard library includes the tkinter package, which is an
> interface to Tcl/Tk.  The 'ttk' module provides themed/themable
> widgets that have the platform-native look by default.  I've
> successfully used tkinter for a few projects, and have kept most of my
> sanity :).  One of the biggest benefits to tkinter is that, since it
> is included with Python, so you don't have to distribute a separate
> GUI toolkit.

Tk is neither sane nor native-feeling, especially on Linux, where it looks
like something from two decades ago. On other platforms, it also is not
100% native.

I personally recommend PyQt4/PySide. wxPython is also worth checking out.
And it might be better to stay with Python 2, there are still things that
don't work with Py3k that you might find crucial.

-- 
Chris “Kwpolska” Warrick <http://chriswarrick.com/>
Sent from my SGS3.

[toc] | [prev] | [next] | [standalone]

#75155

On Fri, Jul 25, 2014 at 3:04 AM, Chris “Kwpolska” Warrick
<kwpolska@gmail.com> wrote:
> I personally recommend PyQt4/PySide. wxPython is also worth checking out.
> And it might be better to stay with Python 2, there are still things that
> don't work with Py3k that you might find crucial.

Can you be more specific? Python 3 should be the default for new
projects unless there's a good reason for going Py2.

Chrisa

[toc] | [prev] | [next] | [standalone]

#75162

On 24/07/2014 17:18, Chris Angelico wrote:
> On Fri, Jul 25, 2014 at 1:57 AM, Noble Bell <noblebell@gmail.com> wrote:
>> I am exploring the idea of creating my next desktop GUI project in Python and would like a little advice from you folks about a couple of requirements.
>>
>> My requirements will be:
>> 1. Needs to be portable across platforms with native LAF (Windows,Linux,OSX)
>> 2. Python 2 or 3? Which will serve me better in the future?
>>
>> Thanks in advance.
>
> The first one is certainly possible. Pick any of the well-known
> toolkits (Tkinter, wxwidgets, GTK, etc), and see how it feels. All of
> them are portable across the three platforms you name, so see which
> one is most comfortable for you to code in and produces the best
> results.

s/wxwidgets/wxpython/ unless you fancy wrapping it yourself :)

>
> Definitely Python 3. If you don't have anything specifically holding
> you to Python 2, take Python 3 and get all the latest features. Most
> importantly, you'll never run into troubles with Unicode.

Definitely definitely Python 3.  It's The Comfy Chair who anybody having 
the audacity to disagreee on this!!!

>
> ChrisA
>

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[toc] | [prev] | [next] | [standalone]

#75163

On Fri, Jul 25, 2014 at 4:04 AM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
> On 24/07/2014 17:18, Chris Angelico wrote:
>> The first one is certainly possible. Pick any of the well-known
>> toolkits (Tkinter, wxwidgets, GTK, etc), and see how it feels. All of
>> them are portable across the three platforms you name, so see which
>> one is most comfortable for you to code in and produces the best
>> results.
>
>
> s/wxwidgets/wxpython/ unless you fancy wrapping it yourself :)
>

Yeah that. And pygtk rather than GTK. Or I could have gone the other
way and said Tk instead of Tkinter. One way or another, I ought to
have been more consistent. Anyway. Pick a good toolkit, get to know
it, and use it. Personally, I like GTK, but that's partly because its
bindings come with Pike, and I did GUI work with Pike before I did
with Python; the same advantage, for someone starting with Python,
goes to Tk. But the main thing is, it's easy to be cross-platform -
take whatever feels good to you.

ChrisA

[toc] | [prev] | [next] | [standalone]

#75169

On Thu, Jul 24, 2014 at 12:04 PM, Chris “Kwpolska” Warrick
<kwpolska@gmail.com> wrote:
> Tk is neither sane

How so?  Like any other facet of programming, using Tk(inter) has it's
frustrations, but for the most part it has always worked as expected
for me.  Granted, I haven't done anything terribly fancy.

> nor native-feeling, especially on Linux, where it looks
> like something from two decades ago.

The problem there is that on Linux, "native" could mean "GTK", "QT",
or something else entirely.  Also, just to make sure, you are talking
about "ttk" rather than plain "tk", right?

> On other platforms, it also is not 100%
> native.

On Windows, at least, ttk comes very very close to it.

> I personally recommend PyQt4/PySide. wxPython is also worth checking out.

I have used neither of those, but I have seen many people report
happiness with them.  For anyone with experience with those toolkits
in other languages, those would be the obvious choices.

> And it might be better to stay with Python 2, there are still things that
> don't work with Py3k that you might find crucial.

I strongly disagree with this: there's no reason to stick with Python
2 until you have a dependency that you can't get rid of that
absolutely requires Python 2.x.  The fact that "there are still things
that don't work with Py3k" is irrelevant if you don't use them.  And
if you find that, halfway through building your app, you find that you
need to add a dependency that requires Python 2, just backport your
project.  In the majority of cases, it is very easy to port from
Python 3 to either the subset of Python that runs fine in both 2 and
3, or straight to 2.  It may just be a matter of going from:

   import tkinter as tk
   from tkinter import ttk

to:

   try:
       import tkinter as tk
       from tkinter import ttk
   except ImportError:
       import Tkinter as tk
       import ttk

It's not necessarily as easy to go from native Python 2 to 2and3 or 3
due to some incorrect assumptions that Python 2 will let you make, but
even that can be mitigated by writing your Python 2 code with Python 3
in the back of your mind.

-- 
Zach

[toc] | [prev] | [next] | [standalone]

#75180

On 2014-07-24, Zachary Ware <zachary.ware+pylist@gmail.com> wrote:
> On Thu, Jul 24, 2014 at 12:04 PM, Chris “Kwpolska” Warrick
><kwpolska@gmail.com> wrote:
>> Tk is neither sane
>
> How so?  Like any other facet of programming, using Tk(inter) has it's
> frustrations, but for the most part it has always worked as expected
> for me.  Granted, I haven't done anything terribly fancy.
>
>> nor native-feeling, especially on Linux, where it looks
>> like something from two decades ago.
>
> The problem there is that on Linux, "native" could mean "GTK", "QT",
> or something else entirely.  Also, just to make sure, you are talking
> about "ttk" rather than plain "tk", right?
>
>> On other platforms, it also is not 100%
>> native.
>
> On Windows, at least, ttk comes very very close to it.

One of the Tk apps I maintain gets distributed to Windows users as
well as Linux users.  On my Win7 machine, it looks/acts like a native
(at least as much as a Linux user can tell).  None of the hardcore
windows guys who use it have ever mentioned that it looks or acts
oddly.

On Linux, it looks like crap and acts a little goofy -- sort of
vaguely old-school-Motif with non-standard keybindings.

-- 
Grant Edwards               grant.b.edwards        Yow! BARRY ... That was
                                  at               the most HEART-WARMING
                              gmail.com            rendition of "I DID IT MY
                                                   WAY" I've ever heard!!

[toc] | [prev] | [next] | [standalone]

#75170

On Fri, Jul 25, 2014 at 4:33 AM, Zachary Ware
<zachary.ware+pylist@gmail.com> wrote:
>> On other platforms, it also is not 100%
>> native.
>
> On Windows, at least, ttk comes very very close to it.

What exactly does that mean? The Windows default UI changed
significantly from W2K -> XP -> Win8, and each time, it's possible to
revert to the old styling; does ttk follow the rest of the OS in that?
And if so, does it achieve that by restricting you to a vicious subset
of functionality that can actually be implemented natively, or does it
try to reimplement as appropriate?

ChrisA

[toc] | [prev] | [next] | [standalone]

#75188

Chris Angelico wrote:
> The Windows default UI changed
> significantly from W2K -> XP -> Win8, and each time, it's possible to
> revert to the old styling;

Well, sort of. I find that using the classic theme with
Win7 is a less-than-satisfying experience, because it
still lays things out the same way as the Win7 theme,
resulting in big ugly gaps and a generally haphazard
appearance. I quickly gave up on it and learned to like
the new look. :-(

-- 
Greg

[toc] | [prev] | [next] | [standalone]

#75171

On Thu, Jul 24, 2014 at 8:33 PM, Zachary Ware
<zachary.ware+pylist@gmail.com> wrote:
> On Thu, Jul 24, 2014 at 12:04 PM, Chris “Kwpolska” Warrick
> <kwpolska@gmail.com> wrote:
>> Tk is neither sane
>
> How so?  Like any other facet of programming, using Tk(inter) has it's
> frustrations, but for the most part it has always worked as expected
> for me.  Granted, I haven't done anything terribly fancy.

Pretty much everyone in the world hates Tcl and Tk.  Ask your favorite
search engine for some results.

i’ve tried to write a Tkinter thing once.  I don’t have a copy anymore
(consciously deleted), but I vaguely remember some issues with widgets
that do not work.  I also remember that the list of widgets is quite
small and not enough for many projects.

>> nor native-feeling, especially on Linux, where it looks
>> like something from two decades ago.
>
> The problem there is that on Linux, "native" could mean "GTK", "QT",
> or something else entirely.

The best way to handle this is just choose one of the two (wxwidgets
chose GTK 2, for example) and be considered native enough by most, as
people don’t really mind mixing them (as there are no good Qt web
browsers, and VLC uses Qt and not GTK)

> Also, just to make sure, you are talking about "ttk" rather than plain "tk", right?

ttk on Linux doesn’t change a thing.  It still uses the ugly, ancient,
motif-esque style:

https://www.google.com/search?q=tk+linux&tbm=isch

(also, off by 10 years, motif is actually from the 1980s.)

On Thu, Jul 24, 2014 at 8:51 PM, Chris Angelico <rosuav@gmail.com> wrote:
> On Fri, Jul 25, 2014 at 4:33 AM, Zachary Ware
> <zachary.ware+pylist@gmail.com> wrote:
>>> On other platforms, it also is not 100%
>>> native.
>>
>> On Windows, at least, ttk comes very very close to it.
>
> What exactly does that mean? The Windows default UI changed
> significantly from W2K -> XP -> Win8, and each time, it's possible to
> revert to the old styling; does ttk follow the rest of the OS in that?

There is one more catch, custom themes can be installed after you
patch some files (which can be done in 5 minutes by anyone with
sufficient googling and reading comprehension skills).

AFAIK, Qt follows the system style properly, and it looks quite native
on every Windows OS.  No idea about ttk though.

-- 
Chris “Kwpolska” Warrick <http://chriswarrick.com/>
PGP: 5EAAEA16
stop html mail | always bottom-post | only UTF-8 makes sense

[toc] | [prev] | [next] | [standalone]

#75181

On 2014-07-24, Chris “Kwpolska” Warrick <kwpolska@gmail.com> wrote:
> On Thu, Jul 24, 2014 at 8:33 PM, Zachary Ware
><zachary.ware+pylist@gmail.com> wrote:
>> On Thu, Jul 24, 2014 at 12:04 PM, Chris “Kwpolska” Warrick
>> <kwpolska@gmail.com> wrote:
>>> Tk is neither sane
>>
>> How so?  Like any other facet of programming, using Tk(inter) has it's
>> frustrations, but for the most part it has always worked as expected
>> for me.  Granted, I haven't done anything terribly fancy.
>
> Pretty much everyone in the world hates Tcl and Tk.  Ask your favorite
> search engine for some results.

Tcl and Tk are both absolutely brilliant for doing trivial things.

Once the complexity starts to increase beyond "hello world, click here
to exit", Tcl falls over almost immediately and starts flopping around
like a fish on a dock.  Tk hangs in there quite a bit longer and is
pretty useful as long as you've just got one main window and a few
dialog boxes.  IMO, it looks/acts native "enough" on Windows (at least
for the widgets I've used).  On Linux, it looks/acts "non-native" (not
GTK or Qt), but Linux users don't have an immediate brain sieze-up
when confronted with a slightly different UI, and they seem to be able
to use Tk apps just fine.

-- 
Grant Edwards               grant.b.edwards        Yow! Well, I'm INVISIBLE
                                  at               AGAIN ... I might as well
                              gmail.com            pay a visit to the LADIES
                                                   ROOM ...

[toc] | [prev] | [next] | [standalone]

#75172

On Thu, Jul 24, 2014 at 1:51 PM, Chris Angelico <rosuav@gmail.com> wrote:
> On Fri, Jul 25, 2014 at 4:33 AM, Zachary Ware
> <zachary.ware+pylist@gmail.com> wrote:
>> On Windows, at least, ttk comes very very close to [a 100% native look].
>
> What exactly does that mean? The Windows default UI changed
> significantly from W2K -> XP -> Win8, and each time, it's possible to
> revert to the old styling; does ttk follow the rest of the OS in that?
> And if so, does it achieve that by restricting you to a vicious subset
> of functionality that can actually be implemented natively, or does it
> try to reimplement as appropriate?

It appears that ttk follows the rest of the OS just fine (just tested
on Win7, switching back and forth to the "classic Windows" theme), and
as yet I've not run into any restrictions because of it.

-- 
Zach

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.python

csiph-web