Great Solution - DataWindow.net
Author: Teyy Burns terry@vbug.co.uk Graham Parker grahamp@vbug.co.uk
Vbug (http://www.vbug.co.uk)
introduction
Sybase's DataWindow patented technology has extended from the PowerBuilder to all development languages of Microsoft .NET Framework (part of the Microsoft Visual Studio 2003 development environment).
Visual Basic .NET, C #, developers of other .NET development languages now enjoy the efficient productivity of DataWindow to focus data (data-intersive) application development.
DataWindow.net allows developers to create custom controls on Window Forms of Visual Studio .NET. The DataWindow control in .NET provides a method similar to a method and event similar to a classic PowerBuilder. It allows .NET developers to perform data processing using the method and event of DataWindow.
DataWindow.NET supports most DataWindow performance styles in addition to Richtext and OLE, and also supports mainstream database drivers.
Other major new features of PB10:
Although there is no direct relationship with this experiment, you can get a comprehensive understanding of how DataWindow.NET can be suitable for DataWindow.net how the other major new features of 10.0 is read.
1, XML Web DataWindow
XML Web DataWindow is a DataWindow designed as separate content, layout and style. It has high performance, benefiting from the target performance and easy accessibility of style sheets.
It allows developers to use PBDom from defining XHTML generation in the DataWindow Drawboard or in PowerScript. In the next beta, developers will be able to define the DataWindow XHTML template and use these templates to export data. Abandon the control, properties, styles, and some additional tags of the DataWindow object, and use XHTML pages or slices, developers will benefit from these wider controls.
2, object-oriented building (through the PowerDesiner plugin)
By using the PowerDesiner plugin, PowerBuilder allows developers to model, code generation, reverse engineering and code navigation.
l Modeling and code generation: Developers create an object-oriented model OOM (Object-Oriented Model) to the model application in the PowerBuilder integration development environment IDE and generate code to run the application.
l Reverse Engineering: Developers can reverse engineering and generate class diagrams for existing PowerBuilder code and provide an overview of the generated code.
l Code Navigation: From the generated class diagram, developers navigate through class and object navigation and open the appropriate Powerbuilder drawing board by double-creating a specific object and pointing to a specific code.
3, in line with unified character coding standard --unicunicode enabling
PowerBuilder10 is a standard of Unicode character set. It allows you to enter, retrieve and display a variety of languages at the same page at the same page. Developing and running can run well in an English environment. A tool will be able to convert ANSI's PowerBuilder application to Unicode.
4, UDDI search
PowerBuilder10 provides a wizard to boot developers to locate web services and local services by using UDDI browsing in PowerScript applications and JSP pages. PowerBuilder developers can also create this UDDI search feature in their PowerBuilder application using UDDI PBNI extensions (PBUDDI100.PBD).
5, ADO.NET
ADO.NET has been provided by Powerbuilder10. It allows PowerBuilder applications to connect to the database using an ADO.NET, or in the same way, using your own or ODBC driver to connect to the database, perform database operations, table operations, data retrieval, and updates. Share with ADO.NET, DataWindow.net Applications A connection created with other .NET languages (such as C # or Visual Basic.net) for transaction management. Note that the functionality of ADO.NET is still under development. Some functions cannot be used before the next beta, and the test will also be postponed to the next test version. Latest requirements
Hardware requirements
l Supported operating system
Ø Windows 2000 SP4
Ø Windows XP SP1
l minimum / recommended hardware requirements
Ø 1 GB disk space
Ø 1GZ processor (recommended)
Ø 128M memory (recommended 256M)
Software requirements
l dw.net development
Ø Visual Studio.Net 2003
l dw.net
Ø .NET FRAMEWORK 1.1
l askASANYWHERE 9.0
l Microsoft acess and nothwind.mdb sample database
(--to be continued)
