-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">\r
-\r
-<html>\r
- <head>\r
- <meta name="generator" content="HTML Tidy, see www.w3.org">\r
-\r
- <title></title>\r
- </head>\r
-\r
- <body>\r
-<H1>Applying templates</H1>\r
-<P>Since version 0.3 you are able to\r
-selectively apply settings from a template of your choice to any job\r
-you like. One reason might be that you want jobs that have already\r
-been recorded to be recorded using different config settings (e.g.\r
-other quality settings, resolution, etc.). If you wanted to do this\r
-for many jobs at once, it would be very tedious to edit each job\r
-manually, setting up changes.</P>\r
-<P>You can apply properties of templates\r
-very easily:</P>\r
-<UL>\r
- <LI><P>Select the template you want to\r
- use</P>\r
- <LI><P>Select the job(s) whose\r
- properties you want to be affected by the template</P>\r
- <LI><P>Right-click inside the jobs\r
- table and select “Apply template”</P>\r
- <LI><P>A new dialog will open where you\r
- will be able to select which one of the settings should be copied\r
- from the template to the job. Please, be aware that old settings of\r
- the job will be overwritten!</P>\r
- <LI><P>Usually the settings will be\r
- copied 1:1 from the template to the job. <B>There are 2 exceptions,\r
- though</B>:</P>\r
- <UL>\r
- <LI><P><B>Demo directory:</B> Here\r
- copying the value from the template to the job would not make\r
- sense, because in a template you actually specified a <B>directory</B>,\r
- <U>not</U> a <B>file</B>. However, a job needs to point at a <B>file</B>.\r
- What will happen shall be demonstrated by the following example:\r
- Let's say that the job's path to the demo file (before applying the\r
- template) has been <B>C:\Nexuiz\data\demos\mydemo.dem</B>\r
- and the path setup in the template has been pointing to the\r
- directory<B> C:\Games\Nexuiz2.5.2\data\demos</B>.\r
- The new demo file path, after the “apply” process is\r
- done, would be <B>C:\Games\Nexuiz2.5.2\data\demos\mydemo.dem</B>;\r
- this means that from the <B>job's</B>\r
- demo path the program will just take the name of the demo by itself\r
- (mydemo.dem), and put the path from the <B>template</B>\r
- in front of it</P>\r
- <LI><P><b>Video\r
- destination:</b> Here the same thing happens like for the Demo\r
- directory. The new video destination will be <Directory set up\r
- in the template> + <just the filename of the setting of the\r
- job></P>\r
- </UL>\r
-</UL>\r
-<P>Another example of how this feature could be useful is this one: Suppose some\r
-movie maker was to create a community movie with frags from different\r
-people, or a movie maker was to continue or finish a movie from\r
-someone else. If one person creates a queue of jobs (which naturally\r
-includes the demo's names, start second and end second) and then\r
-decides not to record the frags herself but send it to some other\r
-movie maker, all that needs to be done is to save the job queue and\r
-send it to the other movie maker, together with the demos. The other\r
-movie maker can then copy the demos into his own demo directory and\r
-import the job queue. Of course the problem would then be that all\r
-these imported jobs could not really be executed right away, because\r
-all these paths might be incorrect, I mean, would simply not exist or\r
-match to the system of the movie maker who wants to record the jobs\r
-(e.g. path to Nexuiz engine or demo directory). But this can easily\r
-be fixed. The movie maker just needs to select the imported jobs and\r
-apply one of her own templates to them, and by doing so, fix all\r
-incorrect paths.</P>\r
- </body>\r
-</html>\r
-\r
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
+
+<html>
+ <head>
+ <meta name="generator" content="HTML Tidy, see www.w3.org">
+
+ <title></title>
+ </head>
+
+ <body>
+<H1>Applying templates</H1>
+<P>Since version 0.3 you are able to
+selectively apply settings from a template of your choice to any job
+you like. One reason might be that you want jobs that have already
+been recorded to be recorded using different config settings (e.g.
+other quality settings, resolution, etc.). If you wanted to do this
+for many jobs at once, it would be very tedious to edit each job
+manually, setting up changes.</P>
+<P>You can apply properties of templates
+very easily:</P>
+<UL>
+ <LI><P>Select the template you want to
+ use</P>
+ <LI><P>Select the job(s) whose
+ properties you want to be affected by the template</P>
+ <LI><P>Right-click inside the jobs
+ table and select “Apply template”</P>
+ <LI><P>A new dialog will open where you
+ will be able to select which one of the settings should be copied
+ from the template to the job. Please, be aware that old settings of
+ the job will be overwritten!</P>
+ <LI><P>Usually the settings will be
+ copied 1:1 from the template to the job. <B>There are 2 exceptions,
+ though</B>:</P>
+ <UL>
+ <LI><P><B>Demo directory:</B> Here
+ copying the value from the template to the job would not make
+ sense, because in a template you actually specified a <B>directory</B>,
+ <U>not</U> a <B>file</B>. However, a job needs to point at a <B>file</B>.
+ What will happen shall be demonstrated by the following example:
+ Let's say that the job's path to the demo file (before applying the
+ template) has been <B>C:\Nexuiz\data\demos\mydemo.dem</B>
+ and the path setup in the template has been pointing to the
+ directory<B> C:\Games\Nexuiz2.5.2\data\demos</B>.
+ The new demo file path, after the “apply” process is
+ done, would be <B>C:\Games\Nexuiz2.5.2\data\demos\mydemo.dem</B>;
+ this means that from the <B>job's</B>
+ demo path the program will just take the name of the demo by itself
+ (mydemo.dem), and put the path from the <B>template</B>
+ in front of it</P>
+ <LI><P><b>Video
+ destination:</b> Here the same thing happens like for the Demo
+ directory. The new video destination will be <Directory set up
+ in the template> + <just the filename of the setting of the
+ job></P>
+ </UL>
+</UL>
+<P>Another example of how this feature could be useful is this one: Suppose some
+movie maker was to create a community movie with frags from different
+people, or a movie maker was to continue or finish a movie from
+someone else. If one person creates a queue of jobs (which naturally
+includes the demo's names, start second and end second) and then
+decides not to record the frags herself but send it to some other
+movie maker, all that needs to be done is to save the job queue and
+send it to the other movie maker, together with the demos. The other
+movie maker can then copy the demos into his own demo directory and
+import the job queue. Of course the problem would then be that all
+these imported jobs could not really be executed right away, because
+all these paths might be incorrect, I mean, would simply not exist or
+match to the system of the movie maker who wants to record the jobs
+(e.g. path to Nexuiz engine or demo directory). But this can easily
+be fixed. The movie maker just needs to select the imported jobs and
+apply one of her own templates to them, and by doing so, fix all
+incorrect paths.</P>
+ </body>
+</html>
+
projects / xonotic / xonotic.git / blobdiff