Re: [WWdevel] location of Union macros

[Davide P. C. <dp...@un...>]

> Currently if one wants to use the Union problems, one has to link in
> the macros.  E.g. the instructions in
>
> http://devel.webwork.rochester.edu/twiki/bin/view/Webwork/ 
> InstallationManualV2pt2forSuSE10pt1
>
> read
>
>  Search for macrosPath and scroll down several lines to the line
> $pg{directories}{macros},
>  After this line add the two lines:
> '/opt/webwork/library/union_problib/macros',
> '/opt/webwork/library/union_problib/parserOrientation',
>
> Is there any reason not to put these under macros in the standard  
> distribution?
>

Yes.  Many of the Union macro files are pre-Parser and are no linger  
needed, and I'm not planning to continue supporting them.  Some are  
pretty early work, and need to be redone.  I do not think they are  
appropriate for the core distribution.  The things that I am ready  
for permanent installation are already added to macros.

Now that the macros path can be easily modified, there is much less  
reason to include these in pg/macros than before.  I would not want  
to see that directory cluttered up with macro files that I'm not  
fully satisfied with.


> I just looked and these  (and some examples)  are not included under
> database_problems/Union
>
> devel ...lock/cvs/database_problems diff -r Union/ ../union_problib/
> Only in ../union_problib/examples: AnswerFile-pl
> Only in ../union_problib/examples: AnswerFile-pm
> Only in ../union_problib/examples: answerEssay
> Only in ../union_problib/examples: compoundProblem
> Only in ../union_problib/examples: multiProblem
> Only in ../union_problib/: macros
> Only in ../union_problib/: parserOrientation
> Only in ../union_problib/: setOrientation
>

The examples files are not actual problems for use, but simply  
samples of programming techniques.  They illustrate the use of some  
macro packages for doing some complicated and non-standard things  
(like problems with several parts, or writing answers to files).   
They are relatively new and I'm not sure that the packages are stable  
yet.  They are experimental and I don't want them to be thought of as  
standard parts of WeBWorK yet.

Davide