Moving configuration and files to PG #651

pstaabp · 2022-02-05T13:43:47Z

This is a draft PR to get a discussion going plus some help. Here's some big picture ideas about this

expansion of PGEnvironment module to 1) read the conf/pg_defaults.yml file 2) process much of it (say to build up nested directories)
move pg-related configuration from defaults.config (on ww2 side) into conf/pg_defaults.yml
addition of a standaloneRenderer code (in bin) from https://github.com/mgage/standaloneProblemRenderer and adaption of it to only use modules from pg-side.
To get standaloneRenderer working, need to move many modules from webwork side to pg side.
All of the modules on pg side should be independent of webwork. The main thing needed is to replace CourseEnvironment with PGEnvironment and update the path to get configurations.

A few things I'm thinking about/having trouble with probably because of my lack of knowledge of the way pg works in detail:

I think I have got Localization compiling on pg-side (though not tested). I copied all of the .po files from ww side. I think only the pg side things need to be there.
I commented out some things about the Delayed Mailer. It seems like that shouldn't be on the pg-side. Can we get this back to webwork2.
In FormatRenderedProblem (now on pg side), there are a number of calls to $ce->{...} which don't seem to exist in the code. Is this automatically added by LTI ?
In FormatRenderedProblem, there is information about the theme? Is this really needed?
Perhaps we need two different FormatRenderedProblem code (one on each side) or a wrapper on the webwork side?

To play with this so far, running bin/standaloneRenderer.pl on a problem with various flags. It doesn't finish, but runs a lot of code.

This clearly isn't done and once we can get the standalone renderer working, need to remove modules from webwork2 side.

Please let me know if there is something I have clearly not done well. Also, I think there might be other modules needed to be moved to PG.

…with CORE::

Conflicts: lib/Complex1.pm

More changes.

Conflicts: lib/LaTeXImage.pm lib/TikZImage.pm

pstaabp · 2022-02-17T12:20:31Z

A new draft. First, in an attempt to clean up and clarify packages, there is now a lib/Renderer directory where I'm hoping to keep all packages related to rendering a problem. This touches a lot, but I think helps separate in our minds what is PG.

Although not currently working (hence a draft PR), the meat of this is in Renderer::Problem. You create a problem passing in a problem source (not a file path), and then render the problem. The idea will be to get the results as a hash of everything we typically expect back. Currently, this isn't working. There's some issues with the safe compartment, but am pushing this up to get some feedback.

I have a very simple script bin/test_render_problem.pl that loads in a problem from the OPL and attempts to set it up to render. Currently I'm getting an error:

Can't locate object method "current" via package "Parser::Context" (perhaps you forgot to load "Parser::Context"?) at /opt/webwork/pg/macros/PG.pl line 16.

drgrice1 · 2022-02-17T12:22:19Z

htdocs/package.json

@@ -12,8 +12,9 @@
        "prepare": "npm run generate-css"
    },
    "dependencies": {
+        "bootstrap": "^5.1.3",


I think I added that before my latest round of changes. I'm trying to strip out as much html/css/js as possible.

drdrew42 · 2022-02-18T15:58:12Z

lib/WWSafe.pm

 }

+use Data::Dumper;


drdrew42 · 2022-02-18T16:05:00Z

lib/Renderer/Translator.pm

+	print "in Translator::new\n";
+	# print Dumper $safe_cmpt;


Suggested change

print "in Translator::new\n";

# print Dumper $safe_cmpt;

drdrew42 · 2022-02-18T16:05:21Z

lib/Renderer/Translator.pm

+	print Dumper "in evaluate_modules";
+	print Dumper \@modules;


Suggested change

print Dumper "in evaluate_modules";

print Dumper \@modules;

drdrew42 · 2022-02-18T16:05:32Z

lib/Renderer/Translator.pm

-			my ( $module, @extra_packages ) = @$module_packages_ref;
-
+			my ($module, @extra_packages) = @$module_packages_ref;
+			warn "Loading $module\n";


Suggested change

warn "Loading $module\n";

drdrew42 · 2022-02-18T16:05:45Z

lib/Renderer/Translator.pm

 #use PadWalker;     # used for processing error messages
-#use Data::Dumper;
-
+use Data::Dumper;


Suggested change

use Data::Dumper;

drdrew42 · 2022-02-18T17:05:14Z

lib/Renderer/Problem.pm

+use PGEnvironment;
+use Renderer::Translator;
+use Renderer::Localize;
+use Data::Dumper;


Suggested change

use Data::Dumper;

drdrew42 · 2022-02-18T17:08:26Z

lib/Renderer/Problem.pm

+	return shift, 0;    # no errors
+}
+
+sub defineProblemEnvir {


isn't all this duplicating PG_env?

drdrew42 · 2022-02-18T17:11:24Z

lib/Renderer/IO.pm

-			/^1\./          and $mod = "WeBWorK::PG::IO::WW1";
-			/^2\./          and $mod = "WeBWorK::PG::IO::WW2";
-			/^Daemon\s*2\./ and $mod = "WeBWorK::PG::IO::Daemon2";
+			/^1\./          and $mod = "Renderer::IO::WW1";


Isn't WW1 being deleted in this PR?

drdrew42 · 2022-02-18T17:11:55Z

lib/Renderer/Localize.pm

+use strict;
+use warnings;
+
+use feature "say";


Suggested change

use feature "say";

drdrew42 · 2022-02-18T17:12:13Z

lib/Renderer/Localize.pm

+use Data::Dumper;
+


Suggested change

use Data::Dumper;

drdrew42 · 2022-02-18T17:39:33Z

I commented out some things about the Delayed Mailer. It seems like that shouldn't be on the pg-side. Can we get this back to webwork2.

I only see DelayedMailer used in PG::Local, and there it is created and then added to the problem environment as an extra. The defineProblemEnvir subroutine adds the DelayedMailer as {mailer} which does not appear anywhere else AFAICT.

In FormatRenderedProblem (now on pg side), there are a number of calls to $ce->{...} which don't seem to exist in the code. Is this automatically added by LTI ?

FormatRenderedProblem::formatRenderedProblem L#82-6 defines a new course environment as $ce?
Edit: It looks like you've replaced CourseEnvironment with PG environment... so isn't this expected?

In FormatRenderedProblem, there is information about the theme? Is this really needed?
Perhaps we need two different FormatRenderedProblem code (one on each side) or a wrapper on the webwork side?

It looks like theme information in FormatRenderedProblem is only used for the footer information. Seems safe to remove.

drdrew42

I think this is the source of your errors -- you're loading PG.pl too soon, try loading the other perl_libraries first.

drdrew42 · 2022-02-18T20:15:49Z

lib/Renderer/Problem.pm

+	############################################################################
+	# evaluate modules and "extra packages"
+	############################################################################
+
+	#warn "PG: evaluating modules and \"extra packages\"\n";
+
+	for my $module_packages_ref (@{ $self->{pg_env}->{perl_modules} }) {
+		my ($module, @extra_packages) = @$module_packages_ref;
+
+		# the first item is the main package
+		$self->{translator}->evaluate_modules($module);
+
+		# the remaining items are "extra" packages
+		$self->{translator}->load_extra_packages(@extra_packages);
+	}
+


I believe this should come right after Translator->new, then we need to set the translator's environment: $translator->environment($self->{pg_env}); (this used to be set with the results of defineProblemEnvir, which I'm assuming is supplanted by the new pg_environment object), and then after all that -- we can load in PG.pl with unrestricted_load...

Conflicts: htdocs/package.json

mgage

I believe that the guts of the AttemptsTable should be left on the callers (e.g. webwork2) side of the renderer -- it reports the status of the graded problem to the student and the styling and method of presentation should be up to the caller. (e.g. the instead of an html answer table the calling program might like to use some fancier framework, including using overlays of the answer blanks when they are moused over -- to indicate which answers are right and what is wrong with the other answers. The information for this is passed back from process_answers( a subroutine in Translator.pm) through rh_evaluated_answers entry in the pg object. Eventually this information is returned to the caller through, I believe, %PG_ANSWERS_HASH which is part of the output of ENDDOCUMENT in PG.pl. The information is also in the PG object which is passed back although currently we use the contents of the %PG_ANSWER_HASH to report information. AttemptsTable subroutines use this data to communicate the information to the student. That might be different for different use cases so AttemptsTable should not be part of the render itself.

mgage · 2022-06-27T20:05:01Z

I suggest concentrating on getting the configuration files (and whatever reads those files working) so that we can make the configuration of webwork2 and pg as separated as possible (hopefully completely separated). It should be possible to plug these two configurations back in to an existing webwork2 course and test the concept. Drawing the configurations from two different files should not upset the current operation of webwork2 and pg and we can test whether we've left some configurations out, or are duplicating some of them or if there are hidden inter-dependencies which we have overlooked

pstaabp · 2022-10-05T18:39:42Z

This PR will be superseded by #709 and closed once that is merged.

pstaabp · 2022-10-12T16:56:28Z

Closed in favor of #709 and #726

mgage and others added 9 commits July 22, 2021 20:13

Fixed a \1 by replacing by in a regex expression, qualified length() …

1e910a7

…with CORE::

tan() is not a native perl function so there is no need to override it

d9cc7e5

initial checkin of moving pg-related configuration and modules to pg.

11652f7

continued moving of files from ww to pg.

1f27e4a

update gitignore so pg_defaults.yml is now available.

6cab99c

Merge remote-tracking branch 'refs/remotes/mgage/bugfix_develop'

96fbd60

Conflicts: lib/Complex1.pm

merges

9283ee9

continued work on pg-ww separation. The legal battle continues. :)

cf692de

More changes.

Merge remote-tracking branch 'refs/remotes/origin/develop'

50aa9b8

Conflicts: lib/LaTeXImage.pm lib/TikZImage.pm

drgrice1 reviewed Feb 17, 2022

View reviewed changes

a couple of minor changes

b274f62

drdrew42 requested changes Feb 18, 2022

View reviewed changes

drdrew42 reviewed Feb 18, 2022

View reviewed changes

pstaabp added 5 commits March 12, 2022 06:15

Merge branch 'develop'

2d2743b

Conflicts: htdocs/package.json

WIP: continued work on getting renderer

8df9d8a

WIP: update po files for pg

91799ed

WIP: more work on getting renderer working.

49a6eb9

WIP: continued work on self-contained rendering code.

92fc975

mgage requested changes Jun 27, 2022

View reviewed changes

pstaabp closed this Oct 12, 2022

pstaabp deleted the move-config-to-pg branch December 9, 2022 11:23

Uh oh!

Moving configuration and files to PG #651

Moving configuration and files to PG #651

Uh oh!

Conversation

pstaabp commented Feb 5, 2022

Uh oh!

pstaabp commented Feb 17, 2022

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

drdrew42 commented Feb 18, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

drdrew42 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mgage left a comment

Choose a reason for hiding this comment

Uh oh!

mgage commented Jun 27, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pstaabp commented Oct 5, 2022

Uh oh!

pstaabp commented Oct 12, 2022

Uh oh!

Uh oh!

drdrew42 commented Feb 18, 2022 •

edited

Loading

mgage commented Jun 27, 2022 •

edited

Loading