diff options
| author | nagai <nagai@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2008-02-27 18:44:31 +0000 |
|---|---|---|
| committer | nagai <nagai@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2008-02-27 18:44:31 +0000 |
| commit | 57a3925cc09f4d5fdc25f247d980f69e3aae33a3 (patch) | |
| tree | 278f46cf1b6a9afafd3391af2b29e8a2ecf31dd4 /ChangeLog | |
| parent | b4ca807898ad957bc45d47a62fe6f6b2b2f64a69 (diff) | |
| download | ruby-57a3925cc09f4d5fdc25f247d980f69e3aae33a3.tar.gz ruby-57a3925cc09f4d5fdc25f247d980f69e3aae33a3.tar.xz ruby-57a3925cc09f4d5fdc25f247d980f69e3aae33a3.zip | |
* ext/tk/lib/tk.rb, ext/tk/lib/*: make default widget set
switchable between Tk (standard Tcl/Tk widget set) and
Ttk (Tile). Initial default widget set is Tk. Now, toplevel
widget classes are removed and defined as aliases.
For example, "TkButton" is an alias of the "Tk::Button" class.
Those aliases are replaced when switching default widget set.
"Tk.default_widget_set=" is the method for switching default
widget set. "Tk.default_widget_set = :Ttk" defines Ttk (Tile)
widget set as default. It means that "TkButton" denotes
"Tk::Tile::Button" class. And then, "TkButton.new" creates
a Tk::Tile::Button widget. Of course, you can back to use
standard Tk widgets as the default widget set by calling
"Tk.default_widget_set = :Tk", whenever you want. Based on
thie feature, you can use Ttk widget styling engine on your
old Ruby/Tk application without modifying its source, if you
don'tuse widget options unsupported on Ttk widgets (At first,
call "Tk.default_widget_set = :Ttk", and next load and run
your application).
This is one step for supporting Tcl/Tk8.5 features.
git-svn-id: http://svn.ruby-lang.org/repos/ruby/trunk@15618 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 24 |
1 files changed, 23 insertions, 1 deletions
@@ -1,3 +1,25 @@ +Thu Feb 28 03:03:32 2008 Hidetoshi NAGAI <nagai@ai.kyutech.ac.jp> + + * ext/tk/lib/tk.rb, ext/tk/lib/*: make default widget set + switchable between Tk (standard Tcl/Tk widget set) and + Ttk (Tile). Initial default widget set is Tk. Now, toplevel + widget classes are removed and defined as aliases. + For example, "TkButton" is an alias of the "Tk::Button" class. + Those aliases are replaced when switching default widget set. + "Tk.default_widget_set=" is the method for switching default + widget set. "Tk.default_widget_set = :Ttk" defines Ttk (Tile) + widget set as default. It means that "TkButton" denotes + "Tk::Tile::Button" class. And then, "TkButton.new" creates + a Tk::Tile::Button widget. Of course, you can back to use + standard Tk widgets as the default widget set by calling + "Tk.default_widget_set = :Tk", whenever you want. Based on + thie feature, you can use Ttk widget styling engine on your + old Ruby/Tk application without modifying its source, if you + don'tuse widget options unsupported on Ttk widgets (At first, + call "Tk.default_widget_set = :Ttk", and next load and run + your application). + This is one step for supporting Tcl/Tk8.5 features. + Wed Feb 27 22:55:42 2008 NARUSE, Yui <naruse@ruby-lang.org> * string.c (rb_str_coderange_scan_restartable): coderange scaning @@ -5079,7 +5101,7 @@ Fri Dec 21 18:40:54 2007 Koichi Sasada <ko1@atdot.net> * bootstraptest/test_io.rb, test_knownbug.rb: move a fixed test. -Fri Dec 21 17:56:30 2007 <nagai@orca16.orcabay.ddo.jp> +Fri Dec 21 17:56:30 2007 Hidetoshi NAGAI <nagai@ai.kyutech.ac.jp> * ext/tk/tcltklib.c: provisional support on Ruby-VM. |