- In the GUI type "auto" (w/o the quotes) and click / hit "return" / "execute"
Why it is called a 'GUI" then ?. So Winbuilder is also going back to the DOS era ?.
Posted 26 November 2013 - 05:43 AM
- In the GUI type "auto" (w/o the quotes) and click / hit "return" / "execute"
Why it is called a 'GUI" then ?. So Winbuilder is also going back to the DOS era ?.
Posted 26 November 2013 - 07:25 PM
As known, GUI means "graphical user interface".
And IMO already the border of a frame is for the computer some graphic.
That's the difference to CLI (console line interface), with just console text lines input / output.
Maybe some other people have a different opinion about GUI / CLI definition
DOS times were simple and disappeared ...
The current WinBuilder power exceeds DOS, ... , Win31, ... ,WinME, ... ,Win2000, ... , XP, ... , WIN8, because it also speaks to the MAC and ??X world.
Book some lessons in a primary school.
I'm sure that after that you understand, that by typing characters you can express your intention much better than by clicking ununderstandable pictures and colorful squares, provided, you have the necessary creativity and intelligence.
Peter
Posted 27 November 2013 - 08:32 AM
For the record, CLI = Command Line Interface.
Basically if you type commands (on a line), it is a CLI interface.
Wonko
Posted 27 November 2013 - 09:35 AM
Everyone is right and this discussion is getting to a state of trolling. I'm splitting it from the original topic.
It is not the end of the world to support different types of interfaces.
Can we please continue?
Thanks.
Posted 27 November 2013 - 10:17 AM
BTW, there is IMHO nothing "wrong" with an app being CLI, I would go farther saying that ALL apps should be CLI (at the core) and have (optional) GUI's.
This way everyone would be happy.
Wonko
0 members, 1 guests, 0 anonymous users