XPhoton OpenSrc anytime soon?

Hello,

I’m pulling this from a thread on Python 2.1.1 in qnxrtp.porting:

Frank wrote:

Given the fact that there is little development in Xphoton
and phinx, can QSSL release the source early? I checked
http://cvs.qnx.com > and they are not there yet. Does QSSL
consider them “core technology” and won’t release the source?

I second that!

Xphoton provides a means to augment Photon with the breath of X applications
(that’ll never be ported to Photon) without overshadowing (or replacing)
Photon.

Xphoton/gtwm is GREAT, but it needs work. QSSL should either work to make
Xphoton bullet proof, or work to make Xphoton open source. We haven’t seen
the fruit of either effort.

-david

“David S. Alessio” <david@NOsysrtimeSPAM.com> wrote in message
news:9qe293$34l$1@inn.qnx.com

Hello,

I’m pulling this from a thread on Python 2.1.1 in qnxrtp.porting:

Frank wrote:
Given the fact that there is little development in Xphoton
and phinx, can QSSL release the source early? I checked
http://cvs.qnx.com > and they are not there yet. Does QSSL
consider them “core technology” and won’t release the source?

I second that!

Xphoton provides a means to augment Photon with the breath of X
applications
(that’ll never be ported to Photon) without overshadowing (or replacing)
Photon.

Xphoton/gtwm is GREAT, but it needs work. QSSL should either work to make
Xphoton bullet proof, or work to make Xphoton open source. We haven’t
seen
the fruit of either effort.

I am not speaking for QNX, but I happen to know that they are working in
both directions (improving code and preparing it to open source). All good
things come to those who wait :wink:

  • igor

Igor Kovalenko wrote:

“David S. Alessio” <> david@NOsysrtimeSPAM.com> > wrote in message
news:9qe293$34l$> 1@inn.qnx.com> …

Hello,

I’m pulling this from a thread on Python 2.1.1 in qnxrtp.porting:

Frank wrote:

Given the fact that there is little development in Xphoton
and phinx, can QSSL release the source early? I checked
http://cvs.qnx.com > and they are not there yet. Does QSSL
consider them “core technology” and won’t release the source?

I second that!

Xphoton provides a means to augment Photon with the breath of X

applications

(that’ll never be ported to Photon) without overshadowing (or replacing)
Photon.

Xphoton/gtwm is GREAT, but it needs work. QSSL should either work to make
Xphoton bullet proof, or work to make Xphoton open source. We haven’t

seen

the fruit of either effort.


I am not speaking for QNX, but I happen to know that they are working in
both directions (improving code and preparing it to open source). All good things come to those who wait > :wink:

Wow … XPhoton compatible with 4.1 … that would be great!

Armin

  • igor

Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS. There are still some issues to be resolved though…

  • igor
    “Armin” <a-steinhoff@web.de> wrote in message news:3BCBFB07.8070109@web.de
    Igor Kovalenko wrote:


    I am not speaking for QNX, but I happen to know that they are working inboth directions (improving code and preparing it to open source). All good things come to those who wait :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

\

  • igor

<!doctype html public “-//w3c//dtd html 4.0 transitional//en”>

 
I agree XFree 4.1 compatibility would be nice, but if given the choice, I'd prefer the concentrated effort be first placed on making Xphoton solid.  Then begin to address 4.1 compatibility.

-david
 
 
 

Igor Kovalenko wrote:

Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS. There are still some issues to be resolved though... - igor "Armin" <> wrote in message news:<3BCBFB07.8070109@web.de>...Igor Kovalenko wrote:

I am not speaking for QNX, but I happen to know that they are working in
both directions (improving code and preparing it to open source). All good things come to those who wait :wink:
Wow  .... XPhoton  compatible with  4.1 ... that would be great!

Armin
 


  • igor



 

Acutally I am more interested in phinx, because I am using X as
my base GUI, and may need to run photon apps occasionally, via phinx.
Looks like phinx is in a even worse status than Xphoton. There is
only one beta release of phinx back in the rtp6.0 days, which may not
even install on rtp6.1. I guess QSSL is not working on it at all now.
Igor, when you said “they are working in both directions”, do you mean
Xphoton, or both xphoton and phinx? It will probably make more sense
to open source phinx first.

frank


Igor Kovalenko <kovalenko@home.com> wrote:

Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS. There are still some issues to be resolved though…

  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:



    I am not speaking for QNX, but I happen to know that they are working inboth directions (improving code and preparing it to open source). All good things come to those who wait > :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

  • igor

QSSL should concentrate their limited resources on phinx I think.
I don’t see any reasons to have Xphoton. You can achieve Xphoton
by running a VNC server (http://www.sourceforge.net/projects/openqnx)
and a Photon based VNC viewer talking to the VNC server locally.
http://www.nexwarecorp.com/Developers/repository.html#VNC
All the remaining Xphoton issues should probably be gone then.
thoughts?


Igor Kovalenko <kovalenko@home.com> wrote:

Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS. There are still some issues to be resolved though…

  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:



    I am not speaking for QNX, but I happen to know that they are working inboth directions (improving code and preparing it to open source). All good things come to those who wait > :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

  • igor

As I mentioned in another post in this thread, if you want a solid
“Xphoton” solution NOW, you should go VNC.

David Alessio <david.alessio@hsa.hitachi.com> wrote:

br>I agree XFree 4.1 compatibility would be nice, but if given the choice,
I’d prefer the concentrated effort be first placed on making Xphoton solid. 
Then begin to address 4.1 compatibility.
p>-david

As if hosting X applications isn’t inherently fat (and slow) enough, you
propose an additional layer of translation as a satisfactory solution ?

-----Original Message-----
From: <fliu@bb.vipstage.com> [mailto:fliu@bb.vipstage.com]
Posted At: Thursday, October 18, 2001 9:29 PM
Posted To: advocacy
Conversation: XPhoton OpenSrc anytime soon?
Subject: Re: XPhoton OpenSrc anytime soon?



QSSL should concentrate their limited resources on phinx I think.
I don’t see any reasons to have Xphoton. You can achieve Xphoton
by running a VNC server (http://www.sourceforge.net/projects/openqnx)
and a Photon based VNC viewer talking to the VNC server locally.
http://www.nexwarecorp.com/Developers/repository.html#VNC
All the remaining Xphoton issues should probably be gone then.
thoughts?


Igor Kovalenko <kovalenko@home.com> wrote:

Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS.
There are still some issues to be resolved though…


  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message
    news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:



    I am not speaking for QNX, but I happen to know that they are working
    inboth directions (improving code and preparing it to open source). All

good things come to those who wait :wink:

Wow … XPhoton compatible with 4.1 … that would be great!

Armin

  • igor

I don’t think Xphoton should go away. In fact i had some discussion with its
developer about its future and there appears to be a lot of potential to
improve things and even have Photon benefit from it. If only someone had
time and qualification to do that :wink:

  • igor

“Rennie Allen” <RAllen@csical.com> wrote in message
news:64F00D816A85D51198390050046F80C9011C66@exchangecal.hq.csical.com

As if hosting X applications isn’t inherently fat (and slow) enough, you
propose an additional layer of translation as a satisfactory solution ?

-----Original Message-----
From: <> fliu@bb.vipstage.com> > [mailto:> fliu@bb.vipstage.com> ]
Posted At: Thursday, October 18, 2001 9:29 PM
Posted To: advocacy
Conversation: XPhoton OpenSrc anytime soon?
Subject: Re: XPhoton OpenSrc anytime soon?



QSSL should concentrate their limited resources on phinx I think.
I don’t see any reasons to have Xphoton. You can achieve Xphoton
by running a VNC server (> http://www.sourceforge.net/projects/openqnx> )
and a Photon based VNC viewer talking to the VNC server locally.
http://www.nexwarecorp.com/Developers/repository.html#VNC
All the remaining Xphoton issues should probably be gone then.
thoughts?


Igor Kovalenko <> kovalenko@home.com> > wrote:
Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS.
There are still some issues to be resolved though…

  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message
    news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:


    I am not speaking for QNX, but I happen to know that they are working
    inboth directions (improving code and preparing it to open source). All
    good things come to those who wait > :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

\

  • igor
    \

Hello

We are working on a new Phinx as we speak. There are no plans to open
the source anytime soon. If you are having problems with it then
send them to me and I will see that they get addressed (if they haven’t
been already ).

Thanks
Rodney


fliu@bb.vipstage.com wrote:

QSSL should concentrate their limited resources on phinx I think.
I don’t see any reasons to have Xphoton. You can achieve Xphoton
by running a VNC server (> http://www.sourceforge.net/projects/openqnx> )
and a Photon based VNC viewer talking to the VNC server locally.
http://www.nexwarecorp.com/Developers/repository.html#VNC
All the remaining Xphoton issues should probably be gone then.
thoughts?



Igor Kovalenko <> kovalenko@home.com> > wrote:
Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS. There are still some issues to be resolved though…

  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:



    I am not speaking for QNX, but I happen to know that they are working inboth directions (improving code and preparing it to open source). All good things come to those who wait > :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

  • igor

Well, if the source isn’t going to be released soon, I wish you
would link phinx with the new XFree86 4 libraries. My assumption
is phinx users are those who use X Window as the base GUI. It is
only naturally that they will pick XFree86 4 over 3, for obvious
reasons.

Frank

On 19 Oct 2001, Gui Group wrote:

Hello

We are working on a new Phinx as we speak. There are no plans to open
the source anytime soon. If you are having problems with it then
send them to me and I will see that they get addressed (if they haven’t
been already ).

Thanks
Rodney


fliu@bb.vipstage.com > wrote:

QSSL should concentrate their limited resources on phinx I think.
I don’t see any reasons to have Xphoton. You can achieve Xphoton
by running a VNC server (> http://www.sourceforge.net/projects/openqnx> )
and a Photon based VNC viewer talking to the VNC server locally.
http://www.nexwarecorp.com/Developers/repository.html#VNC
All the remaining Xphoton issues should probably be gone then.
thoughts?


Igor Kovalenko <> kovalenko@home.com> > wrote:
Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS. There are still some issues to be resolved though…

  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:


    I am not speaking for QNX, but I happen to know that they are working inboth directions (improving code and preparing it to open source). All good things come to those who wait > :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

\

  • igor

    \

Rennie Allen <RAllen@csical.com> wrote:

As if hosting X applications isn’t inherently fat (and slow) enough, you

fat doesn’t necessarily mean slow, see my comments below.

propose an additional layer of translation as a satisfactory solution ?

VNC is very efficient. The VNC server is very “small” and runs as
a daemon. We have a server with more than ten copies running, serving
as a X application server for MS Windows clients. This is similiar
to the MS Windows Terminal Server, serving Unix/Citrix clients.

If this “additional layer” gives better performance and better support,
I would say this is a better solution.

To verify my suspicion, I did some performance tests today. “xbench”
is the program I used. The results are
XFree4.1 on RTP is a bit slower than on Linux, but close enough (within 10%).
This is probably due to the fact that there is no UDS support in RTP.

I have trouble getting Nexware’s VNC photon client to work (maybe they
can release the source, and other Photon experts can improve it) so
I ran my VNC X client for the test. I ran XFree4.1 as main GUI, one VNC
server in background, and then start X vnc client to talk to it and
run the xbench in this vnc window. The result is, for simple graphic
drawings, the speed is comparable to the XFree4.1 itself, but for
complex ones, it is getting slower. I know Xphoton is slower, but
am surprised to find the xbench in Xphoton is average 100X slower
than VNC tests, with some 10X slower, and other 200-300X slower.
I had to kill the xbench test in Xphoton when it goes to the complex
graphics, watching the slow drawing on the screen is a pain.

I can send you the test result files if anyone is interested, or
you can do the test yourself. It will be intesting if someone
can port xbench to Photon so that we can compare the result of
XFree4.1 and Photon itself. My guess is X will be faster. Photon
is designed to have a small footprint (that’s why you can run it
on a single floppy while this is impossible for X). I will
definitely recommend Photon if your application is for small/embedded.
On a desktop system, X will be a better choice: you will have more
readily available applications and it is IMO faster, maybe better
hardware support.

BTW, my test was on my IBM Thinkpad T21 laptop, Savage graphics
card, configured for 16bit color.

Frank



-----Original Message-----
From: <> fliu@bb.vipstage.com> > [mailto:> fliu@bb.vipstage.com> ]
Posted At: Thursday, October 18, 2001 9:29 PM
Posted To: advocacy
Conversation: XPhoton OpenSrc anytime soon?
Subject: Re: XPhoton OpenSrc anytime soon?



QSSL should concentrate their limited resources on phinx I think.
I don’t see any reasons to have Xphoton. You can achieve Xphoton
by running a VNC server (> http://www.sourceforge.net/projects/openqnx> )
and a Photon based VNC viewer talking to the VNC server locally.
http://www.nexwarecorp.com/Developers/repository.html#VNC
All the remaining Xphoton issues should probably be gone then.
thoughts?



Igor Kovalenko <> kovalenko@home.com> > wrote:
Yes Armin, new Xphoton source is basically a patch to Xfree 4.1 CVS.
There are still some issues to be resolved though…

  • igor
    “Armin” <> a-steinhoff@web.de> > wrote in message
    news:> 3BCBFB07.8070109@web.de> …
    Igor Kovalenko wrote:



    I am not speaking for QNX, but I happen to know that they are working
    inboth directions (improving code and preparing it to open source). All
    good things come to those who wait > :wink:
    Wow … XPhoton compatible with 4.1 … that would be great!

Armin

  • igor

<fliu@bb.vipstage.com> wrote in message news:9r04c6$881$1@inn.qnx.com

If this “additional layer” gives better performance and better support,
I would say this is a better solution.

If a given Ford runs better than a given Chevrolet, it does not necessarily
mean Ford in general is better. Might be just bad Chevrolet :wink:

run the xbench in this vnc window. The result is, for simple graphic
drawings, the speed is comparable to the XFree4.1 itself, but for
complex ones, it is getting slower. I know Xphoton is slower, but
am surprised to find the xbench in Xphoton is average 100X slower
than VNC tests, with some 10X slower, and other 200-300X slower.
I had to kill the xbench test in Xphoton when it goes to the complex
graphics, watching the slow drawing on the screen is a pain.

Current Xphoton unfortunately is designed that way. However, I believe there
could be MUCH better variant. I had some interesting discussion with
developer. If those ideas are implemented, Xphoton could be faster than VNC
and equal to X itself. It is still very low priority for QNX however,
because they do not believe into any good business with X.

I can send you the test result files if anyone is interested, or
you can do the test yourself. It will be intesting if someone
can port xbench to Photon so that we can compare the result of
XFree4.1 and Photon itself. My guess is X will be faster. Photon
is designed to have a small footprint (that’s why you can run it
on a single floppy while this is impossible for X). I will
definitely recommend Photon if your application is for small/embedded.
On a desktop system, X will be a better choice: you will have more
readily available applications and it is IMO faster, maybe better
hardware support.

X utilizes some acceleration features which Photon does not, indeed. It also
had 3D support (although I don’t think it would work with QNX without
patching). However, Photon has some advantages too. I don’t think X supports
croma-key or alpha-blending or anti-aliased fonts (not in stable version
anyway), correct me if I am out of date :wink:

Since most of software coming from QNX these days is Photon-oriented,
including system configuration tools and installer and help, people will
really want to use Photon. Then of course, there are people who want X apps
(including myself).

Given above, i think the best solution would be ‘best of both’. That could
be done by fitting both X and Photon into common framework with unified
driver model and unified window management system. Such hybrid would allow
to drive hardware using either Xfree or Photon native drivers, run both
types of apps simultaneously using either Photon or X window manager (any of
them). One may think i am dreaming, but technically it is possible.

  • igor

Igor Kovalenko <kovalenko@home.com> wrote:

and equal to X itself. It is still very low priority for QNX however,

“low priority” is actually the biggest concern I have.
If they could actively develop and support Xphoton, we will all
be happy :slight_smile: If they don’t, we will have to find better alternatives
(if any). As of now, VNC is faster than Xphoton. I won’t doubt
Xphoton will eventually get better, IF QSSL spends time/effort on it.

because they do not believe into any good business with X.

hope they can change their mindset.

X utilizes some acceleration features which Photon does not, indeed. It also
had 3D support (although I don’t think it would work with QNX without
patching). However, Photon has some advantages too. I don’t think X supports
croma-key or alpha-blending or anti-aliased fonts (not in stable version
anyway), correct me if I am out of date > :wink:

fyi:
Starting with version 4.0.2, XFree86 supports anti-aliased fonts.
Currently, most software has not been updated to take advantage of this
new functionality. However, Qt (the toolkit for the KDE desktop) does;
so if XFree86 4.0.2 is used (or higher), Qt 2.3 (or higher) and
KDE, all KDE/Qt applications can be made to use anti-aliased fonts.
(have you seen the screen snapshot of Konqueror with anti-aliased fonts?
it was posted on slashdot.)
gdkxft also gives anti-aliased fonts support for GTK+ 1.2

alpha-blending is in the Render extension, now a standard part of
every XFree86 server.

Since most of software coming from QNX these days is Photon-oriented,
including system configuration tools and installer and help, people will

That is the biggest pain we have :slight_smile: That’s why we hope to have a
good phinx release. In the meantime, you will understand why we
release all our XFree stuff in a tar.gz format.

really want to use Photon. Then of course, there are people who want X apps
(including myself).

Given above, i think the best solution would be ‘best of both’. That could
be done by fitting both X and Photon into common framework with unified
driver model and unified window management system. Such hybrid would allow
to drive hardware using either Xfree or Photon native drivers, run both
types of apps simultaneously using either Photon or X window manager (any of
them). One may think i am dreaming, but technically it is possible.

I like this dream. It is only of matter of resources to realize that.
Unfortunately , this is exactly what QSSL lacks.

\

  • igor