> > I didn't mean to ignore Mac platforms. So, as has been stated, I also agree
> > that providing the help in a more open standard (such as HTML), would be
> > great. There are plenty of tools available for parsing HTML into WinHelp
> > format, etc (or maybe even QuickHelp? on the Mac). The PDF
>format seems not
> > so open, and I'm not sure, but even proprietary?
> >
> > In my opinion, I'm all for leaving the "Companion", "CookBook" and
> > "Tutorials" in PDF, but the "Reference" should be made into something that
> > is more geared toward lookups/searches from IDE's and code editors on all
> > platforms.
> >
> FWIW, I routinely leave a Virtual PC session open on my Mac for the
>express purpose of using a WinHelp-format Palm reference. This, to me, is
>infinitely preferable to searching HTML or PDF. I really don't care what
>format the "Guide" documentation is in, but the reference really has to be
>QUICKLY searchable for it to be useful. On Windows, that pretty much means
>WinHelp, and on the Mac I guess it would be QuickView or QuickHelp, but I
>really would settle for a Windows-centric solution if that's all I could
>get.
And on the Mac, Altura makes a product that converts WinHelp source
into QuickHelp format. Doesn't help UNIX/Linux folks, but covers Mac
and Windows developers.
It would help immensely if Palm would supply the source for their PDF
files, even if it is in FrameMaker or some other app. Someone would
have to convert the source into WinHelp/QuickHelp/whatever, but it
would at least be possible.
