>is it likely that we will see source code for the clipper rendering
>component or at least have access the the launch codes to use it?
>(ie point it to my own database and get it to render)
The rendering and user interaction (i.e. what people think of as a web
browser's functionality) is done by WebLib. The API to WebLib is ... well
... unsupportable, and can be expected to change dramatically in future
releases. Thus there are no plans to give out its source, or support it in
anything other than Clipper.
Sorry, but that's reality. It really was not written in such a way that it
could be usefully used by anything but Clipper itself.
That said, the launch codes that you can send to Clipper to get it to
render a PQA page, or go over the air to get a web clipping and show it,
those are already documented. See sysAppLaunchCmdGoToURL and
sysAppLaunchCmdOpenDB. They just don't take place inside your app; instead
you switch to Clipper and it takes control.
-David Fedor
Palm Developer Support
