Feedback on iProjects - good, bad and ugly

I used iProjects for a while, but abandoned it because it was a lot of work for not so much gain. The build system is not really ready for prime time. It could be automated to the point that you create a list of program and file objects, and it builds it properly for you without the developer having to maintain the COMPILE.CLLE program. But it really isn't ready to do that yet. The build system should be able to detect changed objects, and those that need recompiling or rebuilding based on what has changed. It should be smart enough to know how to build those objects. I should be able to tell it that x is a service program that contains the following modules, and exports the following procedures. Service source should be built automatically and should be smart enough not to change the order of exports. It also needs to be flexible enough that I can tell it that I am changing the parameters on service program A, and it will walk me through getting that done in a way that leaves existing programs unaffected should I choose not to recompile the world.

I also recall having an issue with the fact that an i Project is tied directly to a library. It would be nice if I could have an iProject use whichever libraries I choose, and multiple libraries if I need that. I would also like iProjects to support the IFS. The build system should also support the IFS and allow automatic compiles from the IFS, even for object types that can not compile directly from the IFS.

Sorry for the rambling mess, it has been a while since I used iProjects, and my thoughts are quite fractured at this point.

Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx


-----"Edmund Reinhardt" <edmund.reinhardt@xxxxxxxxxx> wrote: -----
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
From: "Edmund Reinhardt" <edmund.reinhardt@xxxxxxxxxx>
Date: 04/19/2017 06:21PM
Cc: Rob Cecco <cecco@xxxxxxxxxx>
Subject: [WDSCI-L] Feedback on iProjects - good, bad and ugly


As RDi architect, I want to make sure that I don't get out of touch with
your experience in using RDi in the trenches.
For example, I might think that i Projects are a perfect way for people to
be able to use Git on IBM i and maybe I am missing some reason why people
are not adopting i Projects.
So please set me straight.
Who is using i Projects and if so how do you like it?
If you have tried i Projects and abandoned them, let me know why?

I am very thankful to have access to such a vocal group of customers that I
can get unfiltered, immediate feedback from.

Thanks
Edmund