Re: [Wxruby-dev] Summary of naming problems

[Kevin Smith]

On Sun, 2003-06-22 at 10:59, Kevin Smith wrote:
> Ok. I've tried to figure out a way out of all of this. So I laid out all
> the naming problems that I'm aware of right now. Here are the C++
> wxWindows naming categories I've found, with examples:
> 
> CLASS
>  wxWindow
> 
> CLASS METHOD
>  GetPosition
> 
> GLOBAL METHOD
>  wxMessageBox
>  EVT_MENU
> 
> CONSTANT, PRE-DEFINED OBJECT, PTR TO PRE-DEFINED OBJECT
>  wxSUNKEN_BORDER
>  wxLIGHT_GREY
>  wxNullColour
>  wxDefaultPosition
>  WXK_TAB

Rich and Curt now agree on ruby style, and I'm willing to go along. And
I think we have a consensus that we will discourage global including of
Wx and encourage the use of Wx:: (or Wx.). So here's the latest proposal
on the table:

CLASS
 Wx::Window

CLASS METHOD
 get_position

GLOBAL METHOD
 Wx.message_box
 Wx.evt_menu

CONSTANT, PRE-DEFINED OBJECT, PTR TO PRE-DEFINED OBJECT
 Wx::SUNKEN_BORDER
 Wx::LIGHT_GREY
 Wx::NULL_COLOUR
 Wx::DEFAULT_POSITION
 Wx::K_TAB

I think I can live with that. And it means I don't have to undo anything
I've already done (Yea!).

Kevin