Sybase Technical Library - Product Manuals Home
[Search Forms] [Previous Section with Hits] [Next Section with Hits] [Clear Search] Expand Search

7. Product compatibilities [Table of Contents] 9. Migration information

Release Bulletin PowerBuilder Enterprise 9.0

[-] 8. Documentation updates and clarifications

8. Documentation updates and clarifications

8.1 Software components for saving DataWindows as PDF

8.1.1 Using the GNU Ghostscript distiller

Incorrect information appears in the section on page 486 of the User's Guide on saving the data in a DataWindow object as PDF using the distill method, and in the section on page 731of Application Techniques on deploying applications that use this feature. These sections incorrectly state that GNU Ghostscript files are installed with PowerBuilder in Sybase\Shared\PowerBuilder\gs7.05.

In order to use the SaveAs method to save data as PDF using the distiller, or to use the Save Rows As menu item in the DataWindow painter to save row data as PDF, you must first download and install GNU Ghostscript on your computer as described in the procedure that follows.

Your use of GNU Ghostscript is subject to the terms and conditions of the GNU General Public License (GPL). Please read the GPL before installing GNU Ghostscript on your computer. A copy of the GPL is available on the GNU Project Web server .

Save Rows As fails

To save as PDF in the DataWindow painter, select File>Save Rows As and select PDF as the Save As type. If you do not install GNU Ghostscript and use the default export properties, PowerBuilder displays a pop-up window notifying you that Save Rows As failed. If you install GNU Ghostscript and then change the name of the directory where GNU Ghostscript is installed, Save Rows As PDF fails silently.

To install GNU Ghostscript on the PowerBuilder development computer:
  1. Download gs705w32.exe from ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/gnu/gs705 into a temporary directory on your computer.

    You can find a list of alternative mirror sites on the GhostScript Web site .

  2. Run gs705w32.exe to install Ghostscript on your system.

    The default installation directory is C:\gs. You can select a different directory and/or choose to install shortcuts to the Ghostscript console and readme file.

  3. Add the gs7.05\bin directory to your system PATH environment variable in the Windows Control Panel. For example, if you installed Ghostscript in C:\gs, add the following to the system PATH environment variable:

    C:\gs\gs7.05\bin

After installing Ghostscript, you should read the readme.htm file in the gs7.05\doc directory to find out more about using Ghostscript and distributing it with your application.

The Adobe PostScript drivers used in this feature are installed in Sybase\Shared\PowerBuilder\drivers. For more information about downloading and redistributing Adobe printer drivers, see the downloads page on the Adobe Web site .

8.1.2 Using the Apache XSL-FO processor

On page 732 of Application Techniques, the section on deploying applications that use the ability to save files as PDF using XSL-FO and Java printing incorrectly states that some of the software components that must be deployed with these applications are provided as ZIP files in the Support directory. These components are available only in the Shared\PowerBuilder directory in your PowerBuilder installation.

For more information about downloading and redistributing the Apache XSL-FO processor (FOP), see the FOP page of the Apache XML Project Web site .

For more information about downloading and redistributing the Sun Java Runtime Environment (JRE) 1.4, see the J2SE 1.4 downloads page on the Sun Java Technology Web site .

8.2 Changing the Extend Ancestor Script attribute for object inheritance

The online Help and the lesson on creating menus in the PFC Programmer's Guide tutorial erroneously indicate that you can clear the Extend Ancestor Script menu item before you enter code or a comment in the Script view of a descendant object. For PowerBuilder 8 and higher, the code or comment must be entered in the descendant script before you can change the Extend Ancestor Script item. In the PFC tutorial, you must reverse steps 3 and 4 in the procedure entitled "Add and Modify Items."

8.3 Web DataWindow limitations

In addition to the limitations listed in Chapter 6 and Table 6-2 in the DataWindow Programmer's Guide, the following unsupported properties have been identified:

8.4 Implementing a PBNI marshaler extension

The second sentence in "Step 3: Implement the marshaler class" on page 51 of the PowerBuilder Native Interface Programmer's Guide and Reference should read as follows:

It also needs to provide a Destroy function and get the handle of the module.


7. Product compatibilities [Table of Contents] 9. Migration information