2007-10-05 14:38:35 +02:00
|
|
|
# git-gui about git-gui dialog
|
|
|
|
|
# Copyright (C) 2006, 2007 Shawn Pearce
|
|
|
|
|
|
|
|
|
|
proc do_about {} {
|
|
|
|
|
global appvers copyright oguilib
|
|
|
|
|
global tcl_patchLevel tk_patchLevel
|
git-gui: Automatically spell check commit messages as the user types
Many user friendly tools like word processors, email editors and web
browsers allow users to spell check the message they are writing
as they type it, making it easy to identify a common misspelling
of a word and correct it on the fly.
We now open a bi-directional pipe to Aspell and feed the message
text the user is editing off to the program about once every 300
milliseconds. This is frequent enough that the user sees the results
almost immediately, but is not so frequent as to cause significant
additional load on the system. If the user has modified the message
text during the last 300 milliseconds we delay until the next period,
ensuring that we avoid flooding the Aspell process with a lot of
text while the user is actively typing their message.
We wait to send the current message buffer to Aspell until the user
is at a word boundary, thus ensuring that we are not likely to ask
for misspelled word detection on a word that the user is actively
typing, as most words are misspelled when only partially typed,
even if the user has thus far typed it correctly.
Misspelled words are highlighted in red and are given an underline,
causing the word to stand out from the others in the buffer. This is
a very common user interface idiom for displaying misspelled words,
but differs from one platform to the next in slight variations.
For example the Mac OS X system prefers using a dashed red underline,
leaving the word in the original text color. Unfortunately the
control that Tk gives us over text display is not powerful enough
to handle such formatting so we have to work with the least common
denominator.
The top suggestions for a misspelling are saved in an array and
offered to the user when they right-click (or on the Mac ctrl-click)
a misspelled word. Selecting an entry from this menu will replace
the misspelling with the correction shown. Replacement is integrated
with the undo/redo stack so undoing a replacement will restore the
misspelled original text.
If Aspell could not be started during git-gui launch we silently eat
the error and run without spell checking support. This way users
who do not have Aspell in their $PATH can continue to use git-gui,
although they will not get the advanced spelling functionality.
If Aspell started successfully the version line and language are
shown in git-gui's about box, below the Tcl/Tk versions. This way
the user can verify the Aspell function has been activated.
If Aspell crashes while we are running we inform the user with an
error dialog and then disable Aspell entirely for the rest of this
git-gui session. This prevents us from fork-bombing the system
with Aspell instances that always crash when presented with the
current message text, should there be a bug in either Aspell or in
git-gui's output to it.
We escape all input lines with ^, as recommended by the Aspell manual
page, as this allows Aspell to properly ignore any input line that is
otherwise looking like a command (e.g. ! to enable terse output). By
using this escape however we need to correct all word offsets by -1 as
Aspell is apparently considering the ^ escape to be part of the line's
character count, but our Tk text widget obviously does not.
Available dictionaries are offered in the Options dialog, allowing
the user to select the language they want to spellcheck commit
messages with for the current repository, as well as the global
user setting that all repositories inherit.
Special thanks to Adam Flott for suggesting connecting git-gui
to Aspell for the purpose of spell checking the commit message,
and to Wincent Colaiuta for the idea to wait for a word boundary
before passing the message over for checking.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
2008-02-07 08:35:25 +01:00
|
|
|
global ui_comm_spell
|
2007-10-05 14:38:35 +02:00
|
|
|
|
|
|
|
|
set w .about_dialog
|
|
|
|
|
toplevel $w
|
|
|
|
|
wm geometry $w "+[winfo rootx .]+[winfo rooty .]"
|
|
|
|
|
|
2007-10-06 02:15:10 +02:00
|
|
|
pack [git_logo $w.git_logo] -side left -fill y -padx 10 -pady 10
|
2007-10-05 14:38:35 +02:00
|
|
|
label $w.header -text [mc "About %s" [appname]] \
|
|
|
|
|
-font font_uibold
|
|
|
|
|
pack $w.header -side top -fill x
|
|
|
|
|
|
|
|
|
|
frame $w.buttons
|
|
|
|
|
button $w.buttons.close -text {Close} \
|
|
|
|
|
-default active \
|
|
|
|
|
-command [list destroy $w]
|
|
|
|
|
pack $w.buttons.close -side right
|
|
|
|
|
pack $w.buttons -side bottom -fill x -pady 10 -padx 10
|
|
|
|
|
|
|
|
|
|
label $w.desc \
|
|
|
|
|
-text "[mc "git-gui - a graphical user interface for Git."]\n$copyright" \
|
|
|
|
|
-padx 5 -pady 5 \
|
|
|
|
|
-justify left \
|
|
|
|
|
-anchor w \
|
|
|
|
|
-borderwidth 1 \
|
|
|
|
|
-relief solid
|
|
|
|
|
pack $w.desc -side top -fill x -padx 5 -pady 5
|
|
|
|
|
|
|
|
|
|
set v {}
|
|
|
|
|
append v "git-gui version $appvers\n"
|
|
|
|
|
append v "[git version]\n"
|
|
|
|
|
append v "\n"
|
|
|
|
|
if {$tcl_patchLevel eq $tk_patchLevel} {
|
|
|
|
|
append v "Tcl/Tk version $tcl_patchLevel"
|
|
|
|
|
} else {
|
|
|
|
|
append v "Tcl version $tcl_patchLevel"
|
|
|
|
|
append v ", Tk version $tk_patchLevel"
|
|
|
|
|
}
|
git-gui: Automatically spell check commit messages as the user types
Many user friendly tools like word processors, email editors and web
browsers allow users to spell check the message they are writing
as they type it, making it easy to identify a common misspelling
of a word and correct it on the fly.
We now open a bi-directional pipe to Aspell and feed the message
text the user is editing off to the program about once every 300
milliseconds. This is frequent enough that the user sees the results
almost immediately, but is not so frequent as to cause significant
additional load on the system. If the user has modified the message
text during the last 300 milliseconds we delay until the next period,
ensuring that we avoid flooding the Aspell process with a lot of
text while the user is actively typing their message.
We wait to send the current message buffer to Aspell until the user
is at a word boundary, thus ensuring that we are not likely to ask
for misspelled word detection on a word that the user is actively
typing, as most words are misspelled when only partially typed,
even if the user has thus far typed it correctly.
Misspelled words are highlighted in red and are given an underline,
causing the word to stand out from the others in the buffer. This is
a very common user interface idiom for displaying misspelled words,
but differs from one platform to the next in slight variations.
For example the Mac OS X system prefers using a dashed red underline,
leaving the word in the original text color. Unfortunately the
control that Tk gives us over text display is not powerful enough
to handle such formatting so we have to work with the least common
denominator.
The top suggestions for a misspelling are saved in an array and
offered to the user when they right-click (or on the Mac ctrl-click)
a misspelled word. Selecting an entry from this menu will replace
the misspelling with the correction shown. Replacement is integrated
with the undo/redo stack so undoing a replacement will restore the
misspelled original text.
If Aspell could not be started during git-gui launch we silently eat
the error and run without spell checking support. This way users
who do not have Aspell in their $PATH can continue to use git-gui,
although they will not get the advanced spelling functionality.
If Aspell started successfully the version line and language are
shown in git-gui's about box, below the Tcl/Tk versions. This way
the user can verify the Aspell function has been activated.
If Aspell crashes while we are running we inform the user with an
error dialog and then disable Aspell entirely for the rest of this
git-gui session. This prevents us from fork-bombing the system
with Aspell instances that always crash when presented with the
current message text, should there be a bug in either Aspell or in
git-gui's output to it.
We escape all input lines with ^, as recommended by the Aspell manual
page, as this allows Aspell to properly ignore any input line that is
otherwise looking like a command (e.g. ! to enable terse output). By
using this escape however we need to correct all word offsets by -1 as
Aspell is apparently considering the ^ escape to be part of the line's
character count, but our Tk text widget obviously does not.
Available dictionaries are offered in the Options dialog, allowing
the user to select the language they want to spellcheck commit
messages with for the current repository, as well as the global
user setting that all repositories inherit.
Special thanks to Adam Flott for suggesting connecting git-gui
to Aspell for the purpose of spell checking the commit message,
and to Wincent Colaiuta for the idea to wait for a word boundary
before passing the message over for checking.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
2008-02-07 08:35:25 +01:00
|
|
|
if {[info exists ui_comm_spell]} {
|
|
|
|
|
append v "\n"
|
|
|
|
|
append v [$ui_comm_spell version]
|
|
|
|
|
}
|
2007-10-05 14:38:35 +02:00
|
|
|
|
|
|
|
|
set d {}
|
|
|
|
|
append d "git wrapper: $::_git\n"
|
|
|
|
|
append d "git exec dir: [gitexec]\n"
|
|
|
|
|
append d "git-gui lib: $oguilib"
|
|
|
|
|
|
|
|
|
|
label $w.vers \
|
|
|
|
|
-text $v \
|
|
|
|
|
-padx 5 -pady 5 \
|
|
|
|
|
-justify left \
|
|
|
|
|
-anchor w \
|
|
|
|
|
-borderwidth 1 \
|
|
|
|
|
-relief solid
|
|
|
|
|
pack $w.vers -side top -fill x -padx 5 -pady 5
|
|
|
|
|
|
|
|
|
|
label $w.dirs \
|
|
|
|
|
-text $d \
|
|
|
|
|
-padx 5 -pady 5 \
|
|
|
|
|
-justify left \
|
|
|
|
|
-anchor w \
|
|
|
|
|
-borderwidth 1 \
|
|
|
|
|
-relief solid
|
|
|
|
|
pack $w.dirs -side top -fill x -padx 5 -pady 5
|
|
|
|
|
|
|
|
|
|
menu $w.ctxm -tearoff 0
|
|
|
|
|
$w.ctxm add command \
|
|
|
|
|
-label {Copy} \
|
|
|
|
|
-command "
|
|
|
|
|
clipboard clear
|
|
|
|
|
clipboard append -format STRING -type STRING -- \[$w.vers cget -text\]
|
|
|
|
|
"
|
|
|
|
|
|
|
|
|
|
bind $w <Visibility> "grab $w; focus $w.buttons.close"
|
|
|
|
|
bind $w <Key-Escape> "destroy $w"
|
|
|
|
|
bind $w <Key-Return> "destroy $w"
|
|
|
|
|
bind_button3 $w.vers "tk_popup $w.ctxm %X %Y; grab $w; focus $w"
|
|
|
|
|
wm title $w "About [appname]"
|
|
|
|
|
tkwait window $w
|
|
|
|
|
}
|