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)
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)
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)
Greetings, and a Happy 2012 to you!
You may have noticed that I’ve been rather absent from the blogosphere
lately. I’ve been focusing on my transition to the Sybase/SAP Mobility
team. That doesn’t mean I’ve abandoned my passion for PowerBuilder –
that’s the tool that built my career, and it will always be a part of me.
My day-to-day responsibilities are now with the Sybase Mobility stack,
which includes Sybase Unwired Platform (SUP), Afaria, and the SQL
Anywhere/MobiLink/UltraLite toolset. Therefore, the content that I publish
in this blog will take a decided turn towards t... (more)
OData is quickly becoming the Lingua Franca for data exchange over the
web. The OData standard defines a protocol and a language structure for
issuing queries and updates to remote data sources, including (but not
limited to) relational databases, file systems, content management systems,
and traditional web sites. It builds upon existing Web technologies, like
HTTP and RESTful web services, the Atom Publishing Protocol (AtomPub), XML,
SAP and Sybase iAnywhere released SQL Anywhere version 16 in March 2013, and
it had many cool new featur... (more)