From the Editor-in-Chief of PowerBuilder Developer's Journal

Bruce Armstrong

Subscribe to Bruce Armstrong: eMailAlertsEmail Alerts
Get Bruce Armstrong via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Bruce Armstrong

PowerBuilder contains a number of built-in common dialogs that can be used within your own applications. What do you do when one of these dialogs meets most, but not quite all, of the functionality you need? Do you simply accept the limited functionality? Do you write your own dialog from scratch to replicate them and add the additional functionality (a maintenance headache)? There is a third option. You can simply use the dialog that PowerBuilder provides and modify it at runtime to provide just the additional functionality that you need. The dialogs PowerBuilder provides include: The GetFileOpenName, GetFileSaveName, ChooseColor, GetFolder, PrintSetup, and PrintSetupPrinter system function dialogs The DataWindow Control SaveAs, SetFilter, and SetSort function dialogs The DataWindow object DataWindow.Print.Prompt attribute dialog The ubiquitous MessageBox dialog For... (more)

The Next Paradigm Shift...

First there were the thin clients. Not the Internet thin clients, I'm talking about the mainframe applications with dumb terminals. Everything ran on the server; the client was basically there only to display and for input from the user. Then PCs came along and a paradigm shift occurred toward thick clients. Really thick clients in fact. Not only was the user interface running locally on the PC, but often so was the data access layer, with the application accessing local database files or perhaps a shared database file on the network. Key reasons for the shift were a better user... (more)

Implementing the Microsoft Rich Edit Control

What we needed to do was implement spell checking in the rich edit fields in our application (see Figures 1 and 2). To do that, we got a license for the Sentry Spelling Checker Engine from Wintertree Software (www.wintertree-software.com). The utility is easily implemented and works quite well on standard Rich Edit controls. However, the PowerBuilder Rich Edit control is an OEM version of an old third-party control that was popular before Microsoft introduced its Rich Edit control to the common controls. As a result, the messages and functions it supports are completely differen... (more)

New Features in PowerBuilder 11.5

In the previous articles in this series, we looked at FDCC changes (part 1) and GUI enhancements (part 2) in PowerBuilder 11.5. In this article, we'll be looking at the enhancements that were added to PowerBuilder 11.5 that are specifically related to .NET targets. The one thing we won't be covering in this regard is the .NET security enhancements that were covered in a previous PBDJ article: "Applying Code Access Security in PowerBuilder .NET Applications" by Maggie Lv. Strong Named Assemblies The .NET framework allows the author to sign an assembly so that it has a "strong nam... (more)

Come Get Your Beta While It’s Hot

The PowerBuilder 12.0 beta has officially started. It's pretty hard to overstate the magnitude of the changes that are taking place within PowerBuilder for this version. As a result, it's more important than ever for as many people as possible to participate in order to get the most amount of feedback as possible back to Sybase. It's going to be a lot easier to let Sybase know there's a problem with a feature now before the "die is cast" and it's easier for them to fix than to wait until after the release to find the problem, and then have to wait for an EBF for a correction In ... (more)