Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- The Guide to Clip-4-Win version 3.0 - Norton Guide http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]

  To give you an idea of how simple a Clip-4-Win program can be:
  
            MessageBox( , "Hello World!", "Clip-4-Win" )
  
  Although it's not very useful, it does show that Windows
  applications don't have to be complex!  (See SOURCE\HELLO.PRG.)
  
  Almost all the following are actually optional, but a
  reasonable minimum for a business application is:
  
       (a)  A main window.  Sometimes called a frame or shell window.
       (b)  A menu.
       (c)  Dialogs (forms), e.g. for data entry.
       (d)  Browse windows.
  
  As Windows is event driven, you also need:
  
       (e)  An event/message loop.
       (f)  Event/message handlers.
  
  These are analogous to the TBrowse code you need with DOS
  Clipper: code to determine the user's actions, like INKEY(),
  and code to handle the actions.
  
  Later, these are discussed:
  
       (g)  Resources.  See "Simple Data Entry Application".
       (h)  A toolbar (button bar).
       (i)  MDI (multiple document interface).
  
  The event loop in a Windows application is responsible for
  fetching the events from Windows and getting them handled.
  Generally speaking, a Windows application just sits there
  doing nothing until an event arrives.  As the opening screen
  in many applications is a window with a menu, it's a menu-
  related event that starts a browse or dialog.  Toolbars are
  often implemented as if each button is a menu item.
  
  

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson