Update the renderer for the restructuring of PG in openwebwork/pg#709#7
Conversation
|
Note that this should not be merged until after the referenced pg pull request, and the git submodule will need to be updated before this is merged. Also, we need to discuss the state of this repository in relation to the PG 2.17 release. Currently the develop branch is up to date to work with PG 2.17. The main branch is set to work with PG 2.16. This pull request (if merged) will take the develop branch past the PG 2.17 release. So should develop be merged into main, and a "release" made to match PG 2.17 and tag the current commit in main for PG 2.16? |
4ec2614 to
a6bd912
Compare
c5aec52 to
496e77f
Compare
6495bc5 to
8801a38
Compare
8c72c35 to
351f7e7
Compare
76395e7 to
f31362a
Compare
72e9bbf to
ab80799
Compare
ab80799 to
dbedb41
Compare
8e62047 to
bb7b04f
Compare
|
This is now updated to work with the current develop branch of PG. Note that the updated |
The WeBWorK::PG module is now part of PG, and PG has its own environment
so the webwork2 WeBWorK::PG module (and its derivatives) have been
removed.
The WeBWorK::Constants, WeBWorK::Debug, and WeBWork::CourseEnvironment
modules and the webwork2 conf files are no longer needed and so are
removed. The renderer uses the WeBWorK::PG::Environment module which is
part of PG. Note that this adds one minor installation step for the
renderer. The file conf/pg_config.yml must be copied to lib/PG/conf.
Usually that file will work as is, but in some cases administrators may
want to make changes to it. For example, the externalPrograms are the
standard linux executables and in the standard locations. On some
systems those may need to be changed.
Most of the WeBWorK::Utils module has been removed. All that is left is
the two methods that the renderer uses.
In addition the renderer lib directory has been flattened.
lib/WeBWorK/lib/WeBWorK is now just lib/WeBWorK. With this (among other
things) the WEBWORK_ROOT environment variable is not needed. Note that
$WeBWorK::Constants::PG_DIRECTORY is not available. $ENV{PG_ROOT} is
used instead in the renderer code.
Note that the unnecessary encoding and decoding of perl warnings has
been removed.
Also note that the references to drdrew42 have been changed to
openwebwork.
bb7b04f to
080c0e4
Compare
The WeBWorK::PG module is now part of PG, and PG has its own environment so the webwork2 WeBWorK::PG module (and its derivatives) have been removed.
The WeBWorK::Constants, WeBWorK::Debug, and WeBWork::CourseEnvironment modulesa and the webwork2 conf files are no longer needed and so are removed. The renderer uses the WeBWorK::PG::Environment module which is part of PG. Note that this adds one minor installation step for the renderer. The file
renderer/conf/pg_config.ymlmust be copied torenderer/lib/PG/conf. Usually that file will work as is, but in some cases administrators may want to make changes to it. For example, the externalPrograms are the standard linux executables and in the standard locations. On some systems those may need to be changed.Most of the WeBWorK::Utils module has been removed. All that is left is the two methods that the renderer uses.
In addition the renderer lib directory has been flattened. lib/WeBWorK/lib/WeBWorK is now just lib/WeBWorK. With this (among other things) the WEBWORK_ROOT environment variable is not needed. Note that $WeBWorK::Constants::PG_DIRECTORY is not available. $ENV{PG_ROOT} is used instead in the renderer code.
Note that the unnecessary encoding and decoding of perl warnings has been removed.
Also note that the references to drdrew42 have been changed to openwebwork.