Considances When Choosing a Gui Package

zhaozj2021-02-12  217

As we have seen, there are quite a few ways to build a GUI in Python and in some cases a choice is difficult. How, for instance, can you choose among Tk, wxWindows, FLTK or FOX if you do not have knowledge or experience In Them? Well, Before you make a choice you Should Have a Look at each of them in any copy. and you shouth check the Following Issues:

The number of widgets. Well, if they are ugly or unnecessarily numerous, you will not be satisfied. But a diversity of good looking and functional widgets will help you design a good interface, especially if you are not a GUI designer.

Look. It is very important nowadays to allow an application to look exactly accounting to the capital theme of the operationg system, incruding widgets That do not exist on a particular OS.

For some projectant to change the os.

IT IS Also 'In' To Be Able To Create Your OWN LOOK - & - FEEL

IT Is Important to Be Able To Create Your OWN Components. If you need you. See The Transparent screen.

See ifwi widgets provide transparency and layering.

See if IT is Possible to Locate Widgets Both Absolutely and relatively.

See IF zooming is supported. I do not know of any gui library for python That Does

See If the Image Formats you work with is compressed, transparent, interlaacing, annimateable and supported by the Internet explorer.

Look at the geometry capabilities. It may sound weird but the most important geometric figure is a dot. Some packages provide you with lines, circles and what not but when you wish to draw whatever you wish, you often need just a dot :). IT May Be Specially True if you wish to go into charting.text and language iesss:

INTERNATIONALIZATION:

Unicode

.

Some Gui Libraries Offer You Good Components in Which You Can show formatted text. Some Even Go Further And Allow You Show Text Directly in The Common Formats (HTML, RTF, PDF, DOC)

Grid.

Ability to use any.............

Speed. Grids Can Work Slowly With Large Data Chunks.

Cross Platform Compatibility May Be Important to You. There Are Three Issues:

Does it cover all the planforms you need

Does It Really Look Fine on All Platforms:

WHEN you do not define a specific Look - & - Feel and your application buys the os l & f

When you use a certain l & f

You Write One Code and Do Not Go Into the OS Specifics

IT IS Particularly Convenient When Your GUI Is Based On Some Changing Data.

Check the license

How popular the library is. The more popular it is the more chances there are that it will not vanish tomorrow morning. For example, Tk IS popular. WxWindows is also popular because many people out there consider it to be better than Tk. But who CAN COMPARE WITH GTK Which Is a Part of Such Projects as gnome and gimp ?!

Who Stands Behind The Library. It is very important to know what the development of the library you.com you need contract.

Open source or proprietary? It is good when a rich company stands behind a libary. But they can grab you by the .... Open source is theoretically unreliable from many aspects but in practice it is the best because the best brains stand behind it .There are also other, I call them traditional, considerations such as speed, memory use, multithreading and many others but the packages listed above are good. In any case, if you know of some theoretical problem that may come up, test it. .

Comparison Chart of All the package limited here - Under Construction It Is Going to Be a Table with The Following Paramaters for Comparison:

Shell: WHETHER IT IS Performed As You Type (Like Python, TK, DOS ETC)

Widgets: Number and Usefulness

Native Fook - & - Leel Issues

Realtime theme change

Custom L & F

Transparent Top Level Windows

Absolute Layout

RELATIVE LAYOUT

Supported Image Formats

Localization

Unicode and InternationalizationATIONalization

Data Structures and Graphical Widget for Supporting Formatted Text

TEXT FORMATS: HTML, RTF, XML ETC

Grid Support

Platforms

View-Model Architecture

License Type

Used in Longliving Projects (QT IN KDE, GTK IN GIMP ETC)

Who is the developmenter

Creating your own GUI package The most ideal situation would be if Python had at least the most primitive commands for windowing systems The problem is that there are at least three differently built systems:. Windows, X, Mac and why learn how to program them if someone else already did. That's what I think thought Guido van Rossum the Father of Python. He began with the Tk GUI library. As this page shows, many more GUI libraries followed. But how ?! Python has a C extention mechanism. So, if some C GUI library has objects: Window, Button, Canvas it is possible to call these objects from Python This leads to the situation when each of the numerous C GUI libraries must have its own wrapper in Python But do not we live.. in the crosseverything compatibility age ?! Would not it be great to write one GUI package in Python and let developers decide what C GUI libraries they wish to use underneath. and this, in turn, leads to the anyGUI situation when AnyGUI.Window is Implement by pytosomecl ibWrapper.Window. In this respect AnyGUI is just like Java AWT. For those of you who do not know, such a solution did not work for Java. The next stage of Python GUI packages should be the Swing stage of Java when there is preferably but not necessarily one native object that does all the drawing and all the actual widgets should be drawn dot by dot in Python. For example a Button object of such a package would have a draw method whose code would be a dot by dot, line by Line Description of the Button and when '

转载请注明原文地址:https://www.9cbs.com/read-7180.html

New Post(0)