Patrick Baas

Subscribe to Patrick Baas: eMailAlertsEmail Alerts
Get Patrick Baas: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: ColdFusion on Ulitzer

CFDJ: Article

Using CVS with PowerBuilder

How to crack Microsoft's open source lockout

A few moments later all the objects will be imported to their original library. The output window will show a lot of warnings and compile errors because they're imported sequentially. In most cases, the application object won't be updated in this pass. Select the application object, and execute "Get latest version..." again, but this time make sure you've checked "Get clean copy" in the advanced options dialog box.

Do a full build twice and no warnings or compiler errors should occur.

Avoiding Some Traps
Working with PowerBuilder and the CVS is very simple, but you must consider a few things.

  • First of all try out the best proxy settings for your project and ensure that all developers have the same settings all the time. One incorrectly configured proxy can mess up your whole project.
  • Every developer should create his own workspace, but it's important that the relative path from the workspace to the target is identical for all developers. If the path stored in the PBGs is different, it's impossible to retrieve sources to the correct PBL.
  • Create empty PBLs to set up a project from scratch. Don't use a copy of filled PBLs because they might contain objects moved to another PBL. After using these old PBLs the objects can show up twice, and if you try to check out one object, both objects are checked out at the same time. You cannot remove the wrong one easily.
  • The CVS can't manage application icons and PBL descriptions. They are stored in the PBLs directly and aren't available as source files. Set the right PBL description for your empty PBLs and add the correct application icon to your empty application object and every developer will have the right settings.
  • Only check out the object you're working on. If you use strict checkout procedures, the source file is locked for all revisions. The proxy uses the editor entry in the repository to determine if a file is checked out. The editor entry can only be set for a file, not a specific revision.
Conclusion
The CVS SCC proxy plug-in from PushOk is an excellent tool for using SCC- compliant IDEs with the CVS. The PowerBuilder characteristic of using PBLs to store source code is supported just as well as in other version management tools. It's possible to use the plug-in even in larger projects and worth its $19. There is a 30-day trial available and you can test it to see if it meets your needs.

If you do like to use subversion instead of a CVS, the PushOk SVN proxy is worth a try.

More Stories By Patrick Baas

Patrick Baas is a client/server developer for Vodafone in Germany. He has used InfoMaker/PowerBuilder since version 4 and is maintaining the PowerBuilder version management for technical applications at Vodafone
Germany.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.