Applying a New UI Theme to Your Application

This tutorial is an update to the 2019 tutorial. If you have zero experience with the UI Theme feature, please first follow our Quick Start tutorial. If you are ready to gain a comprehensive understanding of this feature and dive deeper into UI Theme settings, then please proceed with this updated tutorial.

Starting from PowerBuilder 2019, Appeon added the UI theme feature to PowerBuilder so that developers can codelessly control how commonly-used controls and objects render during application runtime.

Implementing OAuth 2.0 Authorization with PowerBuilder 2019 R2

Introduction

PowerBuilder supports getting secured data from the OAuth 2.0 authorization server. The Bearer access token is supported, and the following grant types are supported:

• Authorization Code
• Implicit Flow
• Client Credentials
• Extension (or Refresh Token)
• Resource Owner Password

This document provides an example on how to set up OAuth 2.0 authorization workflow using the Authorization Code grant type in a PowerBuilder application.

How to Define Events for RibbonBar Controls

Learning to define user events for items in the RibbonBar control feels like a lot of trial and error.
Different items support different events. Same event type requires different parameters.
My aim with this article is to take "... and error" out of your RibbonBar coding.
For each ribbon item type you get user event definitions that work.

Each ribbon item has its own XML element (here: Print Title is a CheckBox).
Each item binds specific user events via properties (here: Clicked on CheckBox binds to ue_PrintTitle)
Each user event must have the correct parameter list (here: Clicked event for CheckBox always requires al_handle while no other parameters allowed)
Each item type has its own PowerScript class and functions to obtain the object (here: Obtain class = RibbonCheckBoxItem via function GetCheckBox)
 

Enhanced JSON handling

Why enhance JSON handling?

Reading and writing JSON in PowerBuilder is simple using PowerBuilder’s RESTClient object; however, the JSON needs to be in a two-dimensional format. But there are times when the JSON you are working with has multiple nested levels, especially if working with data from an external interface not under your control.

The PowerBuilder objects JSONParser and JSONGenerator can be used to parse or generate such JSON with multiple nested levels.  However, a key caveat is that the JSONParser and JSONGenerator require the JSON data to be accessed through “handles”.  For example, the getItemObject() returns a handle rather than the full JSON object.  Compared to an object-based approach, this handle-based approach requires more coding by the developer.

REST Enhancements in PowerBuilder 2019

REST support was added to PowerBuilder in 2017 R2 and enhanced in 2017 R3.  PowerBuilder 2019 contains additional significant enhancements to REST support, including the following:

• RetrieveOne method – For REST methods return one row
• Submit method - sends request and returns data in one operation
• SetRequestHeader behavior modified
• GZIP compression handled automatically
• Send[Method]Request, where method can be Get, Put, Post, Patch, Delete
• Get and Set OAuth token methods
• Get and set JWT token methods

JSON Enhancements in PowerBuilder 2019

Support for the JSON format was added in the PowerBuilder 2017 R2 release and then enhanced in 2017 R3.  PowerBuilder 2019 contains even more enhancements in this area, particularly with regard to:

1. Enhanced JSONParser
2. Enhanced JSONPackage
3. DataWindows Row Level Import/Export
4. New ModelStore JSON Format

Pushing large projects to Git server

Symptom

When you push your repository from PowerBuilder IDE to your Git server for the first time after you do the Add to Source Control, it may fail when the size of your source code is large and/or your network is slow. 

Using Autoincrementing Columns from a PowerBuilder DataWindow

Note:  This blog entry is basically the written version of a video I did for the SAP Database and Technology Academy.  You can either watch the video or read the blog entry, or both if you're so inclined.

Using PowerBuilder 2019 R2 with Azure DevOps Server (TFS) 2019

For many PowerBuilder users who are using older versions of PowerBuilder with TFS and are wondering whether the latest PowerBuilder 2019 R2 would work with the latest Azure DevOps Server 2019, this article shows how you could achieve that.

Interfacing PB Applications with the Windows API - Part 4

This tutorial has discussed how to interface traditional, Windows-hosted PowerBuilder 32-bit and 64-bit applications with the Windows Application Programming Interface (API), also known as the WinAPI. In the first three parts, the groundwork was laid to make you more knowledgeable and comfortable coding External Function Declarations (EFD's) and understanding the nuances of how information is exchanged between PB and Windows API functions. Part four contains a list of coding tips and techniques and mapping tables to help you with the translation between many common WinAPI datatypes and the standard PB datatypes. It also describes a free PB sample application and non-visual user object that can dynamically determine the memory size and layout of a structure in either 32-bit or 64-bit environments.