This section describes the basic steps you follow when building a traditional client/server application. After completing step 1, you can define the objects used in your application in any order as you need them.
To build a traditional client/server
application:
Create the application (using a New wizard) and specify the library list for the application.
When you use a Start wizard, you create the Application object, which is the entry point into the application. The Application object contains the name of the application and specifies the application-level scripts.
See Chapter 5, “Working with Targets,” and Part 3, “Coding Fundamentals.”
Create windows.
Place controls in the window and build scripts that specify the processing that will occur when events are triggered.
Create menus.
Menus in your windows can include a menu bar, drop-down menus, cascading menus, and pop-up menus. You define the menu items and write scripts that execute when the items are selected.
Create user objects.
If you want to be able to reuse components that are placed in windows, define them as user objects and save them in a library. Later, when you build a window, you can simply place the user object on the window instead of having to redefine the components.
Create functions, structures, and events.
To support your scripts, you define functions to perform processing unique to your application and structures to hold related pieces of data. You can also define your own user events.
See Chapter 8, “Working with User-Defined Functions,” Chapter 9, “Working with User Events,” and Chapter 10, “Working with Structures.”
Create DataWindow objects.
Use these objects to retrieve data from the database, format and validate data, analyze data through graphs and crosstabs, and update the database.
See Part 6, “Working with DataWindows.”
Test and debug your application.
You can run your application at any time. If you discover problems, you can debug your application by setting breakpoints, stepping through your code, and looking at variable values during execution. You can also create a trace file when you run your application and use PowerBuilder’s profiling tools to analyze the application’s performance and logical flow.
See Chapter 32, “Debugging and Running Applications,” and Chapter 33, “Tracing and Profiling Applications.”
Prepare an executable.
When your application is complete, you prepare an executable version to distribute to your users.
This book tells you how to use PowerBuilder painters and tools.
For programming techniques for building applications and components for deployment to the .NET Framework, see Deploying Applications and Components to .NET.
For programming techniques for building applications and building clients and components for application servers, see Application Techniques.
For programming techniques related to DataWindows, including using the Web DataWindow, see the DataWindow Programmer’s Guide.
For information about JSP targets, see Working with JSP Targets.
