OpenEuphoria

COMING REAL SOON !

• Posted by Bernie Ryan <xotron at localnet.com> Jul 20, 2001
• 326 views

Features of the w32engin.ew library

  This is a new Win32 library written with the advance user in mind.

  This library is not meant to compete with the win32lib but is
  written for the user that is familar with "C" and understands
  some Windows programming.

  I know that there many Euphoria user's who want to use a Window's
  library that can be easily extended without having to be concerned
  with how the internal library code works. Many users don't have
  the time to pore through lines of internal code and patch in
  changes.
  Finaly these same user's want to be able use Window's .res files
  directly within your program without loading external files or
  appending files to the exe.
  The w32engin.ew library solves all these problems
  and allows you to write a single stand-alone program protecting
  your resources from be changed because they are enbedd in your code.

  The majority of the Window's constants, functions, and procedures
  are predefined in the library of about 377k in size.

  When a Window's program is written it will look just as it would
  in "C". Using the real Window's function names which makes it
   easier to translate a "C" source code listing.

  The library comes with a utility called eru.ex that takes a standard
  complied 32-bit Window's .res file reads the file and writes a
  complete stand-alone include file. This allows you to create your
  resources with a resource editor, a dialog editor or a text editor.
  Run in the Window's .rc file through a 32-bit resource compiler
  like the free Borland BRCC32 and then use the eru.ex utility to
  generate a Euphoria include file.
  The final Euphoria generated include file will contain all that is
  needed to use the resources the bmps, icons, cursors, string tables
  and dialogs.
  NO EXTERNAL FILES ARE NEEDED just the Euphoria include file. 

  The end user can add any of the following by adding a discription or
  definition in the piston.ew file WITHOUT CHANGING the INTERNAL
  LIBRARY CODE. This will automatically interface them to all the
  features of the library.

  ANY structure can be described and accessed.
  ANY function or procedure including from ANY NON-WIN32 dll can be
  added and used.

  When I posted this anouncement before only one person showed any
  interest.
  Maybe when I complete the demos and send the library to ROB for
  the Archive the users will realize the value of this library.

  PS: if this text is not formated properly blame the topica e-mail

  Thanks for your attention,

Bernie