Re: What are the Missing Parts in the CVF Windows API?

From: Jugoslav Dujic (jdujicREMOVE_at_uns.ns.ac.yu)
Date: 12/22/03 

Date: Mon, 22 Dec 2003 09:44:10 +0100

Craig Dedo wrote:
| Dear Readers:
| I have some questions about writing Fortran Windows Applications
| (not QuickWin) using CVF 6.6B.
|
| 1. Both the documentation and third-party books say that **almost**
| all of the full functionality of the Windows API, as defined in the C
| language <windows.h>, is included. What functionality is missing?

Well, here are some that I know of; mostly, these are ones that may
be considered "addenda" on the top of APIs (the border is fuzzy).
If we define that Win32 API is what is #defined in <windows.h> and
descendants, I think that this translation is really complete; however,
there is more stuff than windows.h.

- Simple MAPI (Mail API)
- HtmlHelp APIs
- Some of Shell COM related stuff. For example, I had to do manual
  translation (+some reverse engineering) of IShellLink interface
  (used with shell shortcuts) in XFTLite::XFTFile::XCreateShortcut.
  (I didn't manage to generate them using Module Wizard)
- Native NT (un/semi)documented low-level stuff (ZWxxx functions)

Plus, Microsoft keeps on adding new stuff with every new release of
Windows/IE. I doubt Intel/Compaq can catch up immediately (but they
do a fairly new job)
 
| 2. What, if any, documentation is there about the missing
| functionality?

I doubt there is any documentation about missing stuff -- do a
"Find in files" in ...\DF98\Include folder to make sure a symbol
is translated.
 
| 3. What, if any, ways are there to get modules that provide the
| missing functionality? I.e., other than writing the modules from
| scratch. E.g., are there any Web sites that provide these modules?

See my home page below for example ("Headers" and "XFT" sections).
There are possibly other isolated attempts. But usually, if you need
an API badly, you have to do it yourself based on existing MSDN
documentation. 

-- 
 Jugoslav
___________
www.geocities.com/jdujic

Relevant Pages

  • Re: Difference between .NET and Java
    ... > people that I know agree with my speculation that the CLR was in fact ... > similarities between the CLR and the Win32 API. ... Actually what I ment to say was the .NET has Windows specific functionality ...
    (comp.lang.java.programmer)
  • Re: Getting/Setting States of VB-Shelled Application Windows
    ... Windows when the window is created and which identifies the window) of ... VB's Shell function does not return an hWnd. ... You'll have to use the API to get that. ... any example code included in the documentation is going to be C/C++. ...
    (microsoft.public.vb.controls)
  • RE: Outlook forms integrated with Tasks
    ... you can use all controls available under windows forms api and better logic. ... it will though everyone using this functionality to install the com add-in ... "Muneeb" wrote: ...
    (microsoft.public.outlook.program_forms)
  • Implementing expected core OS functionality
    ... Most documentation and sample code on Windows ... Dolphin provides a wonderful platform for studying the OS API ... might reference the particular API. ...
    (comp.lang.smalltalk.dolphin)
  • Re: How will PatchGuard change kernel programming?
    ... An API documentation is a contract between the API vendor and ... Windows API sometimes, ... this is just another way that Microsoft is increasing its monopoly ...
    (microsoft.public.win32.programmer.kernel)