Q
qwe rty
i have been searching for am IDE for python that is similar to Visual
Basic but had no luck.shall you help me please?
Basic but had no luck.shall you help me please?
i have been searching for am IDE for python that is similar to Visual
Basic but had no luck.shall you help me please?
i have been searching for am IDE for python that is similar to Visual
Basic but had no luck.shall you help me please?
qwe said:i have been searching for am IDE for python that is similar to Visual
Basic but had no luck.shall you help me please?
i have been searching for am IDE for python that is similar to Visual
Basic but had no luck.shall you help me please?
I think a point and click GUI builder (although some may disagree) is
actually detrimental to your programming skills. The ability to
visualize the GUI only from the source code as you read it, is as
important to a programmer as site reading sheet music is to a
musician. And I like to program with the training wheels off.
Creating a GUI programmatically is almost always the wrong approach. It
tends to be adopted due to a path of least resistance, rather than any
affirmative reason.
The main advantage of a GUI builder is that it helps prevent you from
hard-coding the GUI into the program. You could get the same effect by
coding a UIL/XRC/etc file manually, but a GUI builder tends to force it.
It also allows the GUI to be edited by without requiring any programming
knowledge. This eliminates the need for the GUI designer to be familiar
with the programming language used (or any programming language), and
allows customisation by end users.
Creating a GUI programmatically is almost always the wrong approach. It
tends to be adopted due to a path of least resistance, rather than any
affirmative reason.
A GUI builder results in hard coding the GUI. The code only resides
elsewhere.
+1
What I resent is that it leads to a non-professional attitude
of the graphical part. Programming is over, lets now kludge
some screens together. No. The graphics part has to be carefully
designed, carefully tested, and carefully "written", even if it
is using a graphical tool. So, yes please, *do* create a GUI
"programmatically".
Groetjes Albert
A GUI builder results in hard coding the GUI. The code only resides
elsewhere.
In view of the above this is not quite the correct way to put it.
What I resent is that it leads to a non-professional attitude
of the graphical part. Programming is over, lets now kludge
some screens together. No. The graphics part has to be carefully
designed, carefully tested, and carefully "written", even if it
is using a graphical tool. So, yes please, *do* create a GUI
"programmatically".
and this is why M$ interfaces suck eggs! This whole "let's just slap
together something that works even if kludgy" attitude begets the
horrible UI's of which i speak. Are you saying that programmers have
no ability to design elegant UI's? Or are you saying GUI's are not
*that* important?
I'm saying that the user understands their workflow and environment better
than the application's programmers. The user should be able to decide
which menu items are shown and where, which buttons are shown and where,
etc. The code doesn't need to know this level of detail, let alone dictate
it.
The interface really should be configurable by the user according to their
needs. The code doesn't need to *know* the position or dimensions of
a widget, or its label or colour or spacing, let alone dictate them.
In most cases, the code shouldn't even get to dictate that specific
widgets even exist. Rather, it should provide actions which can
be bound to buttons, menu items and/or accelerators as the user chooses.
r said:I completely disagree with this idea of user "customization" of the
GUI. Sounds more like adolescent accessorizing to me. How is changing
the location of a button, or entry, or whatever, actually going to
make workflow more easier? Sounds like "somebody" failed to get input
from their users at design time. Or "somebody" has the inability to
relate to their end users. However i know some out there like the
"styles" and "skins" crap, which is a different animal altogether than
what you speak of.
Would a mechanic give you a screw driver so you could adjust the fuel/
air ratio yourself? If he did i would never take my car back again!
Just reeks of incompetence!!
Only qualified persons should fix cars, same for software!
Hello qwe rty,
I remember my first days with GUI programming and thinking to myself;
how on earth can i write GUI code without a MS style GUI builder? Not
to long after that i was coding up some pretty spectacular GUI's from
nothing more than source code and loving it.
[Warning: the following is only opinion!]
I think a point and click GUI builder (although some may disagree) is
actually detrimental to your programming skills. The ability to
visualize the GUI only from the source code as you read it, is as
important to a programmer as site reading sheet music is to a
musician. And I like to program with the training wheels off.
I completely disagree with this idea of user "customization" of the
GUI. Sounds more like adolescent accessorizing to me. How is changing
the location of a button, or entry, or whatever, actually going to
make workflow more easier?
Sounds like "somebody" failed to get input
from their users at design time. Or "somebody" has the inability to
relate to their end users.
Would a mechanic give you a screw driver so you could adjust the fuel/
air ratio yourself? If he did i would never take my car back again!
Just reeks of incompetence!!
On Mon, 07 Sep 2009 23:56:17 +0000, Albert van der Horst wrote:
My view is that the program should provide functionality without
unnecessarily dictating the way in which that functionality is used.
Essentially, it's an issue of "loose coupling".
The interface really should be configurable by the user according to their
needs. The code doesn't need to *know* the position or dimensions of
a widget, or its label or colour or spacing, let alone dictate them.
In most cases, the code shouldn't even get to dictate that specific
widgets even exist. Rather, it should provide actions which can
be bound to buttons, menu items and/or accelerators as the user chooses.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.