Matt,

On the properties for the iProject, the default is to always re-create the "compile" source file. I turn that off myself.

1.) Right-Click the project, and select Properties
2.) Select the "iProject Build" & pick the build style.
I normally pick "CL Program"
3.) Click the button: "Configure..." on the right
4.) That opens the "CL Program Build Style Configuration" dialog
5.) Un-check the "Automatically generate COMPILE.CLLE prior to each build"

I love RDI, but the Navigation take a little bit to learn. And after you see it, it makes sense!. IBM i developers are intelligent and willing to learn more! Just like other Developers. Some just need help getting started.

We use the package Softlanding/Turnover, and it has built in integration for iProjects! Awesome!

RDI is so underutilized. It takes a little practice and training to get use it. I remember back in the 90's, that a fellow IBM seemed to pick up PC software packages so Fast! He was not afraid and inquisitive! He explored the different menu options in the software and figure things out. He did this by practicing different options on the software. He was the go to person, even though he had no official training!

I was showing a newbie how to use RDI and Debug. And I notice he got confused by which window had the focus. To someone use to using a dumb terminal, and a single screen, windows can be confusing. On Green Screen when you debug, it is on a single screen. When debugging with RDI you have the RDI session, and possible the Green-Screen, Batch-Job, Stored-Procedure, web-service, etc. to debug. When debugging you have to go back and forth between the screens. He was not use to that, and got confused. I politely point that out to him, and he very quickly picked up on that. He just needed a little help and direction...

Once you understand how iProjects work, it can be EXTREMELY POWERFUL. But, no doubt, there is a learning curve. Once you learn it, you wonder why we don't all use iProjects more often. I do NOT use it all the time, but the times I do it, it is extremely helpful!

I admit, I mostly use the normal non-Project. Because I can do the Ctrl+C to save and compile. That is my FAVORITE Feature of RDI 9.5.1.2. Almost instant compile and error list. Since I occasional fat-finger some code. I can instantly fix my fat-finger errors! Cool!!! <Joy Joy>

Hang in there, and endeavor to persevere through the mastery of RDI! It is worth it. Knowledge of your development tools is a must in this 21st century! <Big Smile>


-Ken Killian-

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tyler, Matt
Sent: Wednesday, April 19, 2017 6:56 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Cc: Rob Cecco <cecco@xxxxxxxxxx>
Subject: Re: [WDSCI-L] Feedback on iProjects - good, bad and ugly

It been many years since I actively use i Projects

1. Build command, program option is difficult. I could not just set it how I want it was always recreating the build script.
2. I develop several different projects in my one library but i Projects treats libraries as a single project so I cannot just sync the two environments.
3. I only develop when I am connected to our server so I really don't need remote capabilities.
4. Quick change, compile, test cycles were difficult.
5. Source dates are wiped clean and replaced by current value.
6. Some tools like RPG Tool box are useless because it cannot connect to a server.
7. There may be more but I don't really use it.
8. i Projects does not integrate with our CMS Rocket Aldon.
9. I rarely import OSS projects but I have used i Projects to do so at least for the upload part.

-Matt

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Wednesday, April 19, 2017 4:21 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
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
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.