As a user more than a developer, I would suggest that if you took the
platform specific documentation out of the RexxRef that you at least left
some hint of it in (at the logical point in the documentation), in the form
of a stub, hyperlink or some such, so that the platform specific users know
that there is something relevant to look for.
By the way, I still use the old Object Rexx Windows help files about 95% of
the time, because they are so much quicker and easier to search than the
PDFs - not that I have a solution to suggest.
Keep up the good work.
> One idea in general, though: how about removing all of the Windows
> documentation from "rexxref", creating an own "windowsRef" documentation
> which should include in addition all of the "ooDialog" docs. This way
> "rexxref" contains all the documentation of ooRexx which is available on
> all platforms. "windowsRef" includes all the additional, Windows
> specific information (OLEObject, OLEVariant, Win* classes, ooDialog
> classes). The Windows docs also will move the ooDialog classes into the
> center, hinting interested Windows programmers at their capabilities and
> This eventually may yield an own "macOSX" reference (which may be just a
> few dozen pages initially), which draws the attention of Mac users to
> the specific functionality on MacOSX.
> Message: 4
> Date: Sat, 30 Jun 2007 07:00:12 -0400
> From: "Rick McGuire" <object.rexx@...>
> Subject: Re: [Oorexx-devel] Info and some ideas ... (Re: v3.2.0
> rexxref.pdf Comments Needed
> To: "Open Object Rexx Developer Mailing List"
> Content-Type: text/plain; charset="iso-8859-1"
> I think I like all of these suggestions....I'd had similar thoughts
> particularly about moving the windows-specific stuff elsewhere.