wxruby development - May 2008 - [ wxruby-Feature Requests-20367 ] wxToolBarTool (wxToolBarToolBase) missing, thus anti-OO

Feature Requests item #20367, was opened at 26/05/2008 16:32
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=221&aid=20367&group_id=35

Category: Missing class(es)
Group: None
Status: Open
Priority: 3
Submitted By: Pascal Hurni (phi)
Assigned to: Kevin Smith (qualitycode)
Summary: wxToolBarTool (wxToolBarToolBase) missing, thus anti-OO

Initial Comment:
The fact that WxToolBarTool is missing (these object represent a tool in a
toolbar) makes it anti-OO and thus less rubyesque to manage toolbars.

Toolbars are the last component (as I''v seen) that requires concrete
ID''s. This is a pain to handle in ruby. We want objects (propaganda).

Example:
  tb = Wx::Toolbar.new(frame)
  tb.add_tool(1000, "Click me", fancy_bitmap)
  tb.add_tool(1001, "Don''t click here", fancy_bitmap)

  evt_tool(1000) { puts "Great job" }
  evt_tool(1001) { puts "I warned you" }

Those IDs: 1000, 1001 may clash with other toolbars on the same frame. For a
fixed app this may be not a great problem, but for generated apps it''s
a mess.

I really want to be able to do

  tb = Wx::Toolbar.new(frame)
  tryme = tb.add_tool(Wx::ID_ANY, "Click me", fancy_bitmap)
  dangerous = tb.add_tool(Wx::ID_ANY, "Don''t click here",
fancy_bitmap)

  evt_tool(tryme) { puts "Great job" }
  evt_tool(dangerous) { puts "I warned you" }

(Well, those ID_ANY should also go away, but this can be done with keyed
constructor arguments)

That''s it.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=221&aid=20367&group_id=35