As mentioned in an earlier post, we are still working hard to find out how we can improve the HTML version support in QNX4.25.
Our exact usecase is we need to display some html files in ‘local filesystem’
We have read about Voyager SDK as in link qnx.com/developers/qnx4/qnx4 … ?code=6374
and embed.com.cn/2993CFA7-951B-4 … oyager.pdf.
Understood that Voyager SDK has HTML3.2 support and also supports PtWebClient.
Also as per schoenbrun.com/mba/faq.htm#L21, Maschoen mentioned about Internet Appliance Toolkit Development CD which includes Voyager SDK.
We have some queries regarding these findings:-
Our assumption is:
a. QNX 4.25 supports HTML1.1 by default.
b. If we buy Voyager SDK and integrate it with QNX4.25, we will get PtWebClient support as well as HTML3.2 support.
Is our assumption correct?
Do we exactly need Voyager SDK for displaying html 3.2 files on local filesystem? I mean, is voyager SDK designed for some complex usecase like displaying html files on remote machines?
As per PtWebClient help page, it is mentioned that PtWebClient transparently supports the version of HTML that the server supports.
So we assume we need to buy Voyager SDK to get PtWebClient support on QNX4.25. After getting PtWebClient working on QNX4.25, can we adjust the backend server on it to some other server such as mozilla server or opera server to get HTML4 support on QNX4.25.
Is this assumption correct?
Please shed some light to our concerns…
Thank you for your understanding and patience…