Coding projects (by others)

This page lists a few projects that I've cloned from elsewhere.

Some of them still sync with the original repository, and in some cases I keep a local (private) branch with my own tweaks and additions.

These changes are merged to trunk with the branch [tkt-improvements](/timeline?r=tkt-improvements), therefore I close this ticket.

This was added in the branch [tkt-improvements](/timeline?r=tkt-improvements) which is merged to trunk. Therefore I close the ticket. Note that both a checkin-hash and the name of a tag will be linked if present in the repository.

The branch is merged and therefore I close this ticket. As a note: this change shows the comments added in the new table ticketchng. At the time the ticket was created all comments were merged in a field. I decided to leave these old style comments out, as over time the newer edits will dominate. If you want to include them, add this to the `<th1>`-block in configuration for edit ticket page: ``` if {[info exists comment]} { if {[string length $comment]>10} { html { <tr><td class="tktDspLabel">Description:</td></tr> <tr><td colspan="5" class="tktDspValue"> } if {[info exists plaintext]} { set r [randhex] wiki "<verbatim-$r links>\n$comment\n</verbatim-$r>" } else { wiki $comment } } } ```

windows issue try to run following batch file (note, file should be saved as oem) fossil init t.fossil mkdir t cd t fossil open ../t.fossil echo. > OEM-B0-░ fossil add OEM-B0-░ fossil commit -m "t" eskil . eskil shows wrong tree with two files t (current) vs t _FOSSIL_ 36864 2025-05-01 14:29:10 OEM-в–‘ 3 2025-05-01 14:29:10 OEM-░ 3 2025-05-01 14:29:06

> As per the OP's suggestion, moving the ticket state colors into CSS, so that they participate in the skinning process, would be a good thing to do someday. I see some problem. It would be quite easy I think to create CSS-Classes if a Variable cssclass or similar is created in the SQL-Query. That part is easy. But what CSS-Classes would a creator of a report pick? As the users can switch their skin, these would've to be supported in all available skins. We could provide some for common cases, but it would be hard to use more customized stuff. The report-creator has to make sure their CSS-Classes are added to the skins. So it is not impossible to implement I think, but as I see it the usefulness would be limited if there isn't a way to add the needed classes to all skins or add custom classes to the report window as well. Which probably would be the best way, add another input for creating CSS that is injected on the report page. But then again it is not part of the skinning.

Theme: "Small Business" by Blackrock Digital

Background: "A beautiful day" by Jason Blackeye