I've implemented support for CHM help, but it still requires some modifications. I've done quite a lot of changes, I'm writing what exactly I have done to make implanting it easy:

1. I moved OnHelp event from actions.asm file to new help.asm.
2. I set Fresh stack to 0x10020 (with just 64K it didnt want to work - argghhh, Micro$uck... )
3. Added code (in fresh.asm) that creates variable containing Fresh directory - it should be useful in future - but temporary it uses GetCurrentDirectory, so it may cause problems. What would be the best way to obtain Fresh dir? Parsing command line?
4. Converted htmlhelp.h to fasm format - it must be placed in include/win32/equates directory.
5. Added MAX_PATH definition to kernel32.inc file from above dir.
6.In Fresh directory folder named 'doc' must be created and freshguide.chm file must lie there.
All modified files files are included in attachement.

If everything will be set properly, pressing F1 will search freshguide.chm for given keyword, and if this lookup fails, it will search file chosen in 'appearance options'.

uffff

oh, and I made updates to the Guide itself

regards,
decard

outdated attachement removed.

Hi Decard.
Really impressive work.
I implemented it and it works good at least in Win98.
I only don't like this variable hFreshDirectory and the way you set it's via "GetCurrendDir".

There are better variants. I suggest you two:
1. Use another line in [Environment] section of Fresh.ini (for example: "FreshDoc") and to use "%FreshDoc%/freshguide.chm" as file name.
Then you have to pass this name to ConvertPath function (it is in Fasm.asm file) - it will return handle to string with full path name to the file. (Don't forget to delete it.)

2. Leave this variant, but move everything related in help.asm and create the full path/file name of the freshguide.chm in InitHelp procedure, using not GetCurrentDir, but GetModuleFileName the same way as hApplication window ( include/libs/application.asm - WM_CREATE handler) when it gets the name of Fresh INI file.

Also, I think that in the future, we have to add Privalovs documentation about FASM syntax to your chm file to allow help on the FASM keywords too.

Regards.

OK, I'll follow variant #2.
But why don't you want to have a global variable containing Fresh directory? It would be useful in future - for example to access directory with templates...

regards

Well, IMHO it is not flexible enough. It ties the help file to the executable location and it is not very good. For example, when I work on Fresh, I compile it in the directory "source" and first I run it from this directory. But in "source" your help don't work. I have to make second copy of freshguide.chm in "source/doc/" to make it work.
BTW: I think that seting environment variables have another problems, but it will be fixed later.

Regards.

BTW: I just remember, there is a port of FASM docs to CHM, made by IceStudent, maybe you have to contact him, and simply add his file to yours.

Regards.

Both solutions have their advantages and disadvantages. I don't like to make user set one more variable in fresh.inc. And proably "ordinary" Fresh users will almost always run our IDE from its main directory. So I will make it this way: I will check fresh.ini for %freshdoc% variable, and if it won't exist, I will look for it in main Fresh directory.


Yeah, but first I must think about the way how to do it. Now I would like to make some better (commented!!!) examples, and make some corrections in existing Guide.
Also, I want the help system to display help even when user selects some assembler instruction, but I would have to add each instruction to keyword file manually .

That is exactly what we need. Good approach. BTW: You still can try "ConvertPath" for this. It checks Fresh.ini AND also environment, the same way as FASM compiler.

Regards

I made the changes that we were talking about. Also, this required some changes in StrLib - I'm attaching new version here.

regards

outdated attachement removed.

New version of the Fresh Guide here. I included FASM manual, but I still have a lot of work on keyword list. However, some of FASM directives are already added, so you can have a contex help when you point for example "virtual" directive

regards

[edit]outdated attachment removed[/edit]

Great!