Has (or is) anyone porting Gnome to RTP?
–
: damocles@TheNostromo.cx : Bruce Morrow, a man before and after his
time :
: “The Constitution shall never be construed to prevent the people of
the :
: United States who are peaceable citizens from keeping their own
arms.” :
: - Samuel Adams :
http://www.thenostromo.cx :
Randy Vice <damocles@thenostromo.cx> wrote:
: Has (or is) anyone porting Gnome to RTP?
Don’t know but you should be able too, in a pure X env.
Porting Gnome to Photon i.e. photon as the backengine is another thing.
Aussi haut que l’on soit assis, on n’est toujours assis que sur son cul !!!
Alain Magloire wrote:
Randy Vice <> damocles@thenostromo.cx> > wrote:
: Has (or is) anyone porting Gnome to RTP?
Don’t know but you should be able too, in a pure X env.
Porting Gnome to Photon i.e. photon as the backengine is another thing.
I take it that would be a multi man year project?
–
: damocles@TheNostromo.cx : Bruce Morrow, a man before and after his
time :
: “The Constitution shall never be construed to prevent the people of
the :
: United States who are peaceable citizens from keeping their own
arms.” :
: - Samuel Adams :
http://www.thenostromo.cx :
Yes we ported Gtk/GLib to RTP and it available as a package from our
repository.
http://www.nexwarecorp.com/repository It uses XPhoton, I don’t think a
conversion to Photon
has been started yet but we have talked about it a bit internally.
Jerry Kirk
Nexware Corp.
Previously, Jerry Kirk wrote in qdn.public.porting:
I don’t think a conversion to Photon
has been started yet but we have talked about it a bit internally.
I’ve been playing in my copious free time with porting gtk/glib to native photon, though most of the work so far (a few days worth at most) has been trying to understand the undocumented bits of talking to photon without going through Pt widgets.
–
Tony Mantler | Proud ---- Days since the last
QNX Consulting | of our | 27 |
tony@astra.mb.ca | Record ---- “Gerbil Incident”
Randy Vice <damocles@thenostromo.cx> wrote:
: Alain Magloire wrote:
:>
:> Randy Vice <damocles@thenostromo.cx> wrote:
:>
:> : Has (or is) anyone porting Gnome to RTP?
:>
:> Don’t know but you should be able too, in a pure X env.
:>
:> Porting Gnome to Photon i.e. photon as the backengine is another thing.
: I take it that would be a multi man year project?
I do not know, it really depends how X"ified" the underlying graphic
model is and how much entertwine the higher level libraries are.
For example doing a porting of tk(tcl is straight forward) is tedious and not
worth the effort(since Xphoton) because there is no clear separation between
X and the higher levels, and if you look at “porting” of tk to Win or Mac
you will see that they end up doing an X layer to satisfy tk. A good
level of abstraction would have make the porting much more appealing
and easier.
alain
Tony Mantler <tony@astra.mb.ca> wrote:
: Previously, Jerry Kirk wrote in qdn.public.porting:
:> I don’t think a conversion to Photon
:> has been started yet but we have talked about it a bit internally.
: I’ve been playing in my copious free time with porting gtk/glib to native
photon, though most of the work so far (a few days worth at most) has been
trying to understand the undocumented bits of talking to photon without going
through Pt widgets.
The Pg*(), Ph*(), Pf*() calls
alain
Previously, Alain Magloire wrote in qdn.public.porting:
Tony Mantler <> tony@astra.mb.ca> > wrote:
: Previously, Jerry Kirk wrote in qdn.public.porting:
:> I don’t think a conversion to Photon
:> has been started yet but we have talked about it a bit internally.: I’ve been playing in my copious free time with porting gtk/glib to native
photon, though most of the work so far (a few days worth at most) has been
trying to understand the undocumented bits of talking to photon without going
through Pt widgets.The Pg*(), Ph*(), Pf*() calls
Yeah, those ones. The documentation guys seem to have been glossing over a lot of them, and not covering some of them at all.
Not to mention there’s a few miscategorized and undocumented calls like PtGetWindowConfig(), which you only need when you don’t use Pt calls to make a window (it gets the window manager defaults for stuff like titlebar colour etc).
Tony Mantler | Proud ---- Days since the last
QNX Consulting | of our | 27 |
tony@astra.mb.ca | Record ---- “Gerbil Incident”
Tony Mantler <tony@astra.mb.ca> wrote:
It’s an interesting adventure to say the least. >
In the newest form of gtk/gdk the gdk is actually portable now and the gtk sits
right ontop. That is how they have gdk working on X11, Win32, BeOS, MacOS,
Linux FrameBuffer, and MicoWindows.
Good luck to you - I would help out but I am already overextended. Be sure to
post here when you get stuck, we (QNX) will help I am sure.
cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Chris McKillop wrote:
Tony Mantler <> tony@astra.mb.ca> > wrote:
It’s an interesting adventure to say the least. >
In the newest form of gtk/gdk the gdk is actually portable now and the gtk sits
right ontop.
The ported sources of GTK+ 1.2.8 and glib 1.2.8 are available at
http://sourceforge.net/projects/pyqnx
Hope it helps …
Armin
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
Chris McKillop wrote:
Tony Mantler <> tony@astra.mb.ca> > wrote:
It’s an interesting adventure to say the least. >
In the newest form of gtk/gdk the gdk is actually portable now and the gtk sits
right ontop.The ported sources of GTK+ 1.2.8 and glib 1.2.8 are available at
Ported to Photon native or Xphoton?
cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Chris McKillop wrote:
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
Chris McKillop wrote:Tony Mantler <> tony@astra.mb.ca> > wrote:
It’s an interesting adventure to say the least. >
In the newest form of gtk/gdk the gdk is actually portable now and the gtk sits
right ontop.The ported sources of GTK+ 1.2.8 and glib 1.2.8 are available at
Ported to Photon native or Xphoton?
Sorry, I’m a little bit off the topic … the sources at pyqnx are
ported for X/Xphoton.
However … porting GTK to native Photon is also a good idea, even
if it’s realisation isn’t simple.
Armin
Tony Mantler <tony@astra.mb.ca> wrote:
: Previously, Alain Magloire wrote in qdn.public.porting:
:> Tony Mantler <tony@astra.mb.ca> wrote:
:> : Previously, Jerry Kirk wrote in qdn.public.porting:
:> :> I don’t think a conversion to Photon
:> :> has been started yet but we have talked about it a bit internally.
:>
:> : I’ve been playing in my copious free time with porting gtk/glib to native
:> photon, though most of the work so far (a few days worth at most) has been
:> trying to understand the undocumented bits of talking to photon without going
:> through Pt widgets.
:>
:> The Pg*(), Ph*(), Pf*() calls
: Yeah, those ones. The documentation guys seem to have been glossing over a lot of them, and not covering some of them at all.
: Not to mention there’s a few miscategorized and undocumented calls like PtGetWindowConfig(), which you only need when you don’t use Pt calls to make a window (it gets the window manager defaults for stuff like titlebar colour etc).
: It’s an interesting adventure to say the least.
When you find this you should consider them as bugs and report them to
doc group.
.Aussi haut que l’on soit assis, on n’est toujours assis que sur son cul !!!
Alain Magloire <alain@qnx.com> wrote:
: Tony Mantler <tony@astra.mb.ca> wrote:
: : Yeah, those ones. The documentation guys seem to have been glossing over
: : a lot of them, and not covering some of them at all.
Actually, the developers have a say in what’s documented and in what detail.
: : Not to mention there’s a few miscategorized and undocumented calls like
: : PtGetWindowConfig(), which you only need when you don’t use Pt calls to
: : make a window (it gets the window manager defaults for stuff like titlebar
: : colour etc).
If something is in the wrong category, please let us know.
: : It’s an interesting adventure to say the least.
: When you find this you should consider them as bugs and report them to
: doc group.
If you find something in a header file and it isn’t documented, you should
usually assume that it’s for internal use only, deprecated, or unsupported.
Details of internal functions can change, so you use them at your own risk.
Steve Reid wrote:
Alain Magloire <> alain@qnx.com> > wrote:
: Tony Mantler <> tony@astra.mb.ca> > wrote:
: : Yeah, those ones. The documentation guys seem to have been glossing over
: : a lot of them, and not covering some of them at all.Actually, the developers have a say in what’s documented and in what detail.
: : Not to mention there’s a few miscategorized and undocumented calls like
: : PtGetWindowConfig(), which you only need when you don’t use Pt calls to
: : make a window (it gets the window manager defaults for stuff like titlebar
: : colour etc).If something is in the wrong category, please let us know.
: : It’s an interesting adventure to say the least. >
: When you find this you should consider them as bugs and report them to
: doc group.If you find something in a header file and it isn’t documented, you should
usually assume that it’s for internal use only, deprecated, or unsupported.
Details of internal functions can change, so you use them at your own risk.
How about _SC_PAGESIZE?
Is it deprecated, unsupported or for internal use only?
There is bunch of others in confname.h, many of them are very useful…
Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:
: How about _SC_PAGESIZE?
: Is it deprecated, unsupported or for internal use only?
: There is bunch of others in confname.h, many of them are very useful…
We were discussing Photon functions.
Steve Reid wrote:
Alain Magloire <> alain@qnx.com> > wrote:
: Tony Mantler <> tony@astra.mb.ca> > wrote:
: : Yeah, those ones. The documentation guys seem to have been glossing over
: : a lot of them, and not covering some of them at all.Actually, the developers have a say in what’s documented and in what detail.
Will we see some day the sources of Photon and its libs?
Or is the commitment to ‘open sources’ just a marketing joke ?
Armin
: : Not to mention there’s a few miscategorized and undocumented calls like
: : PtGetWindowConfig(), which you only need when you don’t use Pt calls to
: : make a window (it gets the window manager defaults for stuff like titlebar
: : colour etc).If something is in the wrong category, please let us know.
: : It’s an interesting adventure to say the least. >
: When you find this you should consider them as bugs and report them to
: doc group.If you find something in a header file and it isn’t documented, you should
usually assume that it’s for internal use only, deprecated, or unsupported.
Details of internal functions can change, so you use them at your own risk.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
Previously, Steve Reid wrote in qdn.public.porting:
Alain Magloire <> alain@qnx.com> > wrote:
: Tony Mantler <> tony@astra.mb.ca> > wrote:
: : Yeah, those ones. The documentation guys seem to have been glossing over
: : a lot of them, and not covering some of them at all.Actually, the developers have a say in what’s documented and in what detail.
Well, whoever’s making the documentation decisions is deciding to not document some of the stuff I need.
: : Not to mention there’s a few miscategorized and undocumented calls like
: : PtGetWindowConfig(), which you only need when you don’t use Pt calls to
: : make a window (it gets the window manager defaults for stuff like titlebar
: : colour etc).If something is in the wrong category, please let us know.
PtGetWindowConfig() is the only one that comes to mind atm.
: : It’s an interesting adventure to say the least. >
: When you find this you should consider them as bugs and report them to
: doc group.If you find something in a header file and it isn’t documented, you should
usually assume that it’s for internal use only, deprecated, or unsupported.
Details of internal functions can change, so you use them at your own risk.
Ok, how about this one: QNX4 Photon docs, bottom of “PhWindowOpen()” page (which is not present at all in the NTO docs), clearly documents the PhWindowInfo_t structure by saying “See PhWm.h for a description of PhWindowInfo_t”. This structure is rather vital to the functioning of the PhWindowOpen() call.
Also, the same page doesn’t at all touch on the importance of setting the data_len element of the PhRegion_t argument, without which the call will fail with a descriptive error of “0”. Instead, it states that the ‘parent’ member must be filled in, and the rest can be left to the default values.
Tony Mantler | Proud ---- Days since the last
QNX Consulting | of our | 27 |
tony@astra.mb.ca | Record ---- “Gerbil Incident”
Jerry Kirk wrote:
Yes we ported Gtk/GLib to RTP and it available as a package from our
repository.
http://www.nexwarecorp.com/repository > It uses XPhoton, I don’t think a
conversion to Photon
has been started yet but we have talked about it a bit internally.
OK, that’s two different sites for those to libs. Are those files
archives related or is this seperate porting efforts going on?
I’ve setup a rtpgnome ML (feel free to joint it at
http://www.thenostromo.cx/cgi-bin/lsg2.cgi) with the associated web
archive at http://thenostromo.cx/archives/rtpgnome/ in hope that will
help speed up porting of gnome to RTP by having devs touch base with
eachother.
–
: damocles@TheNostromo.cx : Bruce Morrow, a man before and after his
time :
: “The Constitution shall never be construed to prevent the people of
the :
: United States who are peaceable citizens from keeping their own
arms.” :
: - Samuel Adams :
http://www.thenostromo.cx :