Qt for nto

that’s only partly true.

i saw qt/e qnx running on the embedded systems fair in nurnberg.
they had some game of live app running and could not show anything else, so
imho we can consider this an alpha stage.

from troll i received the following info:
We have a running prototype of QtE/QNX 3.0. However, at this point we

are not planning an official release unless we get significant customer

commitments.


“Frank Liu” <liug@mama.indstate.edu> schrieb im Newsbeitrag
news:a3l7i6$23m$1@inn.qnx.com

Frank Liu <> liug@mama.indstate.edu> > wrote:
Armin Steinhoff <a-steinhoff@web_.de> wrote:
Yes … but that means you would loose a lot of nice Photon features

therefore
embedded Qt for QNX6 makes no sense for me.

that’s probably why they didn’t release qt/embedded for QNX.

just curious, I sent an email to trolltech and got an reply today.
qt-embedded is fully ported to qnx6!! but it is not open-sourced.
(that’s probably why we didn’t see it in the downloadable source).
so the discussion is over for qt/embedded > :slight_smile:

frank

I got the same comment regarding “significant customer commitment” before
they will officially announce QtE/QNX.

Qt/X11 does run pretty good under XFree86 4.1/4.2 for QNX and it also runs
under XPhoton.

The reason for going with QtE/QNX would be the smaller foot print when
Photon and/or X11 aren’t necessary for a graphical application.


Jens

“Joerg Scherer” <joerg.schererNOSPAM@am3.com> wrote in message
news:a77s18$sv$1@inn.qnx.com

that’s only partly true.

i saw qt/e qnx running on the embedded systems fair in nurnberg.
they had some game of live app running and could not show anything else,
so
imho we can consider this an alpha stage.

from troll i received the following info:
We have a running prototype of QtE/QNX 3.0. However, at this point we

are not planning an official release unless we get significant customer

commitments.


“Frank Liu” <> liug@mama.indstate.edu> > schrieb im Newsbeitrag
news:a3l7i6$23m$> 1@inn.qnx.com> …
Frank Liu <> liug@mama.indstate.edu> > wrote:
Armin Steinhoff <a-steinhoff@web_.de> wrote:
Yes … but that means you would loose a lot of nice Photon features

therefore
embedded Qt for QNX6 makes no sense for me.

that’s probably why they didn’t release qt/embedded for QNX.

just curious, I sent an email to trolltech and got an reply today.
qt-embedded is fully ported to qnx6!! but it is not open-sourced.
(that’s probably why we didn’t see it in the downloadable source).
so the discussion is over for qt/embedded > :slight_smile:

frank

yes, i think that is a critical point, further:

  • “pretty good” is not good enough

  • who wants to carry around a networked windowing environment (X-Windows),
    when she doesn’t need it (slow and memory intensive)

  • xphoton is nice for tools and apps on a qnx-desktop, but in a production
    environment e.g. embedded target?

  • the major advantage imho is directly drawing to the framebuffer, compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself programming
motif-style again, which really sucks badly if you know the beauty of qt.



Jörg

“Jens H Jorgensen” <jhj@remove-nospam-videk.com> schrieb im Newsbeitrag
news:a78et6$df6$1@inn.qnx.com

I got the same comment regarding “significant customer commitment” before
they will officially announce QtE/QNX.

Qt/X11 does run pretty good under XFree86 4.1/4.2 for QNX and it also runs
under XPhoton.

The reason for going with QtE/QNX would be the smaller foot print when
Photon and/or X11 aren’t necessary for a graphical application.


Jens

“Joerg Scherer” <> joerg.schererNOSPAM@am3.com> > wrote in message
news:a77s18$sv$> 1@inn.qnx.com> …
that’s only partly true.

i saw qt/e qnx running on the embedded systems fair in nurnberg.
they had some game of live app running and could not show anything else,
so
imho we can consider this an alpha stage.

from troll i received the following info:
We have a running prototype of QtE/QNX 3.0. However, at this point we

are not planning an official release unless we get significant customer

commitments.


“Frank Liu” <> liug@mama.indstate.edu> > schrieb im Newsbeitrag
news:a3l7i6$23m$> 1@inn.qnx.com> …
Frank Liu <> liug@mama.indstate.edu> > wrote:
Armin Steinhoff <a-steinhoff@web_.de> wrote:
Yes … but that means you would loose a lot of nice Photon
features

therefore
embedded Qt for QNX6 makes no sense for me.

that’s probably why they didn’t release qt/embedded for QNX.

just curious, I sent an email to trolltech and got an reply today.
qt-embedded is fully ported to qnx6!! but it is not open-sourced.
(that’s probably why we didn’t see it in the downloadable source).
so the discussion is over for qt/embedded > :slight_smile:

frank

\

Joerg Scherer wrote:

yes, i think that is a critical point, further:

  • “pretty good” is not good enough
  • who wants to carry around a networked windowing environment (X-Windows),
    when she doesn’t need it (slow and memory intensive)

Did you use XFree86 4.1 with QNX6.1 ??

My impression is it isn’t slow and the memory footprint are in the range
of Photon.

  • xphoton is nice for tools and apps on a qnx-desktop, but in a production
    environment e.g. embedded target?

Not stable enough …

  • the major advantage imho is directly drawing to the framebuffer, compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself programming
motif-style again,

Why ? Qt works with XFree86.

Armin

which really sucks badly if you know the beauty of qt.

Jörg

“Jens H Jorgensen” <> jhj@remove-nospam-videk.com> > schrieb im Newsbeitrag
news:a78et6$df6$> 1@inn.qnx.com> …
I got the same comment regarding “significant customer commitment” before
they will officially announce QtE/QNX.

Qt/X11 does run pretty good under XFree86 4.1/4.2 for QNX and it also runs
under XPhoton.

The reason for going with QtE/QNX would be the smaller foot print when
Photon and/or X11 aren’t necessary for a graphical application.


Jens

“Joerg Scherer” <> joerg.schererNOSPAM@am3.com> > wrote in message
news:a77s18$sv$> 1@inn.qnx.com> …
that’s only partly true.

i saw qt/e qnx running on the embedded systems fair in nurnberg.
they had some game of live app running and could not show anything else,
so
imho we can consider this an alpha stage.

from troll i received the following info:
We have a running prototype of QtE/QNX 3.0. However, at this point we

are not planning an official release unless we get significant customer

commitments.


“Frank Liu” <> liug@mama.indstate.edu> > schrieb im Newsbeitrag
news:a3l7i6$23m$> 1@inn.qnx.com> …
Frank Liu <> liug@mama.indstate.edu> > wrote:
Armin Steinhoff <a-steinhoff@web_.de> wrote:
Yes … but that means you would loose a lot of nice Photon
features

therefore
embedded Qt for QNX6 makes no sense for me.

that’s probably why they didn’t release qt/embedded for QNX.

just curious, I sent an email to trolltech and got an reply today.
qt-embedded is fully ported to qnx6!! but it is not open-sourced.
(that’s probably why we didn’t see it in the downloadable source).
so the discussion is over for qt/embedded > :slight_smile:

frank

\

  • who wants to carry around a networked windowing environment
    (X-Windows),
    when she doesn’t need it (slow and memory intensive)

Did you use XFree86 4.1 with QNX6.1 ??

no, as i mentioned new to qnx. i downloaded your port from sourceforge, but

honestly i didn’t figure out how to get it up running. hint: short howto
would help big time :wink:
i’m really clueless. i think i would have to start up X instead at photon.
right?
i’m used to using X under several *nixen, which means either sysadmin has
done setting it up for me or (linux) having comfortable tools for having set
up my graphic card etc., fiddling with modlines manually scares me off,
honestly.
but maybe all this is easyly accomplished…

My impression is it isn’t slow and the memory footprint are in the range
of Photon.

this is astonishing to me! i would have guessed, that photon should by

nature be faster and be far less memory extensive.
can’t understand memory footprint being equal, as photon has no network
modell i think.
speed: should be a minor issue nowadays, one architekture could beat the
other by factors and it wouldn’t even be recogniseable by the user. on the
other hand: this surely is true for desktop systems, but on an embedded
target, where you typically have an older 1-2mb graphic-card?
an other point could be: while photon could in principle be faster than X, i
would guess xfree drivers are much better optimized than qssl drivers for
photon

  • the major advantage imho is directly drawing to the framebuffer,
    compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself
programming
motif-style again,

Why ? Qt works with XFree86.

all this is of minor concern to me right now, we won’t consider switching

for our current project, but in the future (read: next year) this could be
an option.
couldn’t get x running qt didn’t compile out of the box…
perhaps i should give it another try, if time permitts.

Jörg

Hi Joerg

Let me know if you need some help in getting XFree86 4.2 up and running
under QNX 6.1, and can give you an example XF86Config-4 and a startx script
that will make it work.

Regarding Qt/X11 it got the QT library and the basic tools (qmake, uic…)
compiled successfully. The compile did die during compilation of the
designer, and I have simply not had the time to look at that and I only need
the library and the basic tools.


Jens


“Joerg Scherer” <joerg.schererNOSPAM@am3.com> wrote in message
news:a7a31m$k1n$1@inn.qnx.com

  • who wants to carry around a networked windowing environment
    (X-Windows),
    when she doesn’t need it (slow and memory intensive)

Did you use XFree86 4.1 with QNX6.1 ??

no, as i mentioned new to qnx. i downloaded your port from sourceforge,
but
honestly i didn’t figure out how to get it up running. hint: short howto
would help big time > :wink:
i’m really clueless. i think i would have to start up X instead at photon.
right?
i’m used to using X under several *nixen, which means either sysadmin has
done setting it up for me or (linux) having comfortable tools for having
set
up my graphic card etc., fiddling with modlines manually scares me off,
honestly.
but maybe all this is easyly accomplished…

My impression is it isn’t slow and the memory footprint are in the range
of Photon.

this is astonishing to me! i would have guessed, that photon should by
nature be faster and be far less memory extensive.
can’t understand memory footprint being equal, as photon has no network
modell i think.
speed: should be a minor issue nowadays, one architekture could beat the
other by factors and it wouldn’t even be recogniseable by the user. on the
other hand: this surely is true for desktop systems, but on an embedded
target, where you typically have an older 1-2mb graphic-card?
an other point could be: while photon could in principle be faster than X,
i
would guess xfree drivers are much better optimized than qssl drivers
for
photon

  • the major advantage imho is directly drawing to the framebuffer,
    compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself
programming
motif-style again,

Why ? Qt works with XFree86.

all this is of minor concern to me right now, we won’t consider switching
for our current project, but in the future (read: next year) this could be
an option.
couldn’t get x running qt didn’t compile out of the box…
perhaps i should give it another try, if time permitts.

Jörg

Jens H Jorgensen <jhj@remove-nospam-videk.com> wrote:

Hi Joerg

Let me know if you need some help in getting XFree86 4.2 up and running
under QNX 6.1, and can give you an example XF86Config-4 and a startx script
that will make it work.

you don’t need an example XF86Config-4, “XFree86 -configure” will generate
one for you, for your graphics card/monitor. You can use the resulting
config file as base, modify as needed (such as pick another color depth
as default…).
as for “startx” script, i never had a need to tweak that. the default
one should just work.

btw Joerg, all your questions should have been answered in the mailing list.
subscribe/browse the mailing list for more info.

frank


Regarding Qt/X11 it got the QT library and the basic tools (qmake, uic…)
compiled successfully. The compile did die during compilation of the
designer, and I have simply not had the time to look at that and I only need
the library and the basic tools.


Jens



“Joerg Scherer” <> joerg.schererNOSPAM@am3.com> > wrote in message
news:a7a31m$k1n$> 1@inn.qnx.com> …

  • who wants to carry around a networked windowing environment
    (X-Windows),
    when she doesn’t need it (slow and memory intensive)

Did you use XFree86 4.1 with QNX6.1 ??

no, as i mentioned new to qnx. i downloaded your port from sourceforge,
but
honestly i didn’t figure out how to get it up running. hint: short howto
would help big time > :wink:
i’m really clueless. i think i would have to start up X instead at photon.
right?
i’m used to using X under several *nixen, which means either sysadmin has
done setting it up for me or (linux) having comfortable tools for having
set
up my graphic card etc., fiddling with modlines manually scares me off,
honestly.
but maybe all this is easyly accomplished…

My impression is it isn’t slow and the memory footprint are in the range
of Photon.

this is astonishing to me! i would have guessed, that photon should by
nature be faster and be far less memory extensive.
can’t understand memory footprint being equal, as photon has no network
modell i think.
speed: should be a minor issue nowadays, one architekture could beat the
other by factors and it wouldn’t even be recogniseable by the user. on the
other hand: this surely is true for desktop systems, but on an embedded
target, where you typically have an older 1-2mb graphic-card?
an other point could be: while photon could in principle be faster than X,
i
would guess xfree drivers are much better optimized than qssl drivers
for
photon

  • the major advantage imho is directly drawing to the framebuffer,
    compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself
programming
motif-style again,

Why ? Qt works with XFree86.

all this is of minor concern to me right now, we won’t consider switching
for our current project, but in the future (read: next year) this could be
an option.
couldn’t get x running qt didn’t compile out of the box…
perhaps i should give it another try, if time permitts.
\

That is true that XFree86 -configure will create a XF86Config-4. That is
where my sample XF86Config-4 comes from.

As for startx - I included startup of devi-hirun so that you get your mouse
device.


Jens
<fliu@bb.vipstage.com> wrote in message news:a7d3ii$qqp$1@inn.qnx.com

Jens H Jorgensen <> jhj@remove-nospam-videk.com> > wrote:
Hi Joerg

Let me know if you need some help in getting XFree86 4.2 up and running
under QNX 6.1, and can give you an example XF86Config-4 and a startx
script
that will make it work.

you don’t need an example XF86Config-4, “XFree86 -configure” will generate
one for you, for your graphics card/monitor. You can use the resulting
config file as base, modify as needed (such as pick another color depth
as default…).
as for “startx” script, i never had a need to tweak that. the default
one should just work.

btw Joerg, all your questions should have been answered in the mailing
list.
subscribe/browse the mailing list for more info.

frank


Regarding Qt/X11 it got the QT library and the basic tools (qmake,
uic…)
compiled successfully. The compile did die during compilation of the
designer, and I have simply not had the time to look at that and I only
need
the library and the basic tools.


Jens


“Joerg Scherer” <> joerg.schererNOSPAM@am3.com> > wrote in message
news:a7a31m$k1n$> 1@inn.qnx.com> …

  • who wants to carry around a networked windowing environment
    (X-Windows),
    when she doesn’t need it (slow and memory intensive)

Did you use XFree86 4.1 with QNX6.1 ??

no, as i mentioned new to qnx. i downloaded your port from sourceforge,
but
honestly i didn’t figure out how to get it up running. hint: short
howto
would help big time > :wink:
i’m really clueless. i think i would have to start up X instead at
photon.
right?
i’m used to using X under several *nixen, which means either sysadmin
has
done setting it up for me or (linux) having comfortable tools for
having
set
up my graphic card etc., fiddling with modlines manually scares me off,
honestly.
but maybe all this is easyly accomplished…

My impression is it isn’t slow and the memory footprint are in the
range
of Photon.

this is astonishing to me! i would have guessed, that photon should by
nature be faster and be far less memory extensive.
can’t understand memory footprint being equal, as photon has no network
modell i think.
speed: should be a minor issue nowadays, one architekture could beat
the
other by factors and it wouldn’t even be recogniseable by the user. on
the
other hand: this surely is true for desktop systems, but on an embedded
target, where you typically have an older 1-2mb graphic-card?
an other point could be: while photon could in principle be faster than
X,
i
would guess xfree drivers are much better optimized than qssl drivers
for
photon

  • the major advantage imho is directly drawing to the framebuffer,
    compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself
programming
motif-style again,

Why ? Qt works with XFree86.

all this is of minor concern to me right now, we won’t consider
switching
for our current project, but in the future (read: next year) this could
be
an option.
couldn’t get x running qt didn’t compile out of the box…
perhaps i should give it another try, if time permitts.


\

Jens H Jorgensen <jhj@remove-nospam-videk.com> wrote:

As for startx - I included startup of devi-hirun so that you get your mouse
device.

I don’t know where is a good place to put devi-hirun other than running
it manually. putting in startx is probably not a good idea because
re-startx will cause multiple copies, unless you automatically kill
devi-hirun after you stop X. things are getting complicated, so
I just do devi-hirun manually once. or kill/restart it if you ever
go to photon once.

frank

thanks for your help to everybody!

i wasn’t aware, that qnx configuration is included in vanilla xfree4.2
sources.

seems to compile flawlessly out of the box, which it does right now, so i’ll
see you in a few hours :wink:



best regards

Jörg

<fliu@bb.vipstage.com> schrieb im Newsbeitrag
news:a7d3ii$qqp$1@inn.qnx.com

Jens H Jorgensen <> jhj@remove-nospam-videk.com> > wrote:
Hi Joerg

Let me know if you need some help in getting XFree86 4.2 up and running
under QNX 6.1, and can give you an example XF86Config-4 and a startx
script
that will make it work.

you don’t need an example XF86Config-4, “XFree86 -configure” will generate
one for you, for your graphics card/monitor. You can use the resulting
config file as base, modify as needed (such as pick another color depth
as default…).
as for “startx” script, i never had a need to tweak that. the default
one should just work.

btw Joerg, all your questions should have been answered in the mailing
list.
subscribe/browse the mailing list for more info.

frank


Regarding Qt/X11 it got the QT library and the basic tools (qmake,
uic…)
compiled successfully. The compile did die during compilation of the
designer, and I have simply not had the time to look at that and I only
need
the library and the basic tools.


Jens


“Joerg Scherer” <> joerg.schererNOSPAM@am3.com> > wrote in message
news:a7a31m$k1n$> 1@inn.qnx.com> …

  • who wants to carry around a networked windowing environment
    (X-Windows),
    when she doesn’t need it (slow and memory intensive)

Did you use XFree86 4.1 with QNX6.1 ??

no, as i mentioned new to qnx. i downloaded your port from sourceforge,
but
honestly i didn’t figure out how to get it up running. hint: short
howto
would help big time > :wink:
i’m really clueless. i think i would have to start up X instead at
photon.
right?
i’m used to using X under several *nixen, which means either sysadmin
has
done setting it up for me or (linux) having comfortable tools for
having
set
up my graphic card etc., fiddling with modlines manually scares me off,
honestly.
but maybe all this is easyly accomplished…

My impression is it isn’t slow and the memory footprint are in the
range
of Photon.

this is astonishing to me! i would have guessed, that photon should by
nature be faster and be far less memory extensive.
can’t understand memory footprint being equal, as photon has no network
modell i think.
speed: should be a minor issue nowadays, one architekture could beat
the
other by factors and it wouldn’t even be recogniseable by the user. on
the
other hand: this surely is true for desktop systems, but on an embedded
target, where you typically have an older 1-2mb graphic-card?
an other point could be: while photon could in principle be faster than
X,
i
would guess xfree drivers are much better optimized than qssl drivers
for
photon

  • the major advantage imho is directly drawing to the framebuffer,
    compare
    qt/e to qt/x11 on linux, main purpose: avoiding X

my personal point of view:
i’m new to qnx, i used xt/motif and qt before. now i find myself
programming
motif-style again,

Why ? Qt works with XFree86.

all this is of minor concern to me right now, we won’t consider
switching
for our current project, but in the future (read: next year) this could
be
an option.
couldn’t get x running qt didn’t compile out of the box…
perhaps i should give it another try, if time permitts.


\

Jens H Jorgensen <jhj@videk.com> wrote:

I managed to compile Qt 3.0.0 (static library) for XPhoton fairly easy. I
think if I spend a little more time I would have been able to complile to
dynamic linked libraries also.

Most of the examples ran fine - except some minor problem with some of the
icons and the grid in Qt Designer.

Do you have this problem with the binary version from openqnx?

Frank

Hi Frank

The binary verison from openqnx (http://sourceforge.net/projects/openqnx/)
works works very well. Designer does not experience the below mentioned
problems, but it does crash pretty easily. But it is not a big deal because
I don’t need to use designer under QNX.

Again thanks for your work on supporting Qt for QNX - I almost gave up on
getting the shared library build working under QNX.

Jens


<fliu@bb.vipstage.com> wrote in message news:a8dan8$4b3$1@inn.qnx.com

Jens H Jorgensen <> jhj@videk.com> > wrote:
I managed to compile Qt 3.0.0 (static library) for XPhoton fairly easy.
I
think if I spend a little more time I would have been able to complile
to
dynamic linked libraries also.

Most of the examples ran fine - except some minor problem with some of
the
icons and the grid in Qt Designer.

Do you have this problem with the binary version from openqnx?

Frank

Jens H Jorgensen <jhj@remove-nospam-videk.com> wrote:

Hi Frank

The binary verison from openqnx (> http://sourceforge.net/projects/openqnx/> )
works works very well. Designer does not experience the below mentioned
problems, but it does crash pretty easily. But it is not a big deal because

I just did a re-release of the binary on openqnx site, hope it
will fix those designer crashing problems. the designer plugins
should be built properly this time.
Please download again and give it a try.

I don’t need to use designer under QNX.

Again thanks for your work on supporting Qt for QNX - I almost gave up on
getting the shared library build working under QNX.

You are quite welcome. Now that we have Qt ported, people should
be able to start porting things like KDE, Konqueror browser,
KDeveloper IDE, Koffice, etc.
Also, it will also developers to write portable codes …

Frank



Jens



fliu@bb.vipstage.com> > wrote in message news:a8dan8$4b3$> 1@inn.qnx.com> …
Jens H Jorgensen <> jhj@videk.com> > wrote:
I managed to compile Qt 3.0.0 (static library) for XPhoton fairly easy.
I
think if I spend a little more time I would have been able to complile
to
dynamic linked libraries also.

Most of the examples ran fine - except some minor problem with some of
the
icons and the grid in Qt Designer.

Do you have this problem with the binary version from openqnx?

Frank

Jens H Jorgensen wrote:

Hi Frank

The binary verison from openqnx (> http://sourceforge.net/projects/openqnx/> )
works works very well. Designer does not experience the below mentioned
problems, but it does crash pretty easily. But it is not a big deal because
I don’t need to use designer under QNX.

The designer doesn’t work stable with XPhoton …

Again thanks for your work on supporting Qt for QNX - I almost gave up on
getting the shared library build working under QNX.

There are in the meantime shared versions of Qt 2.3.2 and Qt 3.0.3 at
openqnx. Also available are two interesting sets of visulaization
widgets. Have a look to:

http://qwt.sourceforge.net/screenshots.html (qwt/LGPL)
http://qtai.sourceforge.net/ (Qt AI/ GPL)

For reading the Qt doc … download the small browser ‘dillo’ (200k,
supports PNG picts)

Armin

Armin Steinhoff <a-steinhoff@web_.de> wrote:

For reading the Qt doc … download the small browser ‘dillo’ (200k,
supports PNG picts)

qt3 comes with a program called “assistant”. If you install the binary
from openqnx, it is along with all other executables in
/opt/X11R6/qt3/bin

“assistant” is qt’s document browser, real nice.

Frank

<fliu@bb.vipstage.com> wrote in message news:a8e7t8$m4h$1@inn.qnx.com

Jens H Jorgensen <> jhj@remove-nospam-videk.com> > wrote:
Hi Frank

The binary verison from openqnx
(> http://sourceforge.net/projects/openqnx/> )
works works very well. Designer does not experience the below mentioned
problems, but it does crash pretty easily. But it is not a big deal
because

I just did a re-release of the binary on openqnx site, hope it
will fix those designer crashing problems. the designer plugins
should be built properly this time.
Please download again and give it a try.

Is this binaries built with XFree libraries from openqnx, or as default on

QNX 6.1 - with XPhoton libraries ?

Sergey V. Sobolev <ssobolev@volgasoft.net> wrote:

fliu@bb.vipstage.com> > wrote in message news:a8e7t8$m4h$> 1@inn.qnx.com> …
Jens H Jorgensen <> jhj@remove-nospam-videk.com> > wrote:
Hi Frank

The binary verison from openqnx
(> http://sourceforge.net/projects/openqnx/> )
works works very well. Designer does not experience the below mentioned
problems, but it does crash pretty easily. But it is not a big deal
because

I just did a re-release of the binary on openqnx site, hope it
will fix those designer crashing problems. the designer plugins
should be built properly this time.
Please download again and give it a try.

Is this binaries built with XFree libraries from openqnx, or as default on
QNX 6.1 - with XPhoton libraries ?

with xfree86 4.2 as found at openqnx site.

Armin Steinhoff wrote:

[ clip …]

There are in the meantime shared versions of Qt 2.3.2 and Qt 3.0.3 at
openqnx. Also available are two interesting sets of visulaization
widgets. Have a look to:

http://qwt.sourceforge.net/screenshots.html > (qwt/LGPL)
http://qtai.sourceforge.net/ > (Qt AI/ GPL)

For all donwloaded the broken QtAI archive … it’s corrected now

Armin