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-source CVS (www.cvshome.org) to the full-fledged change
management methodology supported by Rational Software's ClearCase
(www.rational.com).
StarTeam is a flexible, feature-rich SCC environment that should be on any
organization's short list when evaluating tools in this category. Version 5.2
i... (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
development.
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)
In my previous post, we took a closer look at the XAML and WPF design
capabilities of PowerBuilder.Net (AKA PB12), and actually began to construct
a sample calculator application. I’m using this MSDN sample as a design
guide, which was 489 lines of C#, not counting the XAML. The previous
posting got us through the basics of the window and gridPanel layout, and we
were just about to start writing some PowerScript to get the calculator
working. Let’s continue that discussion now!
Step 4: Analysis and Design work
I’m one of those developers that likes to spend some time in the ... (more)
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, inc... (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)