Every software development project of any significant size or complexity has
a requirement for controlling the source code asset. PowerBuilder is capable
of integrating with any third-party Source Code Control (SCC) tool that
implements Microsoft's SCC API. However, the fact that PowerBuilder stores
its code inside PowerBuilder Libraries (PBLs) and not as individual ASCII
text files adds a layer of complexity to that integration. The release of
PowerBuilder 8.0 in 2001 brought with it a new set of challenges in the form
of a completely redesigned interface with SCC providers, including PBNative.
In this article, I outline the nature of the changes that were introduced in
PowerBuilder 8.0, and discuss many of the enhancements that have been
released with PB 9.0.
Why Version Control?
Version Control software adds significant administrative overhead to every
project, a... (more)
Source code control (SCC) has become a "hot topic" lately, especially after
PowerBuilder 8.0 was released, as it contains a wholesale revision to its
interface with third-party SCC tools.
PB8 now leverages the full functionality of Microsoft's SCC API, and is much
more tightly integrated with the SCC repository. There are now over a dozen
commercially available SCC tools that implement the SCC API, and choosing the
appropriate tool for your organization is not a trivial task. The scope,
features, and functions of these tools range from the "bare bones" approach
of the open-sourc... (more)
Every development shop that is currently managing its PowerBuilder source
code with a third-party SCC tool and has not yet migrated to PB8 will need to
understand the upcoming changes in methodology before attempting a migration.
Even PBNative users will be affected, as that interface has been redesigned
to use the SCC interface as well.
In my previous article, "Understanding the SCC Interface in PowerBuilder 8"
(PBDJ, Vol. 8, issue 11), I outlined the sweeping rewrite of the source code
control (SCC) interface introduced in PowerBuilder 8.0. This article walks
through some simp... (more)
PowerBuilder 8.0 was launched in conjunction with the 10th anniversary of the
product and, by all accounts, it has exceeded everyone's expectations (...and
there was much rejoicing!). The enhancements in this release focus
specifically on three major areas - the Web, EAServer integration, and n-tier
The introduction of workspaces and targets, and the redesigned IDE have
greatly enhanced the overall usability of the tool, especially with regard to
these three areas. However, there was one significant revision introduced in
8.0 that is not getting the press I feel it ... (more)
Yes, Virginia, Sybase does have a J2EE-compatible application server, and
it's known as EAS, short for Enterprise Application Server.
In fact, EAS is alive and well, and this issue of the PowerBuilder
Developer's Journal will focus on the recent release of version 6.0. Why, you
may ask yourselves, would a magazine dedicated to a 4GL development IDE want
to devote any energy to reviewing an application server platform? The simple
answer is this - EAS has been the lone choice for PB development shops that
wanted to deploy NVOs to a middle-tier application server. There's no better ... (more)