I wrote an EDTF wrapper as well, so that's covered. Anything else I missed ?
If you come at the problem from a PC developer perspective, they simply check out projects, work on code and commit changes.
The i source file methodology is pretty much the same as having project directories on a PC with QDDSSRC, QCLSRC, etc being directories.
So to that end my developers have ready access to SVN repositories today. Why wouldn't I want to do that in the future ? IBM i development should be made similar to PC development if we're to mainstream it.
All the SCM providers that I have talked to are coming at the problem from the old-style IBM i perspective. I feel like I am taking a fresh look at the problem trying to equalize the ease of which source code is managed on the i to be similar to the PC.
Several in this forum may not agree, but my approach is pretty straightforward and liberating in its simplicity I think.
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
* Subject: RE: Exit Point When Opening a Source Member with RDP ?
* From: rob@xxxxxxxxx
* Date: Fri, 18 Jan 2013 09:29:30 -0500
* List-archive: <http://archive.midrange.com/midrange-l
* List-help: <mailto:midrange-l-request@xxxxxxxxxxxx?subject=help>
* List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
* List-post: <mailto:midrange-l@xxxxxxxxxxxx>
* List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l
* List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l
No I do not know if there is an exit point that gets called from EDTF.
Again, exit points are great. However they're simply patch work if your
development team has excessive authority and can just work around them.