Using the Workspace tab page

The Workspace tab page in the System Tree displays the current workspace and all its targets. PowerScript targets display the library list for the target and all the objects in each PBL. Web targets display the contents of the root folder of the Web target. The Workspace tab page in the System Tree works like a tree view in the Library painter, but you can keep it open all the time to serve as the control center of the development environment.

As in the Library painter, you can set the root of the Workspace page to your computer’s root directory, the current selection, or any directory or library, as well as to the current workspace.

Working with targets To see the pop-up menu that lets you perform operations on a target such as search, build, and migrate, you must set the root of the System Tree or the view in the Library painter to the current workspace.

The following illustration shows a workspace with two PowerScript targets. The first PowerScript target, orders, has a second library in its library search path.

You can use the Workspace page as the hub of your PowerBuilder session. Pop-up menus let you build and deploy targets and open and edit any object. The following table lists the actions you can take on each item that displays on the Workspace page. You can also set properties for each item, choose which object types display in the tree view, change the root of the Workspace page, and reset the root to the current workspace.

**Table 1-1: Action items for objects in the System Tree**
Item	Menu action items
Workspace	New (opens New dialog box), Add Target, Open Workspace, Incremental Build, Full Build, Deploy, Debug, Run, Close, Show, Properties.
PowerScript target	New, Search, Incremental Build, Full Build, Migrate, Deploy, Debug, Run, Remove Target, Show, Properties.
Web or JSP target	New, New Folder, Import Files, Import Folder, Incremental Build, Full Build, Migrate Web, Deploy, Deploy to EP, Run, Remove Target, Show, Properties.
PBL	Delete, Remove Library, Search, Optimize, Print Directory, Build Runtime Library, Import, Import PB Extension, Show, Properties.
PBD	Remove Library, Show
PowerBuilder object	Edit, Edit Source, Inherit, Run/Preview, Copy, Move, Delete, Export, Regenerate, Search, Print, Properties. Edit Source is not available for project and proxy objects. Inherit and Run/Preview are available only for some object types. Source control items are available only if source control information is associated with the target.
Functions and events	Properties. The Properties dialog box shows the prototype of the function or event and its “signature.” The signature is a string that represents the argument types, return types, and passing style. You use this string when you write a PBNI extension that calls the function or event. For more information, see the PBNI Programmer’s Guide and Reference.
Web target object	Edit, Rename, Delete, Build, Properties.

Table 1-1: Action items for objects in the System Tree

Item

Menu action items

Workspace

New (opens New dialog box), Add Target, Open Workspace, Incremental Build, Full Build, Deploy, Debug, Run, Close, Show, Properties.

PowerScript target

New, Search, Incremental Build, Full Build, Migrate, Deploy, Debug, Run, Remove Target, Show, Properties.

Web or JSP target

New, New Folder, Import Files, Import Folder, Incremental Build, Full Build, Migrate Web, Deploy, Deploy to EP, Run, Remove Target, Show, Properties.

PBL

Delete, Remove Library, Search, Optimize, Print Directory, Build Runtime Library, Import, Import PB Extension, Show, Properties.

PBD

Remove Library, Show

PowerBuilder object

Edit, Edit Source, Inherit, Run/Preview, Copy, Move, Delete, Export, Regenerate, Search, Print, Properties.

Edit Source is not available for project and proxy objects. Inherit and Run/Preview are available only for some object types. Source control items are available only if source control information is associated with the target.

Functions and events

Properties.

The Properties dialog box shows the prototype of the function or event and its “signature.” The signature is a string that represents the argument types, return types, and passing style. You use this string when you write a PBNI extension that calls the function or event. For more information, see the PBNI Programmer’s Guide and Reference.

Web target object

Edit, Rename, Delete, Build, Properties.