Sure, I would contibute if I manage to do that.
Actually I developed myself something similar to ActiveVFP years ago, but I find ActiveVFP promising in functionality I did not manage to create, so I am considering to switch to ActiveVFP. However, my web server does compile everything it loads :)
I did try autocompile and it works in some manner, but I get errors as fxp stays locked so compiler cannot replace it. I do use RELEASE PROCEDURE.
Here are two functions I wrote to make it easier to handle loading libraries. Maybe something like that could be included in main code as I guess it is frequently needed.
PROCEDURE LOADLIB
PARAMETERS pLibName, pLibPath
IF (! EMPTY (pLibPath))
mLibName = pLibPath + "\" + pLibName
ELSE
mLibName = pLibName
ENDIF
IF ! FILE(mLibName +".fxp") OR FDATE(mLibName + ".prg", 1) > FDATE(mLibName + ".fxp", 1)
COMPILE mLibName + ".prg"
ENDIF
SET PROCEDURE TO (mLibName) ADDITIVE
ENDPROC
PROCEDURE UNLOADLIB
PARAMETERS pLibName, pLibPath
IF (! EMPTY (pLibPath))
mLibName = pLibPath + "\" + pLibName
ELSE
mLibName = pLibName
ENDIF
RELEASE PROCEDURE (mLibName)
ENDPROC
Thing is, if I use ActiveVFP then most of my code will be in libraries, not scripts, so I have to deal with this fxp file locking.