Friday, August 10, 2018

PowerBuilder 2017 R3 New Feature: Encryption

PowerBuilder 2017 R3 introduces support for encoding and encrypting data, something of particular interest when using REST web services.  We're going to take a look at those new features.

Thursday, August 09, 2018

PowerBuilder 2017 R3 New Feature: OAuth

PowerBuilder 2017 R2 added a number of REST features, which I covered in a previous blog post.  One area for improvement on the original feature was better support for REST authentication methods.  The HTTPClient and RESTClient objects provided methods to set request headers, but doing the legwork needed for some of the more complex authentication mechanism (i.e., OAuth) were left to the developer.  PowerBuilder 2017 R3 addresses that.  In this blog post we'll look at using this new feature.

Tuesday, August 07, 2018

PowerBuilder 2017 R3 New Feature: JSON Enhancements

There were some JSON features introduced in 2017 R2, in particular the JSONGenerator and JSONParser, which were covered in a previous blog post.  2017 R3 introduces additional important JSON features, in particular JSON import/export from a DataWindow, and a JSONPackage object that is used to merge/extract JSON data sets.  Those will be covered in this blog post.

Thursday, August 02, 2018

PowerBuilder 2017 R3 New Feature: Git Enhancements

Support for using Git as a source control system without going through a bridge product was added in 2017 R2 and covered in a previous blog post.  In this blog post we're going to look at the enhancements that were added to that feature in 2017 R3.

Tuesday, May 29, 2018

PowerBuilder 2017 R3 New Feature: PDF Enhancements

With the release of PowerBuilder 2017, a new native method of exporting DataWindows to PDF became available.  There were some enhancements added in R2, primarily support for the following:

Wednesday, March 28, 2018

Calling SHGetKnownFolderPath from PowerBuilder

Up through Windows XP, if you wanted to get the physical location of certain defined folders (e.g. the users Documents folder), you would use the SHGetFolderPath function in the Windows API.  Roland Smith has examples of using that on his Topwiz Software site.  That function continues to work in later versions of Windows, although it's basically a wrapper for the SHGetKnownFolderPath function.

SHGetFolderPath uses CSIDL values, whereas SHGetKnownFolderPath uses KnownFolderID GUIDs.  One difference is that there are a lot more KnownFolderIDs than there are CSIDLs.  That means some of the defined folder locations you may want to get the physical location for can't be accessed through the older SHGetFolderPath method.  And that's exactly the situation I ran into.

Thursday, March 15, 2018

More options for connecting PowerBuilder with Git for source control

One of the things that has been hindering PowerBuilder users from adopting Git for source control has been the lack of a MSSCCI provider for Git.  That changed when PB Software released their provider in 2014, although I didn't discover it until 2017 and wrote about it in this blog post.

Of course, one of the new features in PowerBuilder 2017 R2 is native support for Git, so if you're using that version then the lack of a MSSCCI provider for Git is no longer an issue.  However, if you're on an older version of PowerBuilder, you still need such provider.

The good news is that since I wrote that original article another MSSCCI provider for Git has become available.  In September of 2017, the folks who make the Zeus editor and the AgentSVN MSSCCI provider for SVN announced the release of AgentGit, a MSSCCI provider for Git.

I haven't tried this new Git provider yet, but I do use their SCN provider and it's quite solid.  I would expect their Git provider to work equally as well.  They also have a try before you buy option so you can check it out for yourself for free.