|
1.
DataWindow .NET
PowerBuilder's patented DataWindow
technology is extended (in a C# interface) to
all languages in the Microsoft .NET FrameWork.
Visual Basic .NET, C#, and other .NET language developers
can enjoy the DataWindow's high productivity for data-intensive
application development. PowerBuilder developers
will be able to continue to do so in .NET environment.
DataWindow .NET 1.0 will be part of the PowerBuilder
10.0 release.
DataWindow .NET allows developers
to create custom controls on .NET Windows forms.
The DataWindow control in .NET exposes a similar
set of methods and events as is available in PowerBuilder.
It allows .NET developers to use DataWindow methods
and events when programming data manipulation.
DataWindow .NET supports most of the DataWindow
presentation styles except Rich Text and OLE,
and it supports major database drivers.
2.
XML Web
DataWindow
The XML Web DataWindow is designed
to separate the content, layout, and style of
the DataWindow on the Web. Its benefits include
improved performance, targeted presentation using
style sheets, and accessibility (Section 508). It
allows developers to customize XHTML generation in
the DataWindow Painter or in PowerScript using PBDOM.
In the next beta release, developers will be
able to define DataWindow XHTML templates and
export data using these templates. The developer
benefits from broader control over how a DataWindow
object's controls, properties, and styles, along
with additional markup, render to XHTML pages
or fragments.
3.
Object-Oriented
Modeling (via PowerDesigner plug-in)
With PowerDesigner as a plug-in,
PowerBuilder allows developers to do modeling,
code generation, reverse engineering, and code
navigation in an iterative manner.
- Modeling and code generation:
the developer can create an OOM (Object-Oriented
Model) in the PowerBuilder IDE to model applications
and then generate the code to run the applications.
- Reverse engineering: the developer
can reverse-engineer existing PowerBuilder
code and generate class diagrams to provide an overview
of the code.
- Code navigation: from generated
class diagrams, developers can navigate through
classes and objects and open the appropriate
PowerBuilder painter by double-clicking a specific
object and pointing to specific code.
With these capabilities, PowerBuilder
allows developers to iteratively design and
code complex applications. For maintenance and
enhancement of existing PowerBuilder applications,
these capabilities provide developers with tools to
understand the code and the structure of the application
and make modifications.
4.
Unicode
enabling
PowerBuilder 10 is Unicode enabled.
It allows users to input, retrieve, and display
multiple languages in Unicode on the same page
at the same time. Development and runtime applications
work as usual in an English environment. A migration
tool will be provided to migrate ANSI PowerBuilder
applications to Unicode.
5.
UDDI search
PowerBuilder 10 provides wizards
to guide developers through using UDDI browsing
to locate Web services and consuming the located services
in both PowerScript applications and JSP pages. PowerBuilder
developers can also build this UDDI searching
capability into their PowerBuilder applications
using the UDDI PBNI extension (pbuddi100.pbd).
6.
ADO.NET
ADO.NET is being developed for
the PowerBuilder 10 release. It allows PowerBuilder
applications to use ADO.NET, in the same way that
they use native or ODBC drivers, to connect to various
databases, perform database operations and table
operations, and do data retrieval and update.
With ADO.NET, DataWindow .NET applications will
be able to share a connection created by other
.NET languages (such as Visual Basic .NET or
C#) for transaction management.
Please note that the ADO.NET feature
is still under development. Some of its functions
will not be available until the next Beta and
testing should be deferred to the next Beta.
7.
Other
enhancements
Web Services deployment: PowerBuilder
10 will allow developers to directly deploy
components (NVOs) as Web services in EAServer
5.0. Complex data types are supported in this release.
Profile-based configuration
for EAServer and database: If developers need
to change the EAServer host or database used in a
JSP target, they can make the change in the EAServer
or database profile, do a full build, and redeploy
the JSP target to have the change take effect.
Additional enhancements, including Section 508
accessibility, are being developed for release
in the next Beta.
|
