Click above to get retro games delivered to your door ever month!

  
  Clip-4-Win allows you to build Clipper programs that are true
  Windows programs, with access to resources such as brushes,
  colours, icons, menus, pens and so on.
  
  It does this by building on the functionality provided by
  Clipper, and indeed it is a tribute to Clipper that this is
  possible.
  
  However, Clip-4-Win is not a replacement for the CA project
  code-named Aspen.  Rather, Clip-4-Win is a means to learn and
  use Windows (from the developer's viewpoint), without having
  to give up Clipper and move to C, C++, Visual Basic,
  SmallTalk, Eiffel, Actor, or whatever.

  Clip-4-Win provides a good introduction to Visual Objects
  ("VO"), without locking you in.  On a number of public
  occasions, CA have demonstrated and announced details of VO.
  They have stated and shown that VO supports the Windows API.
  You can expect to move Clip-4-Win programs to VO with
  relatively minor changes.  It will certainly be much easier to
  move a typical Clip-4-Win program to VO than to move a typical
  DOS Clipper program to VO.  This is because Clip-4-Win
  applications are event-driven, use the Windows API, and such
  Windows features as resources (which CA have shown the VO
  compiler can compile).  Any DLL's you use from Clip-4-Win can
  of course also be used from VO.

  The two products are not so much competitors as brothers.
  Clip-4-Win is "Clipper with Windows features", and VO is to be
  a complete Xbase GUI development environment.  Clip-4-Win has
  some advantages, though.  You can ship real Windows
  applications now, and it is more Clipper-compatible: same pre-
  processor, same compiler, etc.  It allows third-party products
  like Class(y) to be used, too.  You can even use one set of
  sources for both DOS and Windows.