PowerBuilder .NET 12.0 功能指南

3星 · 超过75%的资源需积分: 9 75 浏览量更新于2024-08-02 收藏 1.35MB PDF 举报

"PB-12.NET-Features-Guide 是 PowerBuilder .NET 12.0 版本的功能指南，该文档由 Sybase 公司于2009年6月发布，涵盖了针对 Sybase 软件及其后续版本的信息。内容可能随时变更，软件的使用或复制必须遵循许可协议的条款。用户可以通过指定电话或传真订购相关文档，国际用户需联系当地 Sybase 分支机构或分销商。未经许可，不得复制、传输或翻译此出版物的任何部分。" PowerBuilder .NET 12.0 是一个强大的开发工具，专为.NET框架设计，旨在帮助开发者构建企业级的桌面和Web应用程序。以下是一些关键功能和特性： 1. **.NET集成**：PowerBuilder 12.0 支持 Microsoft 的 .NET Framework，允许开发者利用 .NET 类库、服务和组件来开发应用程序。 2. **PowerScript与C#互操作性**：PowerBuilder 12引入了对C#语言的支持，用户可以在同一项目中混合使用PowerScript和C#代码，增强了代码的可移植性和可维护性。 3. **数据窗口增强**：数据窗口作为PowerBuilder的核心组件，在12.0版本中得到了进一步加强，支持更多的数据源类型，如SQL Server、Oracle等，并提供了更丰富的数据显示和编辑选项。 4. **Web应用开发**：通过使用Web窗体（Web Forms）和Web服务，PowerBuilder 12.0 可以创建基于Web的应用程序，支持AJAX技术，提供更好的用户体验。 5. **EAServer集成**：此版本的PowerBuilder可以更好地与Sybase EAServer集成，便于构建分布式和事务处理密集型的应用程序。 6. **对象向导和设计器**：提供了改进的对象向导和可视化设计器，帮助开发者更快地创建和管理对象，如窗口、菜单和事件处理。 7. **源代码控制集成**：支持多种源代码控制系统，如Visual SourceSafe和CVS，便于团队协作开发。 8. **性能优化**：在12.0版本中，对运行时性能进行了优化，提高了应用程序的响应速度和资源管理。 9. **错误处理和调试工具**：增强的调试器使得开发者能够更容易地识别和修复代码中的问题，提供断点设置、单步执行、变量查看等功能。 10. **国际化与本地化**：PowerBuilder 12.0 支持多语言开发，允许开发者轻松创建符合不同地区需求的应用程序。 11. **XML支持**：内置的XML支持使得数据交换和存储更为便捷，与Web服务和其他XML数据源的集成更加紧密。 12. **用户界面改进**：提供了更多自定义选项，使用户界面设计更加灵活，满足各种设计需求。 PowerBuilder .NET 12.0 功能指南是一个详尽的参考资料，涵盖了开发人员在利用PowerBuilder进行.NET开发时所需的所有关键信息和特性。对于希望在.NET环境中利用PowerBuilder高效开发的开发者来说，这份指南是不可或缺的工具。

Visual Studio shell feature Comment

Bookmark window You can enable and toggle bookmarks in painter Script views or in the XAML editor from

the Edit>Bookmarks cascading menu. You open the Bookmark window from the

View>Other Windows cascading menu.

Find and Replace The PowerBuilder .NET Find and Replace dialog box has tabs for Quick Find and Quick

Replace. It is available from the Edit>Find and Replace menu, and it allows you to

bookmark all items that match the Find string.

Layout view The painter Layout views use the Visual Studio designer and are closely associated with

the XAML editor. A magnifier bar in the upper left corner of each Layout view allows you

to change the magnification of objects and controls at design time without changing their

size at runtime. The close (x) icon at top right corner closes only the current tab of the

painter. If you click this icon while the Layout view is current, the Layout tab closes and

the Script (code-behind) view becomes current.

File editor The Open With dialog box replaces the File Editor in PowerBuilder Classic. It allows you

to select an editor for text in the Script views or XAML editor, or for current items in the

Solution Explorer. It also allows you to add editors that you want to use to view these files,

and set a different editor as the default file viewing selection. You can open this dialog box

from the View>Open With menu item.

Text formatting In PowerBuilder .NET, you can format text in painter Script views, in the XAML editor,

and in the Command window with the Edit>Advanced cascading menu items.

Task list Replaces the PowerBuilder Classic To-Do List. You can open the Task list by selecting the

View>Other Windows>Task List menu item.

Solution Explorer in PowerBuilder .NET

The Solution Explorer in PowerBuilder .NET functions in many ways like the System Tree in PowerBuilder Classic,

although for some functionality it appears more like the Solution Explorer in Microsoft Visual Studio.

The System Tree is typically the central point of action in PowerBuilder programming. It provides access to all the objects

in a PowerBuilder workspace.

The System Tree inPowerBuilder Classic displays objects in PowerBuilder libraries (PBLs), whereas in

PowerBuilder .NET, the PBLs have been converted to directories, and the Solution Explorer displays the contents of the

PBL directories only as separate files. The implementation of the System Tree as a Solution Explorer extension in

PowerBuilder .NET has or enables the following enhancements:

• Integration with the Visual Studio shell "Find" subsystem

• Provision of a more natural framework for opening editors

• Replacement of an ad-hoc framework for source control

• Provision of a more natural framework for workspace and project persistence

• Use of extensions for things like code refactoring

• Ability to drag and drop files from the Windows Explorer to targets and libraries

• Listings of all assemblies used by a target in a single References folder

• Ability to select a set of nodes to perform a common action, such as applying a comment or changing a common

writeable property

• Ability to host targets with multiple application objects and to set one of those objects as the current application

object.

However, there is also System Tree functionality that is no longer available with the file orientation of the

PowerBuilder .NET Solution Explorer. This includes:

• Navigation directly from the System Tree to nested controls or to specific functions and events in the Script Editor

• Display of the source control status of objects in the System Tree

Graphic User Interface

8 PowerBuilder .NET

Some functionality operates similarly in the PowerBuilder Classic System Tree and in the PowerBuilder .NET Solution

Explorer. Double-clicking an item in the Solution Explorer executes the default action for that item. Right-clicking an

item opens the pop-up menu for that item.

The Open and Open With pop-up menu items in the PowerBuilder .NET Solution Explorer deliver the same functionality

as the Edit and Edit Source pop-up menu item labels in the PowerBuilder Classic System Tree. However, the Open With

menu allows you to select the editor you want to use to view the object. The PowerBuilder .NET Solution Explorer also has

separate Open Layout and Open Script pop-up menu items for windows and visual user objects.

The following pop-up menu items on a PowerBuilder Classic System Tree object are not available in the Solution Explorer

in PowerBuilder .NET:

• PBNI Extensions

PowerBuilder .NET library nodes do not have the Import PowerBuilder Extension pop-up menu item for importing

PBNI extensions.

• Optimize

In PowerBuilder Classic, the Optimize menu item provides a way to clean up deleted objects and items that have been

accumulated in target PBLs. This is not necessary in PowerBuilder .NET.

• Migrate

The PowerBuilder Classic migrate capability assumes you can view a target in the System Tree that does not list

objects in an expanded PBL format. In PowerBuilder .NET, objects are always listed in an expanded format, so the

Migrate pop-up menu item is not necessary.

The other use of the Migrate pop-up menu is to regenerate Pcode from the sources for an object, and this is also not

needed in PowerBuilder .NET.

• Separate Library List and .NET Assemblies

Separate pop-up menu items for the library list and .NET assemblies are not needed inPowerBuilder .NETbecause of

their functional equivalence. Instead, a single pop-up menu item, "Library List", lists all PBLs and .NET assemblies in

PowerBuilder .NET targets.

• Regenerate

Like the Optimize and Migrate pop-up menu items, the Regenerate menu item is not needed in the PowerBuilder .NET

Solution Explorer because objects are always listed in an expanded format.

WPF Visual Controls in PowerBuilder

The system defined visual controls that you include in PowerBuilder .NET applications maintain the class hierarchy of

traditional PowerBuilder runtime controls, but the WPF controls are referenced in Extensible Application Markup

Language (XAML) files.

The following table maps PowerBuilder visual controls with their WPF equivalents:

Windows 32 Control WPF Control Equivalent

CommandButton and PictureButton Button

CheckBox CheckBox

DataWindow DataWindow WPF control

DatePicker DatePicker (from WPFToolkit)

DropDownListBox and DropDownPictureListBox ComboBox

EditMask EditMask WPF control

Graph Graph WPF control

GroupBox GroupBox

HProgressBar and VProgressBar ProgressBar

HScrollBar and VScrollBar ScrollBar

Graphic User Interface

PowerBuilder .NET Features Guide 9

Layouts

The Layouts tab is available with WPF window painters. It contains icons for

PresentationFramework layouts, like Canvas and Grid layouts, which control the sizes and positions

of elements in your WPF window.

DataWindow

Controls

This tab is available with PowerBuilder DataWindows. It contains icons for controls that you can add

to data forms.

See Visual Studio help for details about basic Toolbox usage and customization.

PB Object Outline

The PB Object Outline provides a convenient, single view for navigating and manipulating all the elements of a selected

object.

The view is available whenever a PowerBuilder object is open in the Designer.

To open the PB Object Outline, select an object in a PowerBuilder design window, then click View > PB Object

Outline .

The PB Object Outline shows the elements of the currently selected object, which can be organized into groups such as

events, controls, and functions.

If you select a different object, an open PB Object Outline changes to show the new object's elements. If no PowerBuild

object is selected, the window is empty except for a message that an outline is not available for the active object.

If the object represented in the outline is under source control, it has a source control icon.

Element icons

Each element in the PB Outline Tool has a static icon. For example, there are control, structure, and event icons. Some

elements, such as events, functions, .NET properties, and indexers, have an additional state icon.

.NET properties and indexer state icons have the same meaning as state icons in Event and Function lists. They reflect the

state of both get and set combined, because an element can represent both methods.

Navigating the outline

You can navigate the PB Outline by expanding and collapsing groups of elements. Individual elements expand to show

any attributes and subcomponents. For example, you can expand a control to list its events. Non-visual objects expand to

events and functions, and custom user objects can expand to controls.

You can also customize the way the outline displays and sorts items. The following navigation functions are available in

the PB Object Outline tool bar and menu, and in the view's context menu:

Sort Alphabetically (either ascending or descending)

Sort by Category

Sort by Type (element class or type)

Group by Category

Expand All

Collapse All

Changing sort and group settings in any PB Outline Tool view affects only the current view.

You can apply grouping and sorting independently. For example, if you disable Group by Category, the entire tree is

sorted. With Group by Category enabled, elements are sorted within each group.

Context menus vary for each element type. In addition to navigation functions, typical context menus also include

shortcuts for copying, pasting, deleting, adding, and editing items. For example, to edit a control, you can right-click it in

the outline and choose Go To Script. The control code opens in the Script view.

Graphic User Interface

PowerBuilder .NET Features Guide 11

Sort and display options for events and functions

You can set the following sort and display options for events and functions:

Group by Category

When enabled, (default), displays a heirarchical tree of elements. Sorting works within each

categeory. When disabled, displays a flat list of elements.

Show Ancestors

When enabled, includes ancestors for events, functions, indexers, and NET properties. When

disabled (the default) only locally scripted events or functions will be displayed for any of the

order schemes below.

Show Unscripted

WPF Events and

Functions

When enabled, includes events and functions for which no script has been created. When disabled

(default), only scripted events and functions are shown.

Problem Scripts

Rise to Top

When enabled (default), lists elements first whose scripts contain errors or warnings. When you

correct the propblem, the element reverts to its appropriate position in the list.

Choose one of the following order schemes:

•

Alphabetically

•

Scripted Local First

Lists local scripts first, followed by the remaining elements in alphabetical order.

•

Scripted Local, Scripted Ancestor, Unscripted (default)

Lists local scripts first, followed by ancestor scripts, and finally unscripted events or functions.

•

Scripted Anywhere, Unscripted

You can control these settings either globally or for the current PB Object Outline:

• Set the options globally in the Script Lists General page of the Options dialog box. You can apply different global

settings for these options to the System Tree, PB Object Outline, and the drop-down lists for functions and events in the

Script Editor.

• Within a PB Object Outline, right-click an event or function element and set the options in the context menu. Your

settings override those in the Options page.

Interface outlines

The PB Object Outline for interface objects shows indexers, events, functions, and .NET properties.

Interfaces can inherit from other interfaces. When an object implements other interfaces, those interfaces expand to the

same information as the interface object. You can expand each level recursively until there are no more implemented

interfaces.

Menu and global structure outlines

For menu and global structure objects, items appear in the PB Object Outline in the same order as they are defined in the

menu, unless you sort them alphabetically.

New Dialog Box

The New dialog box is a wizard that you can use to create most of the objects you need for your application.

Click File > New to open the New dialog box. Instead of the tabbed pages in PowerBuilder Classic, the New dialog box in

PowerBuilder .NET has a single page where you can browse all the available object types.

The New dialog box includes these main areas:

Target

Allows you to choose the target in which a selected object will be created. The field is available only if a

solution is currently open. The Target drop-down list is grayed when you select the Workspace item in the

New dialog box tree view, or when you select any of the items for creating new target.

Graphic User Interface

12 PowerBuilder .NET

剩余131页未读，继续阅读

yqq95

粉丝: 1
资源: 10

PowerBuilder .NET 12.0 功能指南

蓝牙低能耗Mesh网络结构详解与PB-ADV/PB-GATT传输机制

Sybase PB12.NET英文版特性指南

Pandorabots API模块pb-php的安装与使用

php-pb.github.io:来源做站点php-pb.net-php source site

PBL-Diff.Net_免费_pb_pbl_

trac-nghiem-online-asp.net-mvc：在线交易Nghiệm在线ASP.NET MVC

PB-API-Com.rar_PB 串口_PB-API-Com_pb_控件 串口

pb-language-pitfalls-Asaroz:GitHub Classroom创建的pb-language-pitfalls-Asaroz

pb-language-pitfalls-LeaCrazyBambi:GitHub Classroom创建的pb-language-pitfalls-LeaCrazyBambi

TC39xXA_PB-PB-v01_00-EN.pdf

最新资源

PB-API-Com.rar_PB 串口_PB-API-Com_pb_控件串口