|
The document is in the process of being rewritten. Not that any
document will be able to detail all of the complexities of porting
an application to DECwindows. Porting of UIS to DECwindows is
generally a re-write of the application - or should be.
The new document will point out in a little more detail the harder
aspects of porting, provide a few translation routine sources and
point to all the right DECwindows/VMS documentation for reference
when doing various aspects of the port. It will be ready "real soon
now".
Note that UIS and DECwindows have fundamental design philosophy
differences that usually make porting a re-write. Near the top of
the list is that the application must be taught to repair window
damage from occlusion. If the application uses UIS display lists
and any of the features that that provides - then there is a lot of
work since there is no display list provided in the base system, the
application would need to be re-written for GKS or PHIGS or a custom
display list library written. Colormaps and some of the not-often-used
features suich as colormap segments are also a hassle. DOP's and QIO's
are not available. AST notification is possible as a doorbell, but
Xlib design is oriented towards a dispatch loop and not an AST event
driven model that UIS leans towards.
And finally, you have the "look & feel" issue to address. Do you want
it to integrate into the DECwindows/XUI L&F instead of the UIS
non look & feel?
My recomendation to customers wanting to know the complexities of
porting is to take a DECwindows course and then write a DECwindows
application FIRST - BEFORE trying to convert an existing UIS
application to DECwindows.
_Fred, VWS Migration
|