![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I wrote a little program for my win98 to help lip sync with POV
animations. When it came to make the help file I found my old
Help editor (ElipseHelp) crashed. Then came the long search for a Help
editor that would work on my 98. I'm sick of it! I don't know how many
I've downloading, only to have them crash, or be just plain wrong.
I'm serious thinking of going with a seperate Html file for the Help.
I'm blowing of steam :{ Ah.... That felt good.
If you have any suggustions. I'm listening.....
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Leroy Whetstone wrote:
> I wrote a little program for my win98 to help lip sync with POV
> animations. When it came to make the help file I found my old
> Help editor (ElipseHelp) crashed. Then came the long search for a Help
> editor that would work on my 98. I'm sick of it! I don't know how many
> I've downloading, only to have them crash, or be just plain wrong.
> I'm serious thinking of going with a seperate Html file for the Help.
> I'm blowing of steam :{ Ah.... That felt good.
> If you have any suggustions. I'm listening.....
Personally, I think HTML help files are great, as long as everything is
linked correctly. It's either one extra directory to the index, or one
extra visible folder to look at. A good trade-off, IMO.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
stbenge schrieb:
> Personally, I think HTML help files are great, as long as everything is
> linked correctly. It's either one extra directory to the index, or one
> extra visible folder to look at. A good trade-off, IMO.
I personally am more in for (well-indexed) PDF files.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
clipka wrote:
> I personally am more in for (well-indexed) PDF files.
What the BEEP. I hate PDF files with a passion.
You know what PDF means Pretty Damned F###ed.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Leroy Whetstone schrieb:
>> I personally am more in for (well-indexed) PDF files.
>
> What the BEEP. I hate PDF files with a passion.
> You know what PDF means Pretty Damned F###ed.
Why is that?
They give a nice, clean, consistent layout on every output device
(including printers). HTML files, on the other hand, always have this
subtle "half-finished" feel to them, no matter how much effort you put
into their design.
And you can easily do a full-text search on a PDF, which is always a
semi-hassle with HTML help files (as they typically don't come in a
single file).
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
PDF has the advantage that it looks fantastic when printed out, and the
disadvantage that it generally doesn't look very good on-screen. Being a
paged medium, with (usually) portrate pages while the screen has a
landscape aspect, it's really not very screen-friendly.
HTML has the opposite advantages: it looks terribly when printed out
(I've yet to find any browser anywhere that can print HTML properly),
but it's much easier to work with on-screen. It can use screen-optimised
fonts, you can adjust the font size to look good on your screen, the
text layout automatically matches the window size, and so on.
Of course, PDF has the advantage of being a single, compressed file with
no possibility of broken hyperlinks / missing images / missing fonts /
etc. But for a help file, I'd suggest that HTML is more appropriate.
(Who the hell is going to print out 2,000 pages on actual paper?)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Leroy Whetstone wrote:
> I wrote a little program for my win98 to help lip sync with POV
> animations. When it came to make the help file I found my old
> Help editor (ElipseHelp) crashed. Then came the long search for a Help
> editor that would work on my 98. I'm sick of it! I don't know how many
> I've downloading, only to have them crash, or be just plain wrong.
> I'm serious thinking of going with a seperate Html file for the Help.
> I'm blowing of steam :{ Ah.... That felt good.
> If you have any suggustions. I'm listening.....
...you want a program that works on Windows 98?
Uh, good luck with that then.
So are you talking about *.hlp or *.chm files? They're different file
formats.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
A few years ago I used the official HTML-Help compiler from Microsoft to
produce help-files.
All you need apart from the compiler is Word or a RTF-Editor. Not very
comfortable, but I once did help files this way.
"Leroy Whetstone" <lrw### [at] joplin com> schrieb im Newsbeitrag
news:4AF### [at] joplin com...
> I wrote a little program for my win98 to help lip sync with POV
> animations. When it came to make the help file I found my old
> Help editor (ElipseHelp) crashed. Then came the long search for a Help
> editor that would work on my 98. I'm sick of it! I don't know how many
> I've downloading, only to have them crash, or be just plain wrong.
> I'm serious thinking of going with a seperate Html file for the Help.
> I'm blowing of steam :{ Ah.... That felt good.
> If you have any suggustions. I'm listening.....
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> (I've yet to find any browser anywhere that can print HTML properly),
What you mean is that you've yet to find any HTML properly marked up for
printing.
--
Darren New, San Diego CA, USA (PST)
I ordered stamps from Zazzle that read "Place Stamp Here".
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible schrieb:
> Of course, PDF has the advantage of being a single, compressed file with
> no possibility of broken hyperlinks / missing images / missing fonts /
> etc. But for a help file, I'd suggest that HTML is more appropriate.
> (Who the hell is going to print out 2,000 pages on actual paper?)
Especially with a help file, I might want to do a full text search now
and then.
Screw your 2000+ HTML files.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |