Skip navigation.
Home
The QNX Community Portal

View topic - QNX versions

QNX versions

Discussions, suggestions, requests about this website.

Re: QNX versions

Postby hello » Thu Dec 11, 2014 6:59 am

WebKit's JavaScript engine mentioned in https://www.webkit.org/projects/javascript/
I am not so familiar with java; may be that's why i asked a question like this
So for running the javascript, java engine alone required and it is supported for QNX 4.25. Is that correct ?
hello
Senior Member
 
Posts: 101
Joined: Tue May 08, 2012 1:09 pm

Re: QNX versions

Postby maschoen » Thu Dec 11, 2014 2:47 pm

hello wrote:WebKit's JavaScript engine mentioned in https://www.webkit.org/projects/javascript/
I am not so familiar with java; may be that's why i asked a question like this
So for running the javascript, java engine alone required and it is supported for QNX 4.25. Is that correct ?


I can understand the confusion because of the similarity of names, but javascript and java have nothing to do with each other.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: QNX versions

Postby hello » Fri Dec 12, 2014 5:29 am

Which means javascript shall run in QNX 4.25.
hello
Senior Member
 
Posts: 101
Joined: Tue May 08, 2012 1:09 pm

Re: QNX versions

Postby maschoen » Fri Dec 12, 2014 6:31 am

hello wrote:Which means javascript shall run in QNX 4.25.


As I said, it runs as part of the Voyager browser. I don't know of a separate interpreter, however it should not be hard to find one that can be ported if that is what you need.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: QNX versions

Postby hello » Tue Dec 16, 2014 7:55 am

Is javascript runs as a part of Voyager browser or Voyager server ?
hello
Senior Member
 
Posts: 101
Joined: Tue May 08, 2012 1:09 pm

Re: QNX versions

Postby maschoen » Tue Dec 16, 2014 9:09 am

I don't know what the architecture of voyager is. My guess is that it would be part of the Voyager server, but that is just a guess.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: QNX versions

Postby hello » Tue Dec 16, 2014 11:32 am

Ok Maschoen, I also think its a part of Voyager server.
Suppose we are porting any rendering engines like gecko/mozserver etc with HTML 4 and CSS support to QNX 4.25 with Voyager 2.02 as the browser.
Will there be any limitation that can arise using Voyager 2.02 as the browser.
From my understanding, Voyager browser shall not impose any restriction. Browser can transparently support all the features that rendering engine provides.

Please comment on this.

Thanks in advance
hello
Senior Member
 
Posts: 101
Joined: Tue May 08, 2012 1:09 pm

Re: QNX versions

Postby maschoen » Tue Dec 16, 2014 9:00 pm

I think that's right. I believe the rendering engine does just what you would expect, renders a rectangle which Voyager then blit's into it's frame. The big question is, what does the interface between Voyager and it's server look like. You will either need information from QNX or reverse-engineeer it.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: QNX versions

Postby hello » Wed Dec 17, 2014 3:36 am

what does the interface between Voyager and it's server look like. You will either need information from QNX or reverse-engineeer it.

The interface means something like IPC. :?:
And could you please describe in this context what is meant to "reverse-engineer"
hello
Senior Member
 
Posts: 101
Joined: Tue May 08, 2012 1:09 pm

Re: QNX versions

Postby maschoen » Wed Dec 17, 2014 4:17 am

hello wrote:
what does the interface between Voyager and it's server look like. You will either need information from QNX or reverse-engineeer it.

The interface means something like IPC. :?:
And could you please describe in this context what is meant to "reverse-engineer"


Being QNX, the interface between Voyager and it's server very likely uses IPC, specifically message passing.
It is also possible that shared memory is used.

By reverse-engineering, I mean using the existing software to try to figure out how it works, so that you can substitute the Webkit engine for the existing Voyager/Spyglass engine. There is no straight forward way to go about doing this. That is why I suggested talking with QNX first to see if they will provide source code that might make the job much easier. You might use a debugger and step through the code, though I think this would be a painful way to go about it. Another idea would be to build a server and see what the messages being sent back and forth look like.

I don't want to be miss-understood here. I'm answering your questions in a logical manner and trying to be as helpful as possible, but I really believe that it is unlikely that you will succeed.

If you have the resources to attempt this, you probably have the resources to get QNX involved. If you don't then hopefully you are an extremely talented and persistent programmer.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Re: QNX versions

Postby hello » Wed Dec 17, 2014 10:27 am

Yes Maschoen, I got it.

Actually in QNX 6.3, we have Voyager browser 2.10 with mozserver as rendering engine. Voyager server(vserver) binary was also present in QNX 6.3.
So we thought we could easily configure Voyager browser to change mozserver with vserver using the command # voyager –P vserver
But the voyager browser prompt JavaScript Exception[Screen shot is attached]

We could configure any rendering engine for Voyager browser, but modification may be required in the interface between rendering engine/voyager browser. Is this understanding correct ?
Attachments
Javascript_error.png
JavaScript Exception
(11.12 KiB) Not downloaded yet
hello
Senior Member
 
Posts: 101
Joined: Tue May 08, 2012 1:09 pm

Re: QNX versions

Postby maschoen » Wed Dec 17, 2014 6:10 pm

hello wrote:Yes Maschoen, I got it.

Actually in QNX 6.3, we have Voyager browser 2.10 with mozserver as rendering engine. Voyager server(vserver) binary was also present in QNX 6.3.
So we thought we could easily configure Voyager browser to change mozserver with vserver using the command # voyager –P vserver
But the voyager browser prompt JavaScript Exception[Screen shot is attached]

We could configure any rendering engine for Voyager browser, but modification may be required in the interface between rendering engine/voyager browser. Is this understanding correct ?


Yes.
maschoen
QNX Master
 
Posts: 2644
Joined: Wed Jun 25, 2003 5:18 pm

Previous

Return to OpenQNX Site

Who is online

Users browsing this forum: No registered users and 1 guest