makei init support

[worksofliam]

I think it'd be useful for an init parameter to create all the base files for a project.

initialised iproj.json

 {
    "version": "0.0.1",
    "description": "ILE application",
    "objlib": "&CURLIB",
    "includePath": ["QRPGLEREF"],
    "setIBMiEnvCmd": [],
    "repository" : "https://github.com/acme/backoffice",
}

I think some magic needs to be done with includePath. I think init should look for those directories in the working tree and find things like QRPGLEREF, H, etc, and then add them to the list of it exists.

Same thing for repository. Something like git config --get remote.origin.url would get the remote path, which would be a nice initial value.

Rules.mk file in every directory

I think the root Rules.mk file needs to be created with just SUBDIRS = x y x where x y z is a list of directories in the root.

I also think it should make a basic Rules.mk in every folder with some initial values and maybe some additional comments:

TRGs=
DTAs=
SQLs=
BNDDs=
PFs=
LFs=
DSPFs=
PRTFs=
CMDs=
SQLs=
MODULEs=
SRVPGMs=
PGMs=
MENUs=
PNLGRPs=
QMQRYs=
WSCSTs=
MSGs=

[edmundreinhardt]

I like the idea about the git url and the more complete Rules.mk
For the include path, we would need to scan for /INCLUDE and /COPY statement in the RPG and then other language specific and then maybe even do renames to .RPGLEINC
A little more involved. Is it true that there is a naming convention for which SRC-PF has includes?

[edmundreinhardt]

Note that we not longer need the last point about generating the object type targets.
We could infer some basic rules like
x.MODULE: x.RPGLE

would we know if it is PGM or SRVPGM, BNDRPG or RPGMOD, only if there were binaries to query

[edmundreinhardt]

@worksofliam Now that we have SourceOrbit, what should be the interplay between makei cvtsrcpf and sourceorbit.

Today allow Project Explorer to call each in turn.