Tkinter: The good, the bad, and the ugly!

Adam Skutt askutt at gmail.com
Tue Jan 18 17:57:02 EST 2011


On Jan 18, 4:45 pm, Arndt Roger Schneider <arndt.ro... at addcom.de>
wrote:
> Adam Skutt schrieb:
> > Until we have pixel-perfect touch sensors, toolkits for devices with
> > pointer interfaces (e.g., PCs) and toolkits for devices with touch
> > interfaces (e.g., phones and tablets) will necessarily be different.
>
> > You note this yourself: the UI paradigms that work well when you have
> > a pixel-perfect pointer do not work at all when you have a touch
> > screen, especially on a limited size and resolution display.
>
> Yes I did and that's how it is.

And then you go and advocate a single toolkit!  Do you not see the
inherent contradiction there?  While it's certainly not impossible,
the case is hardly obvious for one GUI toolkit for all possible UIs.
You certainly have not presented it, and rantingrick never will.


> Think about all the programmers earning their butter and bread :-).
> Forget toolkits and widgets for awhile.
> What remains are specific types of human/computer interactions,
> a visual representation on a screen and a predefined behaviour
> for said human action.

Also known as "toolkits and widgets".  Talking about such things are
inescapable.

>
> E.g. a button is:
> A function gets asychnronously performed in response to
> a finger/mouse click and release inside a certain screen area.
>

No, that is not the definition of a 'button', not even when we choose
to ignore how it is rendered, which you cannot ignore even if you wish
to pretend you can.  Otherwise, I could always treat hyperlinks and
buttons as equivalent and even interchangeable.  Unfortunately, they
are no such things.

> --A widget is essentially a logical abstraction.

No, as much as we try we cannot divorce presentation from behavior
fully.

> > Because it's not cross-platform, I'd imagine.  The entire point of
> > wxWidgets was to provide a cross-platform "OOP" UI toolkit.  It
> > closely copies MFC since MFC and XView were the two "backends" it
> > supported.
>
> MacApp is/was cross-platform, Apple pulled the plug
> on the non-mac platforms; the industrie
> consortium took charge of the other platforms.
>

MacApp didn't even see the start of cross-platform development until
1996, four years after wxWidgets.  It was not cross-platform from the
start and only became cross-platform when all of Apple's other cross-
platform endeavours failed.

Adam



More information about the Python-list mailing list