Jump to content











Photo
- - - - -

WinBuilder user interfaces


  • Please log in to reply
4 replies to this topic

#1 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

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 ?.



#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

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 :dubbio:

 

DOS times were simple and disappeared ... :jaclaz:

 

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 :cheers:



#3 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

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.

 

:cheers:

Wonko



#4 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10441 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

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 a console line interface (has a console to input line commands)
  • It is a command line interface (runs commands from the command shell)
  • It is a graphical user interface (don't forget others aspects such as "config win7pe" that has buttons and pretty stuff)
  • It is a web user interface (has it's server to allow users controlling wb through a browser)
  • It is an application protocol interface (can be fully controlled by another app using the API system)
  • It is a user interface for the visually impaired

 

It is not the end of the world to support different types of interfaces.

 

Can we please continue?

 

Thanks.



#5 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13443 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

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. :)

 

:cheers:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users