Hi all,
I'm strongly considering biting the bullet and switching over
to Webhelp from HTML Help. I think it's the right decision, but
it's late in our devo cycle...<sigh>...anyway....
I read Peter Grainge's article about Merged Webhelp, and I
think it does everything I need. Our project is relatively huge,
and I'd like to tease it apart into subprojects that can be
distributed separately (already read Peter's caveats about that).
Before I convert, however, I want to ask about CSH mapping.
When we were working with HTML help and a single .chm file, I
generated a map ID file, let's say "project.h". In our application,
we embedded the topic ID (let's say "first_topic"). When a user
pressed F1, the application scanned project.h, then opened the
first_topic page in project.chm. Simple enough.
But with the Webhelp output, it seems that I have to specify
the target *file* to load into the browser using the format:
parent#pathname
However, my project.h file only has something like this:
#define first_topic 1000
#define second_topic 1001
It seems that what I need is something like this:
#define first_topic 1000 parent#path/first_topic.htm
#define second_topic 1001 parent#path/second_topic.htm
So my questions:
1) If I switch over to Webhelp, and if I have only the topic
IDs in the application, can I find the path for the associated help
topic?
2) If I do a *merged* webhelp project (as Peter describes),
with a 'dummy' parent and children for each 'real' project, how is
that handled with regard to CSH?
Thanks in advance,
-Greg