Petr Ferdus wrote:
>
> What might block ckout feature?
>
First, you should be aware that enabling the "th1-docs" setting on a
repository basically
implies that all people with check-in privileges are implicitly trusted.
That is why it
is disabled by default at compile-time and runtime.
If you enable the "th1-docs" setting and add a "*.th1" file into the
repository with
"<th1></th1>" sections contained within it, those scripts will be evaluated
when that
file is rendered via the associated embedded documentation URL, perhaps via
"fossil ui",
e.g.:
http://localhost:8080/doc/ckout/example.th1
Contents of "example.th1":
<th1>
set x 9
html <br>
puts $x
html <br>
reinitialize 5; # enable reading Tcl setting from global config.
puts [globalState flags]
puts [tclEval {clock seconds}]
html <br>
puts [tclEval {clock format [clock seconds]}]
html <br>
</th1>
Should produce some interesting output.
Note that the ".th1" file in the above example should not actually need to
be checked
in, since "ckout" may be used to view pending embedded documentation file
changes.
--
Joe Mistachkin
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
