Re: iSeries Projects - comparing client to server

From: Buck

1) Using iSP Navigator view, open member for editing
2) Edit member, verify, etc. It won't take long before you want to
compile it so that you can test it on System i...
3) Using iSP Nav, right click member and 'Push'
4) Using iSp Nav, right click member, Remote Actions, Compile
5) Test your code on System i in the development library

I'm not a big iSP fan (mostly because of the one library limitations Buck
spoke to), but I have clients using it, so I know a little bit about it.
One thing is that if you choose compile, iSP will push the code
automatically. No big deal, but one less thing to worry about.

Unless no one will ever use PDM/SEU anymore, this is a non-starter for
most companies. Documentation tooling comes into play here as well.
Will Pathfinder or Abstract or X-Analysis be able to traverse a svn
repository to create documentation/cross references? Backup/restore
needs to be considered, as does authority/security to source members.

On the other hand, the nice thing is that you can theoretically include all
your corporate source, including non-System i source, in a single
repository.

Hope some of this was helpful. Don't curse out the WDSC team because
it's unsuitable to the task we're trying to make it do. I'm sure I
could use my scuba drysuit to carry gravel if I worked at it some.

And really, unless you're willing to remove the source from System i source
files completely, there's no way you're going to have an integrated source
management system using SVN or any of its counterparts.

I might express intense curiosity as to _why_ offline development was
important enough to invent iSP, but that's another thread entirely, and
unproductive since we have what we have.

This was Phil Coulthard's baby and he was very proud of it. The idea was to
allow people to work on planes, trains and automobiles (hopefully not while
driving). Only someone who travels for a living would consider it that
necessary. Me, I couldn't use it anyway because I'm an incrememntal
programmer; I write a bit and then test a bit, rinse and repeat.

Joe