• Light gray background for code blocks
• Syntax highlighting for code blocks based on http://shjs.sourceforge.net/
  • Lars H: I officially hate it! It seems to be seriously wrong (if taken as hinting about how the code should be interpreted) at least as often as it is right, and that's when it's colouring Tcl code. We have a lot of code blocks that aren't Tcl code, and no markup to tell which is which. Please disable soonest possible.
  • stevel I don't like it either, and it was my idea originally :) The intention was to make the Tcl commands links to the relevant manual pages, to make it easier for noobs to see code then get details on the language. It's an idea worth pursuing, just not sure if the fugliness of the syntax highlighting kills it. Just to give some perspective, we have one person (Jos Decoster) maintaining the wiki markup code, and Jos tries to keep everyone happy. But with this level of resource, one of the ways that ideas are filtered is to try them and gauge the response, rather than attempt consensus before every change (and therefore stagnate). Mostly he gets it right, occasionally there's a good idea that turns out not to be in practice.
  • AMG: See the syntax highlighting page for a more conservative proposal, including a few examples. I wonder if this highlighting scheme would be less odious, to the point that we can live with it without needing to add Yet More Markup to turn it off and on. (We already have four different ways to do fixed-width text, five if you count the left column of the rarely-used option table markup.)
  • nscerqueira: Apart from the posted problems I like the syntax highlighting a lot. It turns the code more intuitive and easy to read. ( I thought that a positive thought was missing here;) )
  • AMG: I haven't decided if I welcome syntax highlighting on this Wiki or not, but I think it's worth a try. However, I am thoroughly unimpressed with the current implementation. See [1] (derived from [2]) for the definition being used: notice the misspelled keywords, highlighting of single quotes, lack of support for namespaces and arrays, and oversimplified detection of quotes and comments. It seems to be somewhat inherited from C, for instance look at the u, L, int8, etc. suffixes that numbers are allowed to have. I understand that the syntax highlighting engine has intrinsic limitations that can't be overcome by a clever syntax definition, but even given that I think there's a ton of room for improvement. See my [Graffiti] experimentation: [3].
  • CMcC: I think syntax highlighting is a good thing, on balance. The existing implementation needs tweaking, yes. Also, I think its default .css is fairly high-chroma and ill-considered (highlight braces in red? bad ergonomics, IMO, as it draws the eye ... I imagine this has some bearing on peoples' initial aversion) The existing implementation has the considerable benefit that it is in-client, and able to target different languages. It seems to me that a shallow parser for Tcl in JS+regexps isn't a bad project to consider developing communally over time, and this isn't a bad venue for exposing it to contribution and successive improvement.
• The subtitle on line or word difference pages now has a link to the word or line difference page
  • AMG: The page titles are now a bit wonky: "Word difference between version 61 and 60 for Word" or "Line difference between version 61 and 60 for Line". jdc: fixed.
• Reworked history page so you can easily get a diff between non consecutive pages

ReCAPTCHA

doctool

nroff

http://wiki.tcl.tk/_/search?S=wub

• major refactoring of Wub
• major mods to Wikit: removed magic numeric pages, added types, added rudimentary permission system for admin tasks.

• Wiki backend has been rewritten as an abstract API. Behind the API jdc implemented a new TDBC-based database. The current backend target is sqlite, but it should be easy enough to retarget it to any supported database. One virtue of this approach is that we get to provide a testbed for TDBC. Please report any issues arising. We're particularly interested in worst-case page save performance.

• Mainly for fun, created http://wiki.tcl.tk/_tiny/ which is a tinurl-like facility, I call it MiniscURL, which generates persistent unique small URLs from longer ones. You can use it if you like to generate URLs for use on the wiki.

• per-ip connection is back. Using the new reflected channels facility. Limits of 20 connections, but that's a bit fluid. Any strange unexpected network behaviour may be down to this new approach.
• in the development, there are some bugs, we will be exercising and diagnosing them, some strange behaviour may be present. The specific behaviour appears as 'connection reset' on FF.

• per-ip connection limit of 20 - should be enough. Not yet working, backed out, investigating.
• performance instrumentation feedback - anything over 100mS is too slow, and is logged. Exceptions enumerated.
• finally found a way to detect bots pretty reliably. it requires cookies, so just accept 'em.
• bots are now denied access to expensive/slow operations as they don't need 'em and some bots don't obey robots.txt
• rss.xml sped up and cached.

• page caching - experimental
• new instrumentation on page generation (not visible to users, but nice to note :)
• simplified some page generation with concommittant speedups.

• New markup to specify categories:

           <<categories>> Category A | Category B | Category C

• This will be rendered requivalent to:

           ----
           !!!!!!
           %|[Category A]|[Category B]|[Category C]|%
           !!!!!!

• Don't go updating pages where categories are specified in another way, this will be done in batch.

• Link in left hand menu to add comments to a wiki page. You can enter a comment, which will be added at the end of the wiki page, preceded by an horizontal rule, your nick-name and a time-stamp. When the page ends with new style category specifiers, comments are insert right above that.
  LV so what's the philosophical difference between adding a comment to a page versus using the wiki's Edit link to just make changes in place like this? I'm wondering when one is going to be used versus the other. I know that I prefer to see people make corrections directly to the content as opposed to making comments at the bottom that leave me having to read through everything on the page to be certain that what I am reading is correct.
  DKF: The big difference is that you don't get edit conflicts if two people are adding comments to a page at the same time, unlike if they're both editing. Probably could do with some JS/Ajax cleverness so that we can see the page we're commenting on while writing the comment, but that's easier to add once the basic functionality is done (well, it is if you're JDC and know that sort of thing. :-))
  jdc Adding a comment has the same restrictions as a plain edit. Only it is added at the end of the page, in a fixed format. I see it as making remarks about the contents of the page, discussing about the content without clobbering it. Not as a replacement of fixing and adding content in place.
  ferrieux Agreed. One extra value I see to the fixed-form comment style is to deprecate the habit of writing a comment (or whole discussion) without a date.

• More toolbar buttons on edit page (save, preview, cancel, help)
• Move preview and help up so they appear above the edit area

• major Wub mods to provide http:/_nub/nubs and .ini based configuration
• edit preview not currently working (I screwed up the js :}) but will be fixed
• contemplating move to jQuery for javascripting needs

• CSS for media screen, print and handheld.
• Default for media screen is now with left-hand menu. Alternative CSS without left-hand menu for screen, can be toggled from footer, choice is stored in a cookie.
• Media print and handheld are without left-hand menu.
• Some space between general and page links in the left-hand menu.
• Made ribbons on /4 nofollow links.

• Activity indicator on Recent Changes which is a measure for the editing done on the page. The activity is shown as a gray ribbon. The longer the ribbon, the more edit activity on the page. Clicking on the ribbon will bring you to the new editing summary page.
• The edit summary lists the latest edits, most recent at the top, newly added lines in green, removed lines in red.
• Some browsers convert sequences of 8 spaces into a tab. This introduced a lot of fake edits. When saving, tabs are now converted into sequences of 8 spaces.
• The RSS feed now contains all changes, not just the latest one. The description field now also contains the newly added lines.

http://wiki.tcl.tk/_stats/

• Problem interaction with Spider Blocking solved. You may have seen Forbidden responses for a while.
• Caching and fetching after edit are uncoupled, so your client may receive a redirect after edit before the cache has processed the cache-invalidation request. This means you may not see your changes immediately. I've got to mull this over.

http://wiki.tcl.tk/_block

• the empty line across the top is the great outage of 2007
• the big empty space in the middle is a lot of stuff which has been changed or deleted.
• the dark horizontal lines are probably wikignoming (which seems to be a seasonal event :)
• a significant number of pages are edited for creation, then left (that's the 'crust')
• What is that empty space from 6000-8000? (DKF: I think that's remnants from when the FAQ was partially-transferred into the wiki; it generated a very large number of empty/virtual pages, and then the person working on it was asked not to do that, so that many have never had content added to them.)
• And the empty space in the 19000's ???

package require Tk
package require Mk4tcl
package require Plotchart

mk::file open db [lindex $argv 0]

canvas .c  -background white -width 800 -height 600
pack .c -fill both

set s [::Plotchart::createXYPlot .c {0.0 22000.0 2000.0} {900000000.0 1210000000.0 100000000.0}]

$s dataconfig series1 -colour "red" -type symbol -symbol cross
$s ytext "Time"
$s xtext "Page number"
$s title "Page/last-edit graph"

for { set i 0 } { $i < [mk::view size db.pages] } { incr i } {
    lassign [mk::get db.pages!$i date page] date page 
    if { [string length $page] > 1 } { 
        $s plot series1 $i [mk::get db.pages!$i date]
    }
}

mk::file close db

package require Tk
package require Mk4tcl
package require Plotchart

mk::file open db [lindex $argv 0]

canvas .c  -background white -width 800 -height 600
pack .c -fill both

set s [::Plotchart::createXYPlot .c {900000000.0 1210000000.0 100000000.0} {0.0 80.0 10.0}]

$s dataconfig series1 -colour "red" -type symbol -symbol cross
$s xtext "Time"
$s ytext "Page number"
$s title "Residual changes per day"

for { set i 0 } { $i < [mk::view size db.pages] } { incr i } {
    lassign [mk::get db.pages!$i date page] date page 
    if { [string length $page] > 1 } { 
        incr rd([expr $date-($date%86400)]) 1
    }
}

mk::file close db

foreach k [array names rd] {
    $s plot series1 $k $rd($k)
}

package require Mk4tcl

mk::file open db [lindex $argv 0]

set edl {}

for { set i 0 } { $i < [mk::view size db.pages] } { incr i } {
    lassign [mk::get db.pages!$i date page name] date page name
    set ed 0
    if { [string length $page] > 1 } { 
        set ed 1
        incr ed [llength [mk::select db.pages!$i.changes]]
        lappend edl [list $i $ed $name]
    }
}

mk::file close db

set edl [lsort -decreasing -index 1 -integer $edl]

set cnt 0

puts "%|'''Number of page'''|'''Number of edits'''|'''Page name'''|%"

foreach edsl $edl {
    lassign $edsl page count name
    puts "&|[format %5d $page]|[format %5d $count]|\[$name\]|&"
    incr cnt
    if { $cnt > 20 } { 
        break
    }
}

package require Mk4tcl

mk::file open db wikit.tkd

set edl {}

for { set i 0 } { $i < [mk::view size db.pages] } { incr i } {
    lassign [mk::get db.pages!$i date page name] date page name
    if {$date < [clock scan "30 days ago"]} continue
    set ed 0
    if { [string length $page] > 1 } { 
        set ed 1
        for {set j 0} {$j < [mk::view size db.pages!$i.changes]} {incr j} {
            lassign [mk::get db.pages!$i.changes!$j date] date
            if {$date < [clock scan "30 days ago"]} continue
            incr ed
        }
        lappend edl [list $i $ed $name]
    }
}

mk::file close db

set edl [lsort -decreasing -index 1 -integer $edl]

set cnt 0

puts "%|'''Number of page'''|'''Number of edits'''|'''Page name'''|%"

foreach edsl $edl {
    lassign $edsl page count name
    puts "&|[format %5d $page]|[format %5d $count]|\[$name\]|&"
    incr cnt
    if { $cnt > 20 } { 
        break
    }
}

• Home
• Recent changes
• Help
• WhoAmI/Logout
• Create new page
• Random page
• Previous page
• Next page
• 
  
• Add comments
• Edit
• History
• Edit summary
• References