The MASM Forum Archive 2004 to 2012

General Forums => The Laboratory => Topic started by: GregL on August 12, 2007, 04:13:26 AM

Title: Up to date Windows API Reference
Post by: GregL on August 12, 2007, 04:13:26 AM
I made this "Windows API Reference" file at the end of April (2007) and it's pretty good. It's up to date and it's not too big. It was pulled from MSDN with "Package This" and saved as a CHM file.


[attachment deleted by admin]
Title: Re: Up to date Windows API Reference
Post by: Vortex on August 12, 2007, 06:54:47 AM
Hi Greg,

Very nice work, thanks.
Title: Re: Up to date Windows API Reference
Post by: ramguru on August 12, 2007, 07:01:16 AM
Sorry to say, but it doesn't contain a single API definition, not even full API listing...that's why it is so small  :lol
Title: Re: Up to date Windows API Reference
Post by: sinsi on August 12, 2007, 07:32:51 AM
Ahh, it links to the internet - that's why it's so small.
Title: Re: Up to date Windows API Reference
Post by: GregL on August 12, 2007, 06:08:03 PM
Thanks Vortex.

That's a problem with the "Package This" program, it claims to create stand-alone CHM files, but a lot of times they end up being full of links to the internet. Oh well. I've been using this CHM file and it has been handy, although it won't do you much good if you don't have an internet connection.

I'm going to see if I can create a stand-alone version, I'll post it if it's not too big.

Title: Re: Up to date Windows API Reference
Post by: GregL on August 12, 2007, 10:23:56 PM
Nope, can't create it with "Package This".

It is what it is.
 
Title: Re: Up to date Windows API Reference
Post by: Tedd on August 13, 2007, 10:32:14 AM
I have 40MB+ that says otherwise :lol
I have the pages and the section bookmarks work correctly, but most of the page links themselves are messed up and direct to the web instead (even though the pages are in there.)
I'm looking to convert them to plain html and fix them up, but obviously it's going to take a while.
Title: Re: Up to date Windows API Reference
Post by: GregL on August 13, 2007, 05:47:54 PM
Tedd,

Did you use the Package This (http://www.codeplex.com/packagethis) program to create it?

More power to ya man.  :thumbu



Title: Re: Up to date Windows API Reference
Post by: Tedd on August 14, 2007, 12:27:55 PM
Yeah, if you right-click on the subtree you want then you can choose to get all of its children (otherwise you only get that specific page, with links to the children - as you got.) Alternatively you can select with of the children you want, indivually, but that's a pain when there are hundreds.
Title: Re: Up to date Windows API Reference
Post by: GregL on August 14, 2007, 05:11:47 PM
Tedd,

OK, no matter what I do I only get links. If you get your file fixed up please make it available.

After thinking about it, maybe having just the links is a good thing, it's always up to date and it sure is small. If you don't have an internet connection, (how often is that any more?) you can always fall back to an older help file.
Title: Re: Up to date Windows API Reference
Post by: ramguru on August 14, 2007, 05:33:57 PM
Quote from: Greg on August 14, 2007, 05:11:47 PM
After thinking about it, maybe having just the links is a good thing, it's always up to date and it sure is small.
You have a browser for that purpose   :wink
I just recalled one good fairy-tale The Emperor's New Clothes (http://www.worldwideschool.org/library/books/youth/fantasy/AndersensFairyTales/Chap1.html)
Title: Re: Up to date Windows API Reference
Post by: GregL on August 14, 2007, 05:53:46 PM
ramguru,

The reason I like CHM files is they can be integrated into editors like UltraEdit, WinAsm, TextPad, qeditor etc. You can also set it up so that they do context sensitive help with the F1 key.

If you don't like to use them, then don't use them. If you prefer to use a browser that's fine. I prefer to use CHM files. Why am I having to defend myself when I post stuff here?

Title: Re: Up to date Windows API Reference
Post by: ramguru on August 14, 2007, 06:00:29 PM
You're taking my post too seriously and to personally  :toothy
First time you got some criticism  :bg, huh ?..
What an imperfect world we're living in  :boohoo:
Cheer up, and keep up good work  :thumbu
Title: Re: Up to date Windows API Reference
Post by: GregL on August 14, 2007, 06:07:36 PM
QuoteFirst time you got some criticism  BigGrin, huh ?..

No, I just get really tired of smartasses.


Title: Re: Up to date Windows API Reference
Post by: ramguru on August 14, 2007, 06:53:21 PM
One more prove to look into member's profile before posting anything, and correlate reply with his age.
God I never learn that lesson.
Sorry!!
Title: Re: Up to date Windows API Reference
Post by: GregL on August 14, 2007, 07:06:16 PM
ramguru,

No problem, I am getting to be a "grumpy old fart" sometimes.  :bg

Title: Re: Up to date Windows API Reference
Post by: Polizei on August 27, 2007, 06:48:24 AM
When talking about (full) API reference, I'd just advise you to use Microsoft Platform SDK which comes free with Microsoft Document Explorer. The download is about 400MB, however. It's not big, it's ENORMOUS, but it worths.
For those that traffic is not a problem, MS PSDK can be found at www.microsoft.com/msdownload/platformsdk/sdkupdate/ (http://www.microsoft.com/msdownload/platformsdk/sdkupdate/)
Title: Re: Up to date Windows API Reference
Post by: Vortex on August 27, 2007, 04:44:11 PM
Windows Server 2003 R2 Platform SDK Full Download :

http://www.microsoft.com/downloads/details.aspx?FamilyId=484269E2-3B89-47E3-8EB7-1F2BE6D7123A&displaylang=en
Title: Re: Up to date Windows API Reference
Post by: sonic on September 04, 2007, 04:34:38 PM
After looking that it's "Complete Up to date Api reference" i got excited but ahh it needs connection. Thanks for the effort though. i thought maybe a complete helpfile similar to the one we are having from 1997  :snooty:.
But then again the sdk is far too much space needy. It's not of much worth if a person is not always connected or if a person have access to google  :P

Tedd could u share your work?
Title: Re: Up to date Windows API Reference
Post by: GregL on September 04, 2007, 09:17:19 PM
Unless you can automate building a CHM file from the Windows API Reference online, it's just too tedious a task to build one by hand. Package This (http://www.codeplex.com/packagethis) comes close but leaves links in the CHM. If you figured out the MTPS Content Service (http://services.msdn.microsoft.com/ContentServices/ContentService.asmx) you might be able to do it. I think all we will see from Microsoft for offline use is the enormous Platform SDK. It would be great to have an up-to-date stand-alone CHM file for the Windows API Reference.

Actually, the one I made that has the links to the web works fine for me. I noticed the Pelle's C IDE works the same way.

Title: Re: Up to date Windows API Reference
Post by: Tedd on September 05, 2007, 12:39:21 PM
If I manage to get it into a usable form, then yes of course :wink
It will either be a pile of html pages (massaged into shape), or even more optimistically, some kind of meta-format from which html/chm/pdf/rtf/wtf could be automatically constructed :bg
Title: Re: Up to date Windows API Reference
Post by: Howard on September 10, 2007, 09:35:31 PM
Greg
Thanks for sharing this chm. Better than anything else I've found. It will add a new dimension to my programming.
(I've been getting the MSDN Subscriptions Library but MS NZ tell me that they've stopped issueing it.)

Howard
Title: Re: Up to date Windows API Reference
Post by: GregL on September 10, 2007, 10:40:18 PM
Howard,

You are welcome.

Title: Re: Up to date Windows API Reference
Post by: AkinforASM on September 10, 2007, 11:14:04 PM
Hi,

There is an application called HTM2CHM which creates compiled HTML help files. It's quite handy and incorporates itself onto Windows (in my experience XP) shell.

You right-click on the folder containing HTML files to be compiled, click htm2chm menu and select first "create TOC and index" and after creating TOC and indexes you right click on the folder again and this time select "compile" from the context menu.

If the folder contains a lot of files then it takes too long, but the result is satisfactory.

HTH.