Display PostScript: Difference between revisions

Content deleted Content added
Corrected spelling of "the lace of" to "the lack of"
Fixed a comma splice
Line 17:
*''[[programming language]] support'': DPS introduced the concept of a "[[pswrap]]", which allowed [[developer]]s to wrap PostScript code into a C language function which could then be called from an application.
 
DPS did not, however, add a windowing system. That was left to the implementation to provide, and DPS was meant to be used in conjunction with an existing windowing engine. This was often the [[X Window System]], and in this form Display PostScript was later adopted by companies such as [[International Business Machines|IBM]] and [[Silicon Graphics|SGI]] for their workstations. Often the code needed to get from an X window to a DPS context was much more complicated than the entire rest of the DPS interface,. thisThis greatly limited the popularity of DPS when any alternative was available.
 
On the NeXT system a completely new windowing engine was written, to take full advantage of their [[object oriented]] [[operating system]]. A number of commands were added to DPS to actually create the windows and to react to events, similar but simpler than [[NeWS]]. The single API made the writing of stuff at higher levels much easier and making NeXT one of the few systems to extensively use DPS. The user-space windowing system library [[NeXTStep]] used PostScript to draw items like titlebars and scrollers. This, in turn, made extensive use of pswraps, which were in turn wrapped in objects and presented to the programmer in object form.