Re: Using RDP 8.0 i Projects

Well, IMO, that's just a kludge. You're taking a source control mechanism
that's not designed to work with IBM i and finding a way to wedge it in.

I think you would be better off getting a host based SVN client working and
simply adding some RSE user defined options rigged up to do your check in &
check out functions. A subsequent implementation could contribute first
class actions to the RSE popup menu to invoke the checkout & checkin.

You can easily push and pull IBM i source members for compiling at
will as well as objects that you want to version control in SVN.

True, but the development model isn't natural for IBM i.

If we going to call anything kludgy, it should be the traditional IBM i
source model.

The more I develop in non-IBM i environments, the more frustrated I become
with the traditional IBM i source tools and dealing with limited fixed
length source physical files when I return. I haven't dropped an 80 column
punch card deck in over 30 years. At what point will IBM allow us to feed
the RPG compiler something more than 69 characters per line from a source
file?

PLUS you run the risk of two developers overwriting everyone each others
modifications ... since the IBM i project mode doesn't lock the source
member while it is being edited.

Pessimistic locking is one way to deal with contention, but certainly not
the only way. Checking out source requires procedures to break the lock when
circumstances dictate. I prefer the subversion workflow, where source
differences must be resolved before the update is permitted.

Jack Callahan