Hi,
Is there any guide how to build a custom widget for Photon for QNXRT 6.1 and
integrate it into the Photon Bulder?
Is true, that custom widgets in PhAB are live?
Thanks for tips.
Marek Smrz
Marek Smrz <m.smrz@seznam.cz> wrote:
: Hi,
: Is there any guide how to build a custom widget for Photon for QNXRT 6.1 and
: integrate it into the Photon Bulder?
There will be an updated version of Building Custom Widgets in QNX 6.2. In
the meantime, you can refer to the Photon 1.14 version of the book (it’s
on the QDN website).
: Is true, that custom widgets in PhAB are live?
Not as far as I know. Someone else might know for sure.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
When should be QNX 6.2 released?
“Steve Reid” <stever@qnx.com> wrote in message
news:a1v57h$6ub$1@nntp.qnx.com…
Marek Smrz <> m.smrz@seznam.cz> > wrote:
: Hi,
: Is there any guide how to build a custom widget for Photon for QNXRT 6.1
and
: integrate it into the Photon Bulder?There will be an updated version of Building Custom Widgets in QNX 6.2.
In
the meantime, you can refer to the Photon 1.14 version of the book (it’s
on the QDN website).: Is true, that custom widgets in PhAB are live?
Not as far as I know. Someone else might know for sure.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
While we’re at it, when will 6.1.1 be released?
“Marek Smr¾” <m.smrz@seznam.cz> wrote in message
news:a2606c$sni$1@inn.qnx.com…
When should be QNX 6.2 released?
Hi Bill
6.1.1 has now become 6.2.
Bill Caroselli wrote:
While we’re at it, when will 6.1.1 be released?
“Marek Smr¾” <> m.smrz@seznam.cz> > wrote in message
news:a2606c$sni$> 1@inn.qnx.com> …When should be QNX 6.2 released?
\
Thank you Mr. Group.
My understanding was that 6.1.1 was due out very soon and just had bug fixes
and that 6.2 had some new enhancements/features. So I guess that we have to
wait for both in a single release.
–
Bill Caroselli – 1(626) 824-7983
Q-TPS Consulting
QTPS@EarthLink.net
“GUI Group” <gui@qnx.com> wrote in message news:3C4C5B7D.7040505@qnx.com…
Hi Bill
6.1.1 has now become 6.2.
Bill Caroselli wrote:
While we’re at it, when will 6.1.1 be released?
“Marek Smr¾” <> m.smrz@seznam.cz> > wrote in message
news:a2606c$sni$> 1@inn.qnx.com> …When should be QNX 6.2 released?
\
Steve Reid <stever@qnx.com> wrote:
: Marek Smrz <m.smrz@seznam.cz> wrote:
: : Is true, that custom widgets in PhAB are live?
: Not as far as I know. Someone else might know for sure.
One of the developers told me that it is true. Here’s what he sent to me:
This is what palette.def looks like on my machine:
l=ph,<Pt.h>:phrender,m
p=ptpalette,Basic Widgets
p=grpalette,Graphic Widgets
p=sppalette,Contributed Widgets
p=rtpalette,RealTime Widgets
l=PtWeb,<photon/PtWebClient.h>:ph
p=xpalette,Web Widgets
l=PtFlash,<photon/PtFlash.h>:ph,asound
p=fpalette,Flash Widgets
The “l=” lines are new; the rules are more or less like this:
Each “l=” line describes a library, and applies to the “p=” lines
that follow (up to the next “l=” line). In other words, the widgets
described in the palette file defined by a “p=” line are assumed to
be in the library described by the last “l=” line above. If there’s
no “l=” line above, the default is “l=ph,<Pt.h>”, I think.
The syntax is
l=,:
If PhAB needs to display a widget that is in this library, it will
add “lib” in front of , and “.so” after, and pass the
result to dlopen(). If that fails, or if dlsym() doesn’t find your
widget, PhAB will use a placeholder like it always does in Photon 1.
If PhAB decides that your app need this library, "-l " will
be added to the link line, and "#include " to one of the
PhAB-generated headers.
is a comma-separated list of s that must
also be described in their own “l=” lines (before they’re
referenced as dependencies). If a library has dependencies, PhAB
will make sure that they also get included, and in the right order.
Unless I’m mistaken, you can omit along with the comma if
there’s no header to be included, and along with the
colon if there are no dependencies other than “ph”. (The “ph” in
our palette.def is superfluous.)