Difference between revisions of "Style test page"
Bowtieguru (talk | contribs) |
Bowtieguru (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Here are sample font-size and line-height combinations | + | '''Here are sample font-size and line-height combinations''' |
| + | |||
| + | @all I haven't found a way to tweek the inter-para spacing in this demo, the wiki filter ignores it.. but via F12, '.mw-body p { margin: 0.875em 0; }' looks pretty good. | ||
| + | |||
| + | |||
| + | |||
---- | ---- | ||
| − | default - font-size: 0.875em; line-height: 1.6em; | + | default - font-size: 0.875em; line-height: 1.6em; |
| Line 33: | Line 38: | ||
---- | ---- | ||
| − | + | font-size: 0.875em; line-height: 1.3rem; | |
| Line 64: | Line 69: | ||
---- | ---- | ||
| − | + | font-size: 0.875em; line-height: 1.1rem; | |
| Line 95: | Line 100: | ||
---- | ---- | ||
| − | + | font-size: 1.0em; line-height: 1.4em; | |
| Line 127: | Line 132: | ||
---- | ---- | ||
| − | + | font-size: 1.0em; line-height: 1.3em; | |
| Line 159: | Line 164: | ||
---- | ---- | ||
| − | + | font-size: 1.0em; line-height: 1.2em; | |
| Line 191: | Line 196: | ||
| − | + | font-size: 1.0em; line-height: 1.1em; | |
| Line 223: | Line 228: | ||
| − | here's the typical css | + | here's the typical css |
.mw-body p { margin: 0.875em 0; } | .mw-body p { margin: 0.875em 0; } | ||
.mw-body-content { line-height: 1.3em; font-size: 1.0em; } | .mw-body-content { line-height: 1.3em; font-size: 1.0em; } | ||
Revision as of 05:09, 26 June 2016
Here are sample font-size and line-height combinations
@all I haven't found a way to tweek the inter-para spacing in this demo, the wiki filter ignores it.. but via F12, '.mw-body p { margin: 0.875em 0; }' looks pretty good.
default - font-size: 0.875em; line-height: 1.6em;
Warning: If you are using a BOINC version lower than 5.8.2, before you add or edit cc_config.xml, exit BOINC. Normally in Boinc Manager File->Exit. If you are running as a service, Start->Run, type net stop boinc and press OK/Enter.
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
For BOINC 5.2.1 - 5.10.45: Save the cc_config.xml file into your BOINC directory.
For BOINC 6.1 - all above that: Save the cc_config.xml file into your BOINC Data directory.
This can also be found in the the BOINC Wiki .. Check the site regularly for changes/additions.
font-size: 0.875em; line-height: 1.3rem;
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
BOINC Programs directory
The default directory where BOINC will install its executables to is:
- Windows 32bit: C:\PROGRAM FILES\BOINC
- Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
- Linux: wherever you are unpacking it/BOINC/
- Macintosh: /Applications/BOINC/
font-size: 0.875em; line-height: 1.1rem;
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
BOINC Programs directory
The default directory where BOINC will install its executables to is:
- Windows 32bit: C:\PROGRAM FILES\BOINC
- Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
- Linux: wherever you are unpacking it/BOINC/
- Macintosh: /Applications/BOINC/
font-size: 1.0em; line-height: 1.4em;
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
BOINC Programs directory
The default directory where BOINC will install its executables to is:
- Windows 32bit: C:\PROGRAM FILES\BOINC
- Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
- Linux: wherever you are unpacking it/BOINC/
- Macintosh: /Applications/BOINC/
font-size: 1.0em; line-height: 1.3em;
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
BOINC Programs directory
The default directory where BOINC will install its executables to is:
- Windows 32bit: C:\PROGRAM FILES\BOINC
- Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
- Linux: wherever you are unpacking it/BOINC/
- Macintosh: /Applications/BOINC/
font-size: 1.0em; line-height: 1.2em;
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
BOINC Programs directory
The default directory where BOINC will install its executables to is:
- Windows 32bit: C:\PROGRAM FILES\BOINC
- Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
- Linux: wherever you are unpacking it/BOINC/
- Macintosh: /Applications/BOINC/
font-size: 1.0em; line-height: 1.1em;
Note: Not all options are available in lower versions of BOINC. Note: When using a World Community Grid version of BOINC, flags may differ. Please ask at the WCG forums if in doubt. I did add the specific flags in this FAQ.
cc_config.xml is mainly used for debugging BOINC. By enabling these flags BOINC writes specific information both to the Messages tab/Event Log, to stderrdae.txt and stdoutdae.txt.
When you are using BOINC 5.8.2 or above, it isn't necessary to stop the BOINC client. Just edit the cc_config.xml file and tell Boinc Manager to read the file, through Advanced, Read config file.
Warning: Any changes in the <log_flags> section will be used immediately. Yet a lot of changes in the <options> section will need a complete exit and restart of the BOINC client. They will not take if you just re-read the config file.
Below is an example of cc_config.xml, split in the <log_flags> and <options> sections. By showing where the <log_flags> and <options> go in each section, you ought to be able to know where goes what when you make your cc_config.xml file. When saving with a text editor, make sure you save as "All types" and in ANSI format. That way the editor won't auto-add a TXT extension and the file will be readable by BOINC.
BOINC Programs directory
The default directory where BOINC will install its executables to is:
- Windows 32bit: C:\PROGRAM FILES\BOINC
- Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
- Linux: wherever you are unpacking it/BOINC/
- Macintosh: /Applications/BOINC/
here's the typical css
.mw-body p { margin: 0.875em 0; } .mw-body-content { line-height: 1.3em; font-size: 1.0em; }
