version 1.8, 2013/08/30 15:05:58
|
version 1.10, 2013/09/22 15:42:53
|
Line 18 at the first publication step).
|
Line 18 at the first publication step).
|
\begin{verbatim} |
\begin{verbatim} |
<startouttext /> |
<startouttext /> |
<link rel="stylesheet" index="11" |
<link rel="stylesheet" index="11" |
href="/res/yourname/yourpath/testcss.css" type="text/css" /> |
href="/res/yourdomain/yourusername/yourpath/testcss.css" type="text/css" /> |
<span class="Yellow">After the Earth and Mars, which other body in our |
<span class="Yellow">After the Earth and Mars, which other body in our |
solar system is thought to be the next most likely site for finding |
solar system is thought to be the next most likely site for finding |
life?</span><endouttext /> |
life?</span><endouttext /> |
<allow src="/res/yourname/yourpath/testcss.css" /> |
<allow src="/res/yourdomain/yourusername/yourpath/testcss.css" /> |
|
|
where testcss.css contains: |
where testcss.css contains: |
|
|
Line 65 in files that must use the extension {}`
|
Line 65 in files that must use the extension {}`
|
|
|
For performance purposes it is best not to include too may resources in a |
For performance purposes it is best not to include too may resources in a |
.page (8 would be a good limit; and likely fewer if maxima or R are |
.page (8 would be a good limit; and likely fewer if maxima or R are |
required for computation). The course editor offers similar tool called |
required for computation). The Course Editor offers a similar tool called |
a ``Composite page'' which resides within a course rather than in the published |
a ``Composite page'' which resides within a course rather than in the published |
repository. |
repository. |
|
|
The underying XML structure, and |
The underlying XML structure, and |
behavior of a .page file are the same as used for a ``Composite page'', |
behavior of a .page file are the same as used for a ``Composite page'', |
which can be added to a course using the Course Editor. One difference |
which can be added to a course using the Course Editor. One difference |
between the two is that for a .page in Authoring Space, one of the |
between the two is that for a .page in Authoring Space, one of the |
Authoring Space editors (Simple Edit or Advanced Edit) will be used to |
Authoring Space editors (Simple Edit or Advanced Edit) will be used to |
modify the contents of the file, whereas for a Composite Page, the |
modify the contents of the file, whereas for a Composite Page, the |
course editor is used. |
Course Editor is used. |
|
|
Options for reuse of a course Composite page are: (a) use cloning to copy |
Options for reuse of a course Composite page are: (a) use cloning to copy |
everything from the old course to the new; (b) as course coordinator, |
everything from the old course to the new; (b) as course coordinator, |
Line 84 course coordintator in a different cours
|
Line 84 course coordintator in a different cours
|
into the other course from the Course Editor's clipboard. |
into the other course from the Course Editor's clipboard. |
|
|
The course manual describes ways to combine resources in folders, |
The course manual describes ways to combine resources in folders, |
which is an alternative to creating composite pages. The advantage of a .page |
which is an alternative to creating composite pages. A potential advantage of a |
is that they can be printed all at once. The disadvantage is that once a .page |
a composite page is that the browser's inbuilt capabilities can be used to print |
is published, the contents are more difficult to change. Publishing a .page |
all resources included within a page with a single ``Print'' call. |
|
That said, LON-CAPA's own print utility which creates PDFs allows students |
|
to print all resources in a folder to a single PDF, |
|
which lessens the advantange that accrues from use of a composite page. |
|
The disadvantage of use of a published .page is that once a .page |
|
is published, reordering or modifying the contents requires use of the resource |
|
assembly tool in authoring space, followed by republication. Publishing a .page |
in the repository is suggested if the content does not need to change. |
in the repository is suggested if the content does not need to change. |
|
|
For more information on .pages, see the section \ref{Sequence_Page_Maps} |
For more information on .pages, see the section \ref{Sequence_Page_Maps} |
Line 128 a new sequence file in Authoring Space.
|
Line 134 a new sequence file in Authoring Space.
|
for which a student's progress through a series of resources can be |
for which a student's progress through a series of resources can be |
specified. Grading of conditional sequences can be complicated. |
specified. Grading of conditional sequences can be complicated. |
|
|
\item A .rights file is used to specify custom access rights for a published |
\item A \textbf{.rights} file is used to specify custom access rights for a published |
resource. The access rights to apply to a specific resource are |
resource. The access rights to apply to a specific resource are |
specified on publication (or republication) of the resource. A .rights |
specified on publication (or republication) of the resource. A .rights |
file also must be published to be selectable during resource publication |
file also must be published to be selectable during resource publication |
as a ``Custom Distribution File'' when ``Customized right of use ...'' is selected from the |
as a ``Custom Distribution File'' when ``Customized right of use ...'' is selected from the |
``Copyright/Distribution'' dropdown list. See the section \ref{Publishing_Copyright}. |
``Copyright/Distribution'' dropdown list. See the ``Publishing A Resource'' section |
|
\ref{Publishing_Copyright}. |
|
|
\item A .sty is a LON-CAPA style file used to apply custom styling to specific |
\item A \textbf{.sty} is a LON-CAPA style file used to apply custom styling to specific |
tags in a LON-CAPA problem. The styles defined in the file can be applied to display of all |
tags in a LON-CAPA problem. The styles defined in the file can be applied to display of all |
resources in a course using: |
resources in a course using: |
|
|
Line 170 incorporated pages by the annoying $<$bl
|
Line 177 incorporated pages by the annoying $<$bl
|
</definetag> |
</definetag> |
\end{verbatim} |
\end{verbatim} |
|
|
To use the .sty in a course, within the course, In PARM - ``Set Course Environment'' |
|
you can specify a style file for your course under ``Default XML Style File''. |
|
|
|
When printing, LON-CAPA will use the tex \textbackslash section as |
When printing, LON-CAPA will use the tex \textbackslash section as |
$<$h1$>$-rendering. |
$<$h1$>$-rendering. |
|
|
Note that .css is perhaps a more modern way to acheive formatting. |
Note that .css is perhaps a more modern way to achieve formatting. |
|
|
\item A \textbf{.task} task file is a bridge task file. Bridge tasks permit |
\item A \textbf{.task} task file is a bridge task file. Bridge tasks permit |
assessment using rubrics. See the Bridge Task section \ref{BridgeTask_About}. |
assessment using rubrics. See the Bridge Task section \ref{BridgeTask_About}. |