2005-03-05 02:35:41 -05:00
|
|
|
#
|
|
|
|
# tframe widget
|
|
|
|
# by Hidetoshi NAGAI (nagai@ai.kyutech.ac.jp)
|
|
|
|
#
|
|
|
|
require 'tk'
|
|
|
|
require 'tkextlib/tile.rb'
|
|
|
|
|
|
|
|
module Tk
|
|
|
|
module Tile
|
* 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: svn+ssh://ci.ruby-lang.org/ruby/trunk@15618 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2008-02-27 13:44:31 -05:00
|
|
|
class TFrame < Tk::Frame
|
2005-03-05 02:35:41 -05:00
|
|
|
end
|
2005-08-04 00:48:13 -04:00
|
|
|
Frame = TFrame
|
2005-03-05 02:35:41 -05:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
* 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: svn+ssh://ci.ruby-lang.org/ruby/trunk@15618 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2008-02-27 13:44:31 -05:00
|
|
|
class Tk::Tile::TFrame < Tk::Frame
|
2005-03-05 02:35:41 -05:00
|
|
|
include Tk::Tile::TileWidget
|
|
|
|
|
|
|
|
if Tk::Tile::USE_TTK_NAMESPACE
|
|
|
|
TkCommandNames = ['::ttk::frame'.freeze].freeze
|
|
|
|
else
|
|
|
|
TkCommandNames = ['::tframe'.freeze].freeze
|
|
|
|
end
|
|
|
|
WidgetClassName = 'TFrame'.freeze
|
2009-07-12 19:08:32 -04:00
|
|
|
WidgetClassNames[WidgetClassName] ||= self
|
2005-04-09 05:27:54 -04:00
|
|
|
|
|
|
|
def self.style(*args)
|
|
|
|
[self::WidgetClassName, *(args.map!{|a| _get_eval_string(a)})].join('.')
|
|
|
|
end
|
2005-03-05 02:35:41 -05:00
|
|
|
end
|
2009-07-12 19:08:32 -04:00
|
|
|
|
|
|
|
#Tk.__set_toplevel_aliases__(:Ttk, Tk::Tile::Frame, :TkFrame)
|
|
|
|
Tk.__set_loaded_toplevel_aliases__('tkextlib/tile/tframe.rb',
|
|
|
|
:Ttk, Tk::Tile::Frame, :TkFrame)
|