Fossil SCM
Add a section to www/customskin.md about using skintxt2config.c instead of pasting changes into the UI.
Commit
37e2705114b5c6be0c530c315a9fc21ad6ab3a13671a99673b05ac0346385276
Parent
22b38448bd27667…
1 file changed
+37
-1
+37
-1
| --- www/customskin.md | ||
| +++ www/customskin.md | ||
| @@ -310,10 +310,11 @@ | ||
| 310 | 310 | with the "--skin ./newskin" option. If the argument to the --skin |
| 311 | 311 | option contains a "/" character, then the five control files are |
| 312 | 312 | read out of the directory named. You can then edit the control |
| 313 | 313 | files in the ./newskin folder using you favorite text editor, and |
| 314 | 314 | press "Reload" on your browser to see the effects. |
| 315 | + | |
| 315 | 316 | |
| 316 | 317 | ### Disabling The Web Browser Cache During Development |
| 317 | 318 | |
| 318 | 319 | Fossil is aggressive about asking the web browser to cache |
| 319 | 320 | resources. While developing a new skin, it is often helpful to |
| @@ -526,11 +527,46 @@ | ||
| 526 | 527 | Iterate until the desired look is achieved. |
| 527 | 528 | |
| 528 | 529 | 4. Copy/paste the resulting css.txt, details.txt, |
| 529 | 530 | header.txt, and footer.txt files |
| 530 | 531 | into the CSS, details, header, and footer configuration screens |
| 531 | - under the Admin/Skins menu. | |
| 532 | + under the Admin/Skins menu. Alternately, import them using the | |
| 533 | + process described below. | |
| 534 | + | |
| 535 | +An alternative to step 4 is to convert the skin files into a form | |
| 536 | +which can be imported into a repository using `fossil config import`. | |
| 537 | +It requires compiling [a small tool from the fossil source | |
| 538 | +tree](/file/tools/skintxt2config.c): | |
| 539 | + | |
| 540 | +> | |
| 541 | +``` | |
| 542 | +$ cc -o s2c /path/to/fossil/checkout/tools/skintxt2config.c | |
| 543 | +``` | |
| 544 | + | |
| 545 | +With that in place, the custom skin files can be converted with: | |
| 546 | + | |
| 547 | +> | |
| 548 | +``` | |
| 549 | +$ ./s2c yourskin/*.txt > skin.config | |
| 550 | +``` | |
| 551 | + | |
| 552 | +It can be imported into an arbitrary fossil repository with: | |
| 553 | + | |
| 554 | +> | |
| 555 | +``` | |
| 556 | +$ fossil config import skin.config | |
| 557 | +``` | |
| 558 | + | |
| 559 | +And it can be pushed to a remote repository with: | |
| 560 | + | |
| 561 | +> | |
| 562 | +``` | |
| 563 | +$ fossil config push skin | |
| 564 | +``` | |
| 565 | + | |
| 566 | +That approach has proven to be an effective way to locally develop | |
| 567 | +skin changes then push them to a "live" site. | |
| 532 | 568 | |
| 533 | 569 | |
| 534 | 570 | ## See Also |
| 535 | 571 | |
| 536 | 572 | * [Customizing the Timeline Graph](customgraph.md) |
| 537 | 573 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -310,10 +310,11 @@ | |
| 310 | with the "--skin ./newskin" option. If the argument to the --skin |
| 311 | option contains a "/" character, then the five control files are |
| 312 | read out of the directory named. You can then edit the control |
| 313 | files in the ./newskin folder using you favorite text editor, and |
| 314 | press "Reload" on your browser to see the effects. |
| 315 | |
| 316 | ### Disabling The Web Browser Cache During Development |
| 317 | |
| 318 | Fossil is aggressive about asking the web browser to cache |
| 319 | resources. While developing a new skin, it is often helpful to |
| @@ -526,11 +527,46 @@ | |
| 526 | Iterate until the desired look is achieved. |
| 527 | |
| 528 | 4. Copy/paste the resulting css.txt, details.txt, |
| 529 | header.txt, and footer.txt files |
| 530 | into the CSS, details, header, and footer configuration screens |
| 531 | under the Admin/Skins menu. |
| 532 | |
| 533 | |
| 534 | ## See Also |
| 535 | |
| 536 | * [Customizing the Timeline Graph](customgraph.md) |
| 537 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -310,10 +310,11 @@ | |
| 310 | with the "--skin ./newskin" option. If the argument to the --skin |
| 311 | option contains a "/" character, then the five control files are |
| 312 | read out of the directory named. You can then edit the control |
| 313 | files in the ./newskin folder using you favorite text editor, and |
| 314 | press "Reload" on your browser to see the effects. |
| 315 | |
| 316 | |
| 317 | ### Disabling The Web Browser Cache During Development |
| 318 | |
| 319 | Fossil is aggressive about asking the web browser to cache |
| 320 | resources. While developing a new skin, it is often helpful to |
| @@ -526,11 +527,46 @@ | |
| 527 | Iterate until the desired look is achieved. |
| 528 | |
| 529 | 4. Copy/paste the resulting css.txt, details.txt, |
| 530 | header.txt, and footer.txt files |
| 531 | into the CSS, details, header, and footer configuration screens |
| 532 | under the Admin/Skins menu. Alternately, import them using the |
| 533 | process described below. |
| 534 | |
| 535 | An alternative to step 4 is to convert the skin files into a form |
| 536 | which can be imported into a repository using `fossil config import`. |
| 537 | It requires compiling [a small tool from the fossil source |
| 538 | tree](/file/tools/skintxt2config.c): |
| 539 | |
| 540 | > |
| 541 | ``` |
| 542 | $ cc -o s2c /path/to/fossil/checkout/tools/skintxt2config.c |
| 543 | ``` |
| 544 | |
| 545 | With that in place, the custom skin files can be converted with: |
| 546 | |
| 547 | > |
| 548 | ``` |
| 549 | $ ./s2c yourskin/*.txt > skin.config |
| 550 | ``` |
| 551 | |
| 552 | It can be imported into an arbitrary fossil repository with: |
| 553 | |
| 554 | > |
| 555 | ``` |
| 556 | $ fossil config import skin.config |
| 557 | ``` |
| 558 | |
| 559 | And it can be pushed to a remote repository with: |
| 560 | |
| 561 | > |
| 562 | ``` |
| 563 | $ fossil config push skin |
| 564 | ``` |
| 565 | |
| 566 | That approach has proven to be an effective way to locally develop |
| 567 | skin changes then push them to a "live" site. |
| 568 | |
| 569 | |
| 570 | ## See Also |
| 571 | |
| 572 | * [Customizing the Timeline Graph](customgraph.md) |
| 573 |